61–70 of 655 posts
Earlier quoted context omitted.
You can access the device when you're away from home if it's internet connected. Of course, the server doesn't need to be doing much besides proxying connections.
And of course, you can easily run a VPN/Tailscale/ZeroTier/whatever to achieve the same without the downsides.
You don’t need a cloud server to remotely access a device.
Why does a garage door need an API?
Two reasons: 1. My wife can check that we didn't forget to close it instead of driving 20 minutes back home to quell her nerves. 2. We can let a friend or neighbor into the garage (or into the house if we use the smart lock on the door inside the garage) when we're not home. Without giving permanent access to a key or PIN code.
Earlier quoted context omitted.
I prefer to have an e-waste law that says that if you stop maintaining the service, you have to open-source it :)
That will only work for the code the company owns herself. But they can't open source code they licensed themselves, which means they can easily cheat the law by outsourcing their code.
can we just make non-sens like that illegal no one has time for it you bought the device you should own it it's not even anything fancy where you could argue that continuous software updated need to be done or similar also pass a law that all smart home devices had to go through a hub, no direct internet connection allowed, uh put it under "reducing DDOS potential due to long term issues with internet connected smart…
> all smart home devices had to go through a hub I fully agree, this is the reason I mostly buy Zigbee devices for my smart home. The problem with this rule is that there is already a device on the market that complies with it on paper, but not how you intended: Amazon Echo devices act as Zigbee gateways. While I never tried it, I bet it will not turn on your lights without calling the mothership. If this rule were t…
I think that part is more important than demanding a hub. Demanding that the device can connect to a local hub (where "can" means "can easily be reconfigured without going through the original manufacturer or requiring expensive tools"...) speaking open protocols (and specify clearly what "open protocol" means, to avoid your 600 page, 200$ ISO standard) is more important than requiring that they must connect to a local hub. Also necessary to specify that you can carry out all the functions of the device via open protocols, or you'll get bullshit where essentials get locked away.
Personally, I don't care if I have proprietary smart home devices. I do care that the maximum cost and hassle if a manufacturer goes "rogue" like in this linked article remains low. So each proprietary device in current use reduces my willingness to get another one. Currently, all of my devices can be controlled via open source, and though some of them (some cheap Govee led strips) do call home, there are open source to talk to them, and worst case I can literally cut them off with a pair of scissors and replace the controllers for a pittance if they ever become a nuisance, and that makes them an acceptable choice (though whenever there are multiple options I will look for the more open one).
I use Home Assistant and have this openner. My installer recommeneded it because he’s had happy customers like me who use home automation. I can tell you that I a) will never recommend or buy the brand again, and b) have already complained to my installer about his recommendation of this line (and he is moving to another brand). I wish ratgdo a ton of success and have several on order.
On top of the lack of integration support, the MyQ app used to open garage doors is full of advertisements. It's ridiculous. I regret buying their products.
This will most likely be a significant factor in though, though good luck getting them to admit it.
HA users will mostly be bypassing the app and therefore not providing revenue via ad impressions.
Earlier quoted context omitted.
Devices that rely on cloud infrastructure should be required to carry an expiration date right on the box. "This item guaranteed to receive support until XX/XX/XX"
There are lots of devices these days that rely on cloud infrastructure, like Apple devices, Teslas. Its becoming more devices. The same for software. Even Microsoft is going fully Cloud. Just had problems to activate my MS Office for Mac Business 2019, which I bought in physical. They now require on @outlook.com email address to be able to activate. Otherwise I can't use my "box" software.
Earlier quoted context omitted.
Devices that rely on cloud infrastructure should be required to carry an expiration date right on the box. "This item guaranteed to receive support until XX/XX/XX"
I prefer to have an e-waste law that says that if you stop maintaining the service, you have to open-source it :)
Wow, what a contemptuous statement.
I have news for you, Chamberlain Group. You are not only alienating, being hostile and losing a "Small percentage of users" (most companies would prefer to call them "valued customers", but I get it). You are causing an enormous permanent damage to your own brand.