Automatic (Car Adapter) Shutting Down(automatic.com) |
Automatic (Car Adapter) Shutting Down(automatic.com) |
Luckily I got a lot of use out of them, but definitely said to see them go.
Having a subscription means it can disappear on you at any point.
In the good old days, businesses thrived perfectly well off of one-time purchases of products.
The added information compared to what Google or Apple are collecting is perhaps ODB metrics, but I'm not sure whether ODB metrics of gaz cars have a lot of value.
Said like nobody will ever drive cars again.
I'm perplexed at how quickly these businesses are deciding to fold.
What upsets me is seeing this hardware just become e-waste. I really dislike seeing perfectly functional hardware become unusable just because the company folds or something newer comes out. I ranted about the iphone 4 and how it's no longer possible to build software on that platform, especially since it's low power and could be used for any small project. My old Nexus 7 is still kicking (just slooow)
> We no longer recommend using the Automatic car adapter due to reliability issues.
Do you happen to know if this is real or just a CYA? I'd pay $10 to extend the life of my adapter, but not if I needed to buy another device anyway.
i.e. if you uninstall the BT apps, change phone etc...
This is IoT.
Just out of curiosity, have there been more (relatively successful) companies with a paid subscription plan that announced that they would, within a couple of weeks, shut their services down? As an outsider it seems quite drastic to me, given that the daily costs of keeping the servers running a bit longer is negligible.
https://play.google.com/store/apps/details?id=org.prowl.torq...
I see what you did there :D
[EDIT] Thank you to the wonderful hackers who reached out to me. I think that I am all set now.
Anyway, I had an original Bluetooth Automatic until I upgraded to a Pro when it was launched. I love them! Sorry to hear this is the end.
We're working on mitigating this by having an open hardware platform. The idea being that, even if our cloud service isn't up, you can re-flash the hardware to do anything you want. And you can use our documentation to do it so you don't have to reverse-engineer everything from scratch.
I'd like to see more companies follow this approach. I've at least a handful of IoT devices that are effectively bricked, which sucks because I know they have decent and usable innards.
These IoT devices (and especially the phones and PCs that typically act as intermediaries) are abundantly capable of storing the configuration data and doing the API calls necessary to communicate with online services.
Is it just about the control?
I think that's absolutely great. I've had enough IoT products brick on me that I avoid most out of principle now. I'd change my mind for a product that make it clear they've implemented a customer-friendly plan for when the servers inevitably are shut down.
That said, I think your plan really only seems to help tinkerers. There may be no way around that for what you're building, but I think graceful degradation in functionality is preferable, such as having a maximally-functional no-cloud mode. The few smart products I buy have a mode like that.
Perhaps the choices you make and the time you spend on mitigating the possibility of your product becoming e-waste will make you more likely to fail, leading to a higher probability of your product becoming e-waste because most people won't bother re-flashing the hardware you're making.
Work on improving your product and making sure that you succeed.
Sadly this doesn’t scale, it takes specialized skills and time to build out home automation using these technologies.
I read about how the company had just discontinued the old version of the product in the reviews on Google play of their app figured I'd have some decent time with it since they just rolled out the version I bought...
Jokes on me!
Any chance there's some way we could get the data out of them with something open source?
I'm sorry that people are losing jobs over such closure, but usually the writing is on the wall.
[1]: https://help.automatic.com/hc/en-us/articles/360000599847-Ho...
It records how gas-efficient your driving is, as well as beeping when you go over 80 mph or have a hard break.
It tried to gamify your driving behavior to be more efficient and safe. And I think it was effective but from the start it's been tied to the cloud.
At the start they'd send weekly reports of driving behavior, congratulating or saying what could be done better. As well as tracking (with location data on the phone) where you drove. I once used it to expense milage for a conference.
However the emails soon stopped coming as frequently or reliably, then a year later when the emails stopped they said they were discontinuing my unit, encouraging me to buy the new one. I did not, as they failed to provide me with the service they promised.
EDIT: to clarify, the phone app would start upon bluetooth connection, and send the data to Automatic. I'm not sure if it was realtime or not.
Also consider:
1. The choices we make on mitigating the possibility of the product being waste can actually improve our product. For example, because the product can be reprogrammed easily, we can enter verticals that wouldn't be possible otherwise. Or because our hardware is well-architected and documented, it's easier for us to iterate on it.
2. If we fail because we couldn't figure out a way to make the product responsibly, that's a good thing. I'd rather we fail early than put out waste.
Great feedback. A limited "no-cloud" mode is something we could possibly do, I'll think about it.
I think you are correct that it would really only be a small number of people who would be able to use our docs and write their own firmware for our device. But we want to make it relatively easy to switch between public firmware variants.
So even if you're not an engineer, you can choose to try a different flavor for your device. And if we have to completely shut down our services, you could do that as well.
I could surely get a different BT ODB reader but I already have this one.
For devices that are air-gapped the idea may be workable, but not in the form you’ve outlined for internet-connected devices. What happens when a major vulnerability is discovered? Who is liable when a vulnerable device gets exploited in a well-orchestrated breach?
Such a company would eventually be confronted with the reality of lawsuits.
Honestly, that kinda seems like something that makes sense to do server-side, especially if they were forced to implement some of those integrations in very kludgy and fragile ways (like screen scraping/form filling). Even if the calls were made directly from the customer's device, there's probably a background hum of development work needed just to keep the integrations working.
Other than the fact that this is difficult to keep up-to-date and working, it increases the hardware cost significantly. Instead of having a very cheap microcontroller handling everything, you might need something more capable and more expensive.
Development cost goes up too, since instead of writing your integrations in Python, Go, JS, or whatever, you need to write your integrations on your embedded system.
In theory, it could be done on a cellphone, but a ton of extra data is needed inc volumetric models of an engine (to calculate fuel usage accurately). Doing it server side makes it possible to build this in an agile method vs going to every single make/model and getting this right the first time.
Can you comment on what the safety/security/reliability blocks were?
- loss of ground
A vehicle OBD connector can at times, loose its GND pin. There are actually two GND pins - chassis and electrical that can sometimes disagree. Its possible for one of either of them to either (a) loose connectivity (b) bias towards the signal level or head towards a negative signal level (-2v was our typical observation).
To prevent an OBD protocol pin from dumping current down the channel, a complex HW/SW solution is needed to monitor and react quickly to prevent downstream ECUs from being fried.
- security
We built a custom debug tool based on CM-DAP (ARM debugger technology) that included OOB security paths to unlock a device for re-flashing / debugging. I think we made 500-1k of these in total for manufacturing/RMA/logistic purposes. This was super fun to work on :)
It looks like they are spending over $2B annually on content fees. They could launch a lot of satellites with $2B per year.
Not every vehicle might need or want a full blown satellite ground terminal that can provide IP service.