Companies should be forced to hand over the communication and operation specification of their IoT devices as soon as they meaningfully degrade the quality or functionality of a cloud service. This will restore trust in the ecosystem, avoid ewaste, and nourish a community of developers/hackers/geeks/users.
Great framing, we’re incapable of maintaining a cloud solution that we built for a product we sold to you, so we’re taking it down for your protection.
I’m surprised that they aren’t charging their customers for such great service and attention to detail.
A great opportunity to bring up that a robot that operates 100% locally and is located within Bluetooth range has never needed a cloud account, has never had to become unavailable whenever AWS goes down, and certainly doesn't have to be reduced to a manual dud when its company ceases to exist. I wonder what whoever produced such "Systems Design" would have to say to customers now.
Neato's D-Series Botvac just works (e.g., BVD8-SD/HP). No Bluetooth. No cloud. No Wi-Fi. Zero network connectivity required. Had mine about 10 years. Replaced the battery once, probably due for another one. Still cleans well.
I don't understand the appeal of having local appliances bound to the fate of network services.
Neato made a line of (good) vacuum robots with Lidar.
It seems there were bought by a company called Vorwerk, and Vorwerk are shutting down the cloud infra.
This means the app, floor plans, schedules, no-go zones etc will no longer work. The robot can only be manually started by pushing the button on the device.
As an owner of one of these robots this is sad but not unexpected for anything relying on an app.
By submitting to HN, I’m hopeful someone can point me in the direction of open firmware or OSS projects that can help me restore the lost functionality.
Vorwerk is the company who makes Themromix - that is a quite expensive cooking robot
. They also are a MLM sales company albeit with a decently appealing product. I expect in a couple of months to get calls to get free cleaning demos. I guess they will have a turf war with the Kirby people.
> Please note that this list is exhaustive. These are the supported robots.
Robots not on this list are not supported by Valetudo. If your robot is not on this list, it is not supported.
From what i gathered so far, Valetudo is actually no custom firmware but modified vendor firmware? So, not sure if anyone related to the project has any interest and capability to reverse that...
When I looked into it, it seemed like a community that loved freeing robots but was absolutely not willing to buy robots that the developers did not have access to. This seems like a fair stance and I think they will start receiving dead vacuums soon. Hopefully Neato's security is as bad as their business side.
I currently not expect a existing project, but the communication with the server is mostly xml, with the app too. It's a relatively easy protocol and the robot has more or less no protection against changing the software and some security bugs to own it without opening the case.
Is that what was advertised when the product was sold? As long as "press the button on the hoover once to launch a full house run" was the only thing advertised to sell the hoover, then I'm ok with that. But I highly doubt it.
Wonder why they built them like that? How was the decision made, just simply incompetence: they didn't know how to do it any other way, delusion: they expected to be become the Google or the Microsoft of vacuums: they'd never go out of business. Maybe just plain greed: wanted to milk their customers for extra features and disable them remotely if they stop paying?
Perhaps one day some jurisdiction will have the wherewithal to implement legislation to stop this madness. At the very least all the device and protocol documentation and crypto keys etc should be escrowed somewhere for the day this happens.
What would help just as much: people actually giving a fcuk - as in: researching how durable something is, how hackable, how cloud-dependant or not...
...and not act all surprised when something stops working once the manufacturer calling it quits (or starts charging for a previously-free service).
Today, whenever i talk to others how i evaluate products i still get blank stares and i might as well have talked in a foreign tongue.
Also not happening: learning from $companys previous behaviour - stopped supporting something after a year? No parts, no schematics, no nothing?
Well - welcome to my shitlist of companies that'll never see another $/€ from me, ever again.
Doing this eventually would force companies to change their ways, but as long as they can continue selling whatever dreck they come up with to the masses...
You're blaming the end users. Most end users aren't aware of this stuff, and even if they are, have no practical way to evaluate quality in the way you've described. Even I, as a very technical person, could not evaluate if something is "hackable" without a huge amount of work, and not before I've purchased it.
Like similar cases (is this car roadworthy? are airplanes safe?), this is the classic case for regulation.
Companies should be forced to hand over the communication and operation specification of their IoT devices as soon as they meaningfully degrade the quality or functionality of a cloud service. This will restore trust in the ecosystem, avoid ewaste, and nourish a community of developers/hackers/geeks/users.
Even better, they should be required to publish the communication protocol as soon as the device is released.
Great framing, we’re incapable of maintaining a cloud solution that we built for a product we sold to you, so we’re taking it down for your protection.
I’m surprised that they aren’t charging their customers for such great service and attention to detail.
"Updating this environment would not be technically meaningful"
This is Kremlin-level deflection.
A great opportunity to bring up that a robot that operates 100% locally and is located within Bluetooth range has never needed a cloud account, has never had to become unavailable whenever AWS goes down, and certainly doesn't have to be reduced to a manual dud when its company ceases to exist. I wonder what whoever produced such "Systems Design" would have to say to customers now.
> a robot that operates 100% locally and is located within Bluetooth range
Which robot is that?
Neato's D-Series Botvac just works (e.g., BVD8-SD/HP). No Bluetooth. No cloud. No Wi-Fi. Zero network connectivity required. Had mine about 10 years. Replaced the battery once, probably due for another one. Still cleans well.
I don't understand the appeal of having local appliances bound to the fate of network services.
Dreame with Valetudo
https://valetudo.cloud/pages/installation/dreame.html
I mean it's _every_ robot with valetudo, but I don't think any manufacturer sells their robots with valetudo preinstalled.
Neato made a line of (good) vacuum robots with Lidar.
It seems there were bought by a company called Vorwerk, and Vorwerk are shutting down the cloud infra.
This means the app, floor plans, schedules, no-go zones etc will no longer work. The robot can only be manually started by pushing the button on the device.
As an owner of one of these robots this is sad but not unexpected for anything relying on an app.
By submitting to HN, I’m hopeful someone can point me in the direction of open firmware or OSS projects that can help me restore the lost functionality.
Vorwerk is the company who makes Themromix - that is a quite expensive cooking robot . They also are a MLM sales company albeit with a decently appealing product. I expect in a couple of months to get calls to get free cleaning demos. I guess they will have a turf war with the Kirby people.
Before they made that cooking machine, they were in the business of premium vacuum cleaners -
https://valetudo.cloud is the only one I know about but not sure if the controller in those units would be flashable.
Well, it appears that Neato/Vorwerk robots are not supported - at least they're not listed on https://valetudo.cloud/pages/general/supported-robots.html
> Please note that this list is exhaustive. These are the supported robots. Robots not on this list are not supported by Valetudo. If your robot is not on this list, it is not supported.
From what i gathered so far, Valetudo is actually no custom firmware but modified vendor firmware? So, not sure if anyone related to the project has any interest and capability to reverse that...
When I looked into it, it seemed like a community that loved freeing robots but was absolutely not willing to buy robots that the developers did not have access to. This seems like a fair stance and I think they will start receiving dead vacuums soon. Hopefully Neato's security is as bad as their business side.
I currently not expect a existing project, but the communication with the server is mostly xml, with the app too. It's a relatively easy protocol and the robot has more or less no protection against changing the software and some security bugs to own it without opening the case.
This reminds me a lot situation with computer games. Maybe stop killing games movement scope should be widened to all the software?
> This decision was not made out of convenience or incapacity.
I don't believe you...
> Robots still work: Your Neato robot will continue to function manually. Simply press the button once to launch a full house run.
The title is strictly wrong, the things that's being discontinued is the cloud platform.
Still shit though...
Is that what was advertised when the product was sold? As long as "press the button on the hoover once to launch a full house run" was the only thing advertised to sell the hoover, then I'm ok with that. But I highly doubt it.
Wonder why they built them like that? How was the decision made, just simply incompetence: they didn't know how to do it any other way, delusion: they expected to be become the Google or the Microsoft of vacuums: they'd never go out of business. Maybe just plain greed: wanted to milk their customers for extra features and disable them remotely if they stop paying?
Perhaps one day some jurisdiction will have the wherewithal to implement legislation to stop this madness. At the very least all the device and protocol documentation and crypto keys etc should be escrowed somewhere for the day this happens.
Sure, having legislation would help tremendously.
What would help just as much: people actually giving a fcuk - as in: researching how durable something is, how hackable, how cloud-dependant or not...
...and not act all surprised when something stops working once the manufacturer calling it quits (or starts charging for a previously-free service).
Today, whenever i talk to others how i evaluate products i still get blank stares and i might as well have talked in a foreign tongue.
Also not happening: learning from $companys previous behaviour - stopped supporting something after a year? No parts, no schematics, no nothing?
Well - welcome to my shitlist of companies that'll never see another $/€ from me, ever again.
Doing this eventually would force companies to change their ways, but as long as they can continue selling whatever dreck they come up with to the masses...
You're blaming the end users. Most end users aren't aware of this stuff, and even if they are, have no practical way to evaluate quality in the way you've described. Even I, as a very technical person, could not evaluate if something is "hackable" without a huge amount of work, and not before I've purchased it.
Like similar cases (is this car roadworthy? are airplanes safe?), this is the classic case for regulation.
> Robots still work: Your Neato robot will continue to function manually. Simply press the button once to launch a full house run.
Your title is wrong
Perhaps a better title is “to stop working in the way they were sold / advertised”?
Almost all functionality is being disabled, other than limited manual operation.
The functionality is very much reduced.
Then they will hopefully refund their customers.