Barry I am having the same issue with my hue bridge.
Under my habridge hue bridge data is shows
- ip: 192.168.1.28
- mac: B827EBEDFDF4
- port: 443
so port needs to be changed from 443 to 80.
How do I do it?
thx
sg
1 Like
Yes, I am using seeing the same issue with port: 443. Is this something we can change? Do we need to create a custom modified device handler?
Thanks.
Iāve just read this thread so thought Iād check my Hue Hub and add to the convo.
Looks like itās gone offline and straight back online once per day since 27th so I havenāt noticed it since it was a quick flip flop.
Before the update it was really stable so clearly somethings not quite right.
Hi @Tech_GFam, @HJM we are testing a patch to the locally running handler which is working on my test setup. This fix along with a few others for other identified problems will probably be released sometime in the next several weeks.
4 Likes
Weāre looking into the flip-flop cases. We think this most likely is an accurate reflection of the hue bridgeās āreachableā state for the bulbs but we will still be discussing ways in which we can apply logic to avoid frequent health changes in bulbs when the hue bridge reports the state inconsistently.
2 Likes
I had been using Tasmota Hue Emulation for some reprogrammed Tuya devices. None have worked since the late June timeframe youāve all specified, In my troubleshooting i removed all the original devices and emulated bridges from my IDE to attempt re-adding. ST is still unable to find/add them again. For the most part I just use the Tasmota device handler for these devices, but for any automation where the state of one device directly influences another, hue emulation is required as the Tasmota DTH does not have this ability.
Weeks?
This will seal the fate of the ST hub in my home, Iām going to lose voice control because software was changed without properly testing the impact on the user base.
Do I have that straight?
(Also I canāt apply the workaround because we arenāt allowed access to the device/server side switch)
1 Like
I have been using the Hue Emulation for control of Sonoff 4 channel devices with Tasmota. Since mid June this has all stopped working. Have tried changing the hue device types but refuses to work any more.
Weeks how about letting some of us test it out.
Or how about rolling back the firmware until thereās a fix. And while theyāre at it, implement user control of firmware updates
2 Likes
Both my physical Hue and my HA Bridge are down. I removed and tried to re-add them both and now all my bulbs are gone in addition to showing as offline. I tried installing Hue B Smart for the HA Bridge but it doesnāt work, it gives a network error in the app while the other one shows as offline. Canāt DM the relevant support ppl like Brad. Official support just told me to power cycle the thing which of course did nothing and no response after. Please help.
Same for me, with some Sonoff wifi outlets running Tasmota. It all stopped working in June. I did the same thing you did - removed and then couldnāt re-add. Iāve never been able to make the Tasmota device handler work right so Iāve been using Hue emulation exclusively.
Barry,
I wonder why Tasmota is detected as a V2 hub - according to one of the developers at this Gitlab issue, Tasmota enumerates as āPhilips hue bridge 2012ā which should be V1. I wonder if something about the message Tasmota sends is tripping up the hubās version detection, or if itās only a semi-related issue.
My HA-Bridge (from bwssystems.com ) also started showing as offline with SmartThings Hub v2. I can control my devices via the bridge without issue but SmartThings cannot see the emulated hue hub or any of the respective devices attached to it. Any help would be appreciated!
@ndlessfun DM Barry_Andersen with your ST username and he can change your HA-Bridge from port 443 to port 80 so it will work again for the interim.
https://community.smartthings.com/t/hub-firmware-beta-0-26-12
Patch for hue emulators or older hue bridges which do not support TLS/port 443 is now in external beta so if anyone having this problem is part of the beta already they can give this a go (I have personally tested these changes with an ha-bridge setup as well).
Prod release will likely be out next week barring issues in external beta or other discoveries. You can subscribe to fw update notifications at status.smartthings.com. ATM we arenāt adding more beta participants (but window will probably be open again before the next major release).
2 Likes
FYI, the HA-Bridge has release candidate RC10 that has HTTPS ability with a self signed cert. Both systems working toward compatibility is great to see.
1 Like
Ha bridge working again.
Thsnks
1 Like
No luck on the Tasmota hue bridges unfortunately. ST seems to detect them, but requests that you āpress a button on the hue bridgeā which isnāt possible.