Hue Light Sensors - HANDLER_CONFIGURATION_PENDING

Add-ons Bindings
1

I have three Hue motion/illuminance sensors. Running OpenHABian on milestone builds.

All three Things periodically go into HANDLER_CONFIGURATION_PENDING state. The related things for temp and motion do not experience this issue, and all three go into this state at the same time (I believe). Rebooting the bundle, service or system doesn’t resolve the incident. Only removing and re-adding the thing does:

events.log

2022-03-04 08:41:55.332 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:001788462822:123' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING): Missing or invalid configuration.
2022-03-04 09:03:49.661 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:001788462822:123' changed from UNINITIALIZED (HANDLER_CONFIGURATION_PENDING): Missing or invalid configuration. to UNINITIALIZED
2022-03-04 09:03:49.689 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:001788462822:123' changed from UNINITIALIZED to UNINITIALIZED (DISABLED)
2022-03-04 09:03:51.679 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:001788462822:123' changed from UNINITIALIZED (DISABLED) to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING): Missing or invalid configuration.
2022-03-04 09:14:58.261 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:001788462822:123' changed from UNINITIALIZED (HANDLER_CONFIGURATION_PENDING): Missing or invalid configuration. to REMOVING
2022-03-04 09:14:58.263 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:001788462822:123' changed from REMOVING to REMOVED
2022-03-04 09:14:58.272 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:001788462822:123' changed from REMOVED to UNINITIALIZED
2022-03-04 09:14:58.281 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:001788462822:123' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2022-03-04 09:15:14.659 [INFO ] [openhab.event.InboxAddedEvent       ] - Discovery Result with UID 'hue:0106:001788462822:123' has been added.
2022-03-04 09:15:21.469 [INFO ] [openhab.event.InboxRemovedEvent     ] - Discovery Result with UID 'hue:0106:001788462822:123' has been removed.
2022-03-04 09:15:21.477 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:001788462822:123' changed from UNINITIALIZED to INITIALIZING
2022-03-04 09:15:21.502 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:001788462822:123' changed from INITIALIZING to ONLINE

openhab.log

2022-03-04 09:15:14.659 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'hue:0106:001788462822:123' to inbox.
2022-03-04 09:15:21.491 [DEBUG] [ue.internal.handler.HueSensorHandler] - initializeThing thing hue:0106:001788462822:123 bridge status ONLINE

I believe this started with 3.2.0 (not 100% sure) but has persisted with 3.3.0M1 and 3.3.0M2.

I’ve turned on debugging for the hue bundle but can’t seem to find anything - maybe I should be logging against a different bundle?

2

It started with 3.3.0-M1 and is not solved with 3.3.0-M2 - I am also waiting for a solution to this problem

3

Good to know I’m not alone, I guess!

Happy to test any resolutions if necessary!

4

Are you sure it is not the same?

At least this is solved in M2. In my configuration the issue was:

ledindication: false

With every restart it was a number again instead of “true” or “false”. Please check code in Thing configuration. If it is not solved for you maybe it helps to uninstall/install binding or clean cache.

5

That sounds the same to me. My troubleshooting may have been flawed.
In my case, when I updated from M1 to M2 they came back as HANDLER_CONFIGURATION_PENDING and I recreated them. I’ll see if since re-creation they stay in an ONLINE state.

Thanks for pointing this out.

6

Hi - I believe I am experiencing just the same issue. Is this meanwhile resolved, and what do I have to do to get it solved?

7

I think I had to recreate the things… but it may have been solved in an update.

1 Like
8

Recreating things also solved the issue for me. Should be integrated into the breaking changes docs.