Hue bridge unreachable since last update

Hello there,
I’m using Hass.io on my raspberry pi 3 without any issues for months.

I have many things : 2 hue bridges, arlo, zwave devices, car, tado, etc…

Everything was running smoothly on 0.98 so far. Yesterday I have updated to 0.101.1 and now I’m having issues with hue sensors :frowning:

The log says my hue bridges (both of them) are unreachable. Lights are working but all of my motion sensors are marked as unavailable (6 sensors)

I tried to restart many times, sometimes the sensors appears, then disappear, and so on every 5 seconds.

Bridges are on static ip and accessible on hue app and everywhere else it can be seen.

Don’t know if it helps but all the recorder events are stored on a SQL database on a separate server. The Pi do not seems « overwhelmed » in any ways.

Someone else having this issue?

Little update,
I tried to remove the integration on one of my bridge et re-adding it (removed, restarted, added without discovery)

Issue is the same, lights are ok, but motion sensors switch every 5 seconds to unavailable.

I can control the lights (on/off/color, etc…), the issue is only with motion sensors.

EDIT:
I have downgraded first to 0.98 and issue is resolved, then updated to 0.100.3 and still no issue, I think there is a problem with the 0.101.1 update

Hi,

Glad I’ve found this - just upgraded from 100.3 to 101.1 and the temp and light levels are no longer available for the sensors on just one of my two bridges.

Didn’t think I’d seen anything in the release notes regarding hue-related chnages though.

Going to try going back to 100.3 to see if it comes back to life…

OK…strange…

Having gone back to 100.3 the missing sensors returned - with all their values but more anoyingly the ones that were working with 101.1 are now all showing ‘Unknown’ for their values…

Haven’t a clue what to do now…

Well another strange thing… even if my sensors are back and working well, I still have the Bridge unreachable error in the logs sometimes