I'm pretty sure the my500e guy is making out alright by selling them. Will it make him independently wealthy.... **** no. But for $300 in "hardware" which likely cost ~$40 or less, and $70/yr server fees (which even if he rents an AWS server for it, CAN"T be 70/yr/device) he's making a very healthy profit. It's not a long term, or massive quantity profit... but still a hefty profit considering.It doesn't make sense as a business plan. I suspect that it began as a 500e owner/engineer originally creating it for his own personal use. Like the guy who is selling 500e aerodynamic underbody panels.
I'd love to work with you on this. I've dabbled a bit in the electronics, its the can addressing where I've not done enough mapping/logging to cobble this together, mostly because my car works and I'm not pushed too much to make it better, even though it'd be a lot more convenient. Also working WITH someone on it means i'm pushed to do more than log and try to decipher every time the car annoys me (when it starts getting cold, when it first is 100+ outside, etc) then drop it once it bores me.@Ironhydroxide absolutely - raw costs aren't much. It's all about low volume, high effort, and no other options. I agree with @MondoMojo. It does the basics for people who just want it to just work. I've had one for a few months and don't regret it one bit. I've even used their API to make my own apps and features - but this can only go so far.
I am still personally learning/working on decoding the CAN because I want much more. my500e lacks hardware and software capabilities making certain things impossible or impractical (as confirmed by emailing with creator.) Things like:
- Offline lock/unlock (to make my proximity lock/unlock faster)
- Offline precondition (for more complicated/automated cabin conditioning)
- Performance metrics logged and aggregated (so we can back our performance claims and advice with reliable data)
- All the lesser messages like SWC, doors, trunk, windows, etc (to tie into for other automations)