Problem with HA Integration - Offline if off

Hi all,

having a bit of an issue with Diyhue+Home Assistant at the moment, which prevents me from using it currently.

When configured, all of my lights appear as offline, all of those lights are working within HA jut fine.
All of the HA lights appear offline, it seems to be that when the lights are off, they are offline:

2023-11-29 12:48:08,187 - services.stateFetch - INFO - start lights sync
2023-11-29 12:48:08,187 - services.stateFetch - WARNING - Kitchen is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,188 - services.stateFetch - WARNING - Living Room is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,188 - services.stateFetch - WARNING - Lamp is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,188 - services.stateFetch - WARNING - Bathroom is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,188 - services.stateFetch - WARNING - Upstairs is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,188 - services.stateFetch - WARNING - Bedroom is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,188 - services.stateFetch - WARNING - Entrance is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,188 - services.stateFetch - WARNING - Light: Kitchen Main is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,189 - services.stateFetch - WARNING - Living Room Light 4 is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,189 - services.stateFetch - WARNING - Living Room Light 5 is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,189 - services.stateFetch - WARNING - Living Room Light 3 is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,189 - services.stateFetch - WARNING - Living Room Light 2 is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,189 - services.stateFetch - WARNING - Entrance Light is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,189 - services.stateFetch - WARNING - Bedroom Light 1 is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,189 - services.stateFetch - WARNING - Bedroom Light 2 is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,189 - services.stateFetch - WARNING - Stairs Light is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,189 - services.stateFetch - WARNING - Bathroom Light is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,189 - services.stateFetch - WARNING - Lamp Light 3 is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,189 - services.stateFetch - WARNING - Lamp Light 2 is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,189 - services.stateFetch - WARNING - Lamp Light 1 is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,190 - services.stateFetch - WARNING - Kitchen Light 2 is unreachable: ‘NoneType’ object is not subscriptable
2023-11-29 12:48:08,190 - services.stateFetch - WARNING - Living Room Light 1 is unreachable: ‘NoneType’ object is not subscriptable

It looks like this has to do with the Null values within the HA entities.

Any ideas?

I am experiencing the exact same error in my logs.
Zigbee lights still works flawless on ZHA in HA but trying to use DiyHue and Hue Essentials is unusable at this point or extremely unstable.
Nothing has changed except HA updates a few days ago. HA 2023.11.3

So not really sure what to troubleshoot. Reinstalled DiyHue multiple times but as soon as you add any lights it starts misbehaving.

Something must have changed between DIYHue and HA, but i’ve got no idea what, i’m no programmer :slight_smile:

There seem to be several reports of this now, but no fix as of yet.

When the lights do ‘work’ for me, i can turn them on and off, and only adjust the colour via the hue elements preconfigured scenes, brightness and colour control do not work at all.

Where did you see other reports of this issue? Your post with your logs is the first time that I came across someone mentioning this. Didn’t see any mention on the GitHub Issues tab.

(I commented in this one), but there are two others with the same issue

I think there are more, but there you go

Ah thank you.
Sadly doesn’t look like a possible fix is coming anytime soon. :cry:

You never know, unfortunately it’s completely unusable for me right now, but it’s not critical for my setup, was just a nice to have,

If anyone wants me to do anything specific, i’ll follow through