61–70 of 153 posts
When I moved my Philips Hue bridge got damaged. Turns out there is no way (and I tried) to get your lightbulbs to reset and attach to a new bridge. Not very happy with Philips Hue, wish there was a better option out there.
you can do a re-pair by typing the bulb's serial number into the app and it will force the bulb to forget it's hub.
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.
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.
When I moved my Philips Hue bridge got damaged. Turns out there is no way (and I tried) to get your lightbulbs to reset and attach to a new bridge. Not very happy with Philips Hue, wish there was a better option out there.
Steps are as follows:
Turn the bulb on for three seconds and then off for three seconds, repeat a few times, then turn it on and it should blink. Turn it off, start the pairing/search process and then turn the bulb back on.
It helps to use a lamp/light switch if you have them somewhere that requires plugging/unplugging to turn off.
declaring that you'll never buy another philips product ever again because they shut off hosted services support for a relatively flawed v1 device -- when a v2 device is available for £25 -- is pretty petulant imo. it will still work on your lan.
i've got 15 hue bulbs and a hue bridge but i don't use any of their cloud services. i control them via zigbee light switches on a raspi running homeassistant paired to the hue hub without any "hue cloud account" or any reliance on internet access or anything of the sort.
i don't know of another mainstream brand who will even begin to allow that without significant vendor lock-in.
Earlier quoted context omitted.
Or maybe they factored in 8 years worth of service?
They market their bulbs as having a 15 year life span.
And even without upgrading the bridge, bulbs will still work just fine with the older one, as long as you are trying to access them on your LAN instead of while you are outside of home. What Philips did here sounds very reasonable to me imo.
my problem with being too critical of this is that hue is very open, very well documented and nothing else is. declaring that you'll never buy another philips product ever again because they shut off hosted services support for a relatively flawed v1 device -- when a v2 device is available for £25 -- is pretty petulant imo. it will still work on your lan. i've got 15 hue bulbs and a hue bridge but i don't use any of…
On top of that, no need for a bridge or base station. They can operate entirely locally with no need for a mother ship if you don't need to control them away from home.
I make pretty heavy use of the UDP API from my local server and help maintain a Go library.
This is abominable, there's literally no reason other than "It costs money to maintain this, and we'd rather make money selling new stuff than support what we already made". I have a v2 bridge, but back when I bought it about 3 1/2 years back, I payed a lot of money for it. It's not an expensive product to manufacture, so I expected that money to go towards supporting it long term. So much for that.
You paid a lot of money for the bridge? It comes with the starter packs? I know a few people with these systems that have v2 bridges piled up at home as it was cheaper to get the starter kits and a bonus bridge than it was to buy the bulbs individually.
The world could seriously use some legislation for hardware devices tied to online (dis)services. Maybe if you can't guarantee that your service stays alive for the lifespan of your hardware product, your product shouldn't have existed in the first place.