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-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.
> 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.
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.
Indeed. The day to day compliance work will be very expensive, and in addition you would need to put a lot of money aside in case of a security flaw.
This is the kind of thing that they frequently hand-wavingly claim, however, 'compliance'? I'm not aware of any US garage door regulatory body.
These same companies have you click through 1000 pages of legalese (that thoroughly covers their butts) in order to use their own apps, which are probably more likely to be compromised than a public API, so I don't know why that would come with more liability.
Well, that certainly is the disingenuous corporate line. But the 'hackers' required nothing of Chamberlain -- what they built was already working, until they played a cat-and-mouse game to block them until the maintainer gave up. There are hundreds of companies that do support Home Assistant integrations or at least let them exist, and maintainers are always eager to fix any issue that comes up.
It's really not a dichotomy between aggressively blocking users from having any control over their own home, vs. some kind of imaginary concierge red carpet public API service that hijacks the company's product roadmap. The open source community will basically do 100% of the work for any firm which doesn't opt to actively sabotage.
- [deleted]
Pretty sure Chamberlain/MyQ was because they made their API go through the cloud for no reason (that garage door opener isn't going to get out of WiFi range), so the only way to make the app reliably work was to hit their servers. Which they then had to pay for.
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.
I agree with you. Of course, they already made the money selling the garage door openers, and make more money on the millions of people who use the Amazon and Walmart integrations (they get a little fee for opening the door for those). But if this cut their cloud bill by $200 a month or something I guess they feel vindicated.
This is why I avoid all those "smart" devices like the plague.
They’re API used to work via just providing a VIN however that also allowed remote control so you could just run through all the VINs Nissan uses and turn on remote heating, etc.
This was reported in the media which caused Nissan to start locking down their API something fierce.
Then the three years free of many services have started to expire for most vehicles, so locking it down more became a potentially profitable exercise so now they actual have development work against it.
Car APIs are $$$.
If you want to have some unified API check https://enode.com/connect, but that too costs a premium.