Not picking up all Hue accessories

[jdshkolnik]

I have 2 Hue bridges at home. It's been working fine for a while but, in the last week or two, this plugin has stopped picking up all the accessories from one of the bridges. It's all the same config yet it gets all 9 sensors upstairs yet only 1 out of the 5 downstairs. I'm on the latest version of everything.

[jdshkolnik]

I removed both bridges and, when attempting to add, it throws this error:

[ebaauw]

Please post the output of homebridge -D (see Troubleshooting in the README), so I can have a look.

[CooperCGN]

@ebaauw If you remember I had the same problem. I added a new lamp and a new Hue tap yesterday and the problems are back again.
I hope I did the right thing, attached ist the log
log.txt

[ebaauw]

Thanks, @CooperCGN!

I think I have found a bug that the Battery service isn't created when the sensor's config.battery is 0. This would explain both the error and why it disappears spontaneously when restarting homebridge after a while: the Hue bridge has updated the battery value.

Not sure how the Hue bridge works here - I don't have any motion sensors connected to my Hue bridge at the moment. But I could image it initialises config.battery to 0 and waits for the first report from the sensor before updating it. This could be up to two hours for the Hue motion sensor. Would be nice if you can confirm config.battery is/was 0 at the time of the error.

Anyways, I'll improve the error handling during setup, to:

• Log the resource on which homebridge-hue chokes together with the error;
• Continue setup for the remaining resources.

[CooperCGN]

I guess you’re right as just shortly before that happened the Home app told me that the batteries were almost empty on a few devices. I will install the new version today in the afternoon and then see what happens. How can I find out what state config.battery is in?

[ebaauw]

I will install the new version today

v0.5.47

How can I find out what state config.battery is in?

Using the CLIP API debugger on the Hue bridge or with ph.sh:

$ ph_get /sensors/xx/config/battery
100

As of v0.5.47, homebridge-hue should log the full resource in case of an error during setup (incl. config.battery).

[CooperCGN]

OK,now it's getting even more weird. Version 0.5.43 was the one I had installed before. Now with the latest version the service enters a failed state, see attached log.txt. Also attached the dump for the sensors from the bridge and my config.json.
config.txt
log.txt
sensors.txt

[CooperCGN]

Oh I see, I might need to update my homebridge version first
Did it, it's up and running again, sensors are back.

[ebaauw]

Nov 26 13:01:50 raspberrypi homebridge[3077]: Error: The requested platform 'Hue' was not registered by any plugin.

Homebridge throws this error when you try and initialise a platform from config.json for which the plugin wasn't loaded. Typically, the plugin hasn't been installed, or has been installed to the wrong directory. Make sure to install homebridge and homebridge-hue using:

sudo npm -g install homebridge --unsafe-perm
sudo npm -g install homebridge-hue