71–80 of 153 posts
Stop buying smart home shit. People warned of exactly this when they started.
It's not the light bulb's API versioning that's the problem - it's that the fucking bulb has an internet connected API in the first place.
So, Philips Hue users need a new $60 bridge after 8 years? That actually seems reasonable to me. 8 years is longer support than most other devices.
Imagine you are designing the web server for some hardware like this. You might write it in Go, dockerized and hosted it in Kubernetes in Google Cloud. You might use a hosted mongo db and 3rd party auth service. Now in 30 years time, Google Cloud will probably no longer exist, your database API will have changed beyond recognition, and your auth service has closed down. IPv4 no longer exists and your hardware depends…
AFAIK the bulbs are compatible with v1 and v2 hubs, so the bulbs do not need to be replaced. The v1 hubs will continue to work across a local area network. Philips offered a heavily discounted upgrade for v1 hub users to get a new v2 hub. However, I still think they should support the v1 hubs for the lifespan of a typical bulb (15 years), at minimum.
Yea, as long as it works locally and they don't pull the old app .. still it's shitty they're trying to push people to buy new shit they don't need. It's just creating waste to increase sales. The attempt to grow without responsibility really needs to die. Consumerism with the goal of more consumerism is a cancer.
This is also a more likely explanation if you consider that Philips offered heavily discounted v2 bridges to v1 bridge owners. It's probable that it's cheaper to Philips to sell v2 upgrades to customers at or below cost than it is to maintain support for the v1 bridge.
Having said that, it sucks for v1 owners that they have a product that's going to lose features unless they upgrade. I do have a few Hue bulbs (with a v2 bridge), but I have everything set up through openHAB, with remote access going through a server I control. This way I don't have to rely on anyone but my VPS provider to keep all of it functional. Unfortunately this route is out of most people's technical know-how. And I certainly sympathize with people who could do this, but would rather use an off-the-shelf product that just works.
Earlier quoted context omitted.
> IPv4 no longer exists I hope you're right, but i'm not entirely convinced. IPv4 has proven to very resilient. A survey in Denmark of pretty much all ISPs reveals that most, if not all, of the large ISPs have absolutely no plans for migrating to IPv6. Not as "not right now", but as "no plans at all". Some of them have plans for migrating business customers, but no plans for residential. We'll end up with companies r…
What actually is a 4to6 gateway? For example, how would an IPv4 client connect to a 128-bit address like 2606:4700:20::6819:6c0d?
If you have a lan then you can set up radvd (or similar) to distribute addresses. You may need to replace your router though.
Your ipv6 packets head out over a 4to6 tunnel to your broker, and then out to the wider world.
Earlier quoted context omitted.
If you don't connect it to the internet, all TVs are dumb.
At least until TV manufacturers start having them try and connect to open wifi points or try and piggy back off of a connection thru HDMI ARC.
Earlier quoted context omitted.
> IPv4 no longer exists I hope you're right, but i'm not entirely convinced. IPv4 has proven to very resilient. A survey in Denmark of pretty much all ISPs reveals that most, if not all, of the large ISPs have absolutely no plans for migrating to IPv6. Not as "not right now", but as "no plans at all". Some of them have plans for migrating business customers, but no plans for residential. We'll end up with companies r…
What actually is a 4to6 gateway? For example, how would an IPv4 client connect to a 128-bit address like 2606:4700:20::6819:6c0d?
I can imagine this to be extremely fragile and break whenever an IP address is looked up using any different manner than plain DNS (e.g. by having IP in API responses, or just using DoH). Yet, I can imagine someone's probably already working on this abomination.
Earlier quoted context omitted.
At least until TV manufacturers start having them try and connect to open wifi points or try and piggy back off of a connection thru HDMI ARC.
Or embed a $2 3g dongle.
And then there's obsolescence: you said 3G... how long before carriers have shut down their 3G networks, or at least have reduced coverage to the point where it's hard to get a 3G connection in most places?
Granted, if the manufacturers only use that as a backup, since most customers probably will connect the TV to their wifi, maybe it won't cost that much.
So, Philips Hue users need a new $60 bridge after 8 years? That actually seems reasonable to me. 8 years is longer support than most other devices.
Yup, and the old bridge will keep working locally, still has an open API, and there was an upgrade program when v2 was introduced, with a 33% discount. Four or so years ago.