31–40 of 104 posts
I wish that US car manufacturers would finally realize that they're software companies with a hardware device, and pivot accordingly. The differentiating factor between car models is not the hardware in the world of EVs. It's the software. And right now, if you aren't either on Tesla, Rivian, or Polestar the software experience is horrific.
Earlier quoted context omitted.
> and then I need to wait 3 seconds to see if it actually turned them on If you want to unlock a Kia with the app, first you need to pay $15/month, and then you need to press and hold for one second the unlock button, after which you have a 30-50% chance of the unlock request going through. To let you know that it went through, you will receive an email. It's the most user-hostile app I still have on my phone. So no,…
I had remote unlock for my Chevy Volt in 2012. It was as fast as Tesla's. So yep, Tesla sucks. Other car makers can suck a bit more, but that doesn't make Tesla any better.
Great work! I love commitment to make it at no cost as @liamwire mentioned. Still not sure why on Earth car manufacturers would not just release APIs open to all owners (basically issue API key based on VIN) and let them use it. For developers to build apps that will only require API key to be entered would be win/win for everyone....
Like all similar "why don't they have at least a self/community-supported open basic API" questions, the answer is usually the same: They're afraid someone else might create something of value, in part using their API, without them getting their own beaks wet in the process. If you want to integrate with a Nissan Leaf, even if all you wanted were the most harmless read-only access, they'd like you to request a biz dev meeting with them where they'll be happy to talk ruinous terms.
For a related story, see how Chamberlain (MyQ) torched the great, community-built Home Assistant integration it once had for no reason at all. They're afraid somehow they could stop getting the kickbacks from the likes of Walmart and Amazon delivery which they enjoy today, seeing themselves as co-owners of your garage door.
Earlier quoted context omitted.
I had remote unlock for my Chevy Volt in 2012. It was as fast as Tesla's. So yep, Tesla sucks. Other car makers can suck a bit more, but that doesn't make Tesla any better.
Even this example is terrible, I don't "remote unlock" my Tesla, it's just unlocked when I get close to it. It used to be 95% reliable (not great), but now that they added an Apple Watch app, it's 100% reliable (either my phone or my watch unlocks it via proximity).
(yes I know manufacturer tools go deeper but that's another issue)
Just like OBD, I think api access to data like this should be open to the car user. If the manufacturer is taking the data ( as they do with my renault zoe) then it should be available to the end user at a standard API which is available across all manufacturers, so if you change car you can just point your setup at a new endpoint with new credentials and all the endpoints and responses are standard, just like OBD2 i…
[1] https://digital-strategy.ec.europa.eu/en/policies/data-act
Great work! I love commitment to make it at no cost as @liamwire mentioned. Still not sure why on Earth car manufacturers would not just release APIs open to all owners (basically issue API key based on VIN) and let them use it. For developers to build apps that will only require API key to be entered would be win/win for everyone....
> Still not sure why on Earth car manufacturers Like all similar "why don't they have at least a self/community-supported open basic API" questions, the answer is usually the same: They're afraid someone else might create something of value, in part using their API, without them getting their own beaks wet in the process. If you want to integrate with a Nissan Leaf, even if all you wanted were the most harmless read-…
In most cases it's not about profit, but about having to invest serious amounts of effort to please one or two hackers, who will then DoS your API as soon as you've made a mistake.
I've seen Actions that create a usable Arch etc repos where other software that has been build can be listed
What's the most creative set-up using a number of Actions that anyone has seen? On GitHub or elsewhere
P.S. Could that computational paradigm somehow be extended to a Yahoo! Pipes form of visual [data]flow? For some kind of personal orchestrations
Earlier quoted context omitted.
I had remote unlock for my Chevy Volt in 2012. It was as fast as Tesla's. So yep, Tesla sucks. Other car makers can suck a bit more, but that doesn't make Tesla any better.
Even this example is terrible, I don't "remote unlock" my Tesla, it's just unlocked when I get close to it. It used to be 95% reliable (not great), but now that they added an Apple Watch app, it's 100% reliable (either my phone or my watch unlocks it via proximity).
Great work! I love commitment to make it at no cost as @liamwire mentioned. Still not sure why on Earth car manufacturers would not just release APIs open to all owners (basically issue API key based on VIN) and let them use it. For developers to build apps that will only require API key to be entered would be win/win for everyone....
> Still not sure why on Earth car manufacturers Like all similar "why don't they have at least a self/community-supported open basic API" questions, the answer is usually the same: They're afraid someone else might create something of value, in part using their API, without them getting their own beaks wet in the process. If you want to integrate with a Nissan Leaf, even if all you wanted were the most harmless read-…
Had the whole setup been local first, they wouldn't ever had that issue. But again, that makes it hard to charge people for using it.