Cannot connect Hue Resonate and Hue Outdoor Sensor to OH4.1.0

tonus · May 20, 2024, 8:09pm

So far, I had only a Tradfri E27 bulb connected to OH 4.1.0 on my Pi (actually an HA Yellow with a RPi4 compute module) using an Ember based Zigbee module. That works fine.

But trying to connect the Philips Hue Resonate Outdoor lamp and the Philips Outdoor Sensor did not work out. In the UI, they are reported as Generic Zigbee device which are offline. I’d like to do it directly to the Pi, not via a Hue bridge.
Has anyone established those HUE devices directly to OH4 ?

I read not much issues about connecting Hue devices directly to OH on this forum. That could mean nobody is doing it, or nobody has issues

When scanning, the logfile reports that it found some device, but also:

Node discovery not complete

Here is the log for the mains powered outdoor lamp:

18:30:51.309 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Starting ZigBee scan for zigbee:coordinator_ember:bf79f974a7
18:31:41.035 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 60B647FFFEB01BCC: Polling 1 channels
18:31:41.036 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 60B647FFFEB01BCC: Polling zigbee:device:bf79f974a7:60b647fffeb01bcc:60B647FFFEB01BCC_1_dimmer
18:31:47.679 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 001788010D1DE481: Starting ZigBee device discovery
18:31:47.681 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - 001788010D1DE481: Creating ZigBee device zigbee:device with bridge zigbee:coordinator_ember:bf79f974a7
18:31:47.694 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zigbee:device:bf79f974a7:001788010d1de481' to inbox.
18:31:47.696 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - 001788010D1DE481: Node discovery not complete
18:31:47.929 [DEBUG] [ding.zigbee.internal.ZigBeeDataStore] - 001788010D1DE481: ZigBee saving network state complete.
18:32:01.840 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010D1DE481: Initializing ZigBee thing handler zigbee:device:bf79f974a7:001788010d1de481
18:32:01.843 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010D1DE481: Coordinator status changed to ONLINE.
18:32:01.844 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010D1DE481: Coordinator is ONLINE. Starting device initialisation.
18:32:01.858 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010D1DE481: Node has not finished discovery

and something later:

18:53:31.444 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010D1DE481: Polling initialised at 1921401ms
18:53:31.445 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010D1DE481: Node updated - ZigBeeNode [state=ONLINE, IEEE=001788010D1DE481, NWK=DC01, endpoints=[]]
18:53:31.460 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010D1DE481: Node has not finished discovery
18:53:31.710 [DEBUG] [ding.zigbee.internal.ZigBeeDataStore] - 001788010D1DE481: ZigBee saving network state complete.

When trying to connect the Hue Outdoor (movement) sensor, I got this logfile:

18:53:14.661 [INFO ] [bee.discovery.ZigBeeDiscoveryService] - 001788010CDB2EAB: Starting ZigBee device discovery
18:53:14.662 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - 001788010CDB2EAB: Creating ZigBee device zigbee:device with bridge zigbee:coordinator_ember:bf79f974a7
18:53:14.666 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zigbee:device:bf79f974a7:001788010cdb2eab' to inbox.
18:53:14.668 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - 001788010CDB2EAB: Node discovery not complete
18:53:14.913 [DEBUG] [ding.zigbee.internal.ZigBeeDataStore] - 001788010CDB2EAB: ZigBee saving network state complete.
18:53:30.433 [DEBUG] [ding.zigbee.internal.ZigBeeDataStore] - 001788010CDB2EAB: ZigBee saving network state complete.
18:53:45.960 [DEBUG] [ding.zigbee.internal.ZigBeeDataStore] - 001788010CDB2EAB: ZigBee saving network state complete.

My hardware is not very standard. Could that be the issue? Should I try a mainstream Zigbee connector, for instance a Conbee or so ?
Or is something else going on?

The hardware is not broken, it works fine directly on a Hue Bridge.

rpwong · May 27, 2024, 8:54pm

I don’t use HUE devices, but suggest that you check the Zigbee2mqtt database to see if your devices are in it. If so, try running Z2M to see if you can connect to them. That won’t cost you anything.

Note that you’ll need to disable your Zigbee Binding controller thing. It can’t run at the same time as Z2M.

tonus · October 19, 2024, 3:54pm

I finally solved this. It had to do with the highly unsual configuratiojn to be honest…

The Zigbee controler (EFR32MG21), which is built into the Home Assistant Yellow, has 3 modes:

Only Zigbee
Thread controller
Multiprotocol: that is combined Zigbee and Thread (this is experimental, but it it the default mode as wel).

Although some Hue lamps appear to work in the multiprotocol mode, aparantly some DO NOT work.

So, when I switched back to Zigbee mode only, the Philips Hue Resonate outdoor lamp was discovered easily (even using the old firmware 6.something, whereas 7.something is possible now).`

See this link how to switch that: Disable multiprotocol support – Home Assistant Yellow It requires going back to Home Assisant, and follow this guide. It is perhaps possible to do this without Home Assistant, but I couldn’t find the tools for switching the protocol and updating the firmware from the commandline. I should be possible, I suppose.

So, the experimental multiprotocol mode, was the problem here.
For the record, I tested it with OpenHab 4.2.2.