Zigbee binding - no discovery of things

  • Synology on DSM 6.2.2
  • openHab 2.4.0.002
  • ZigBee binding 2.4.0

After changing the ownership on the USB port /dev/ttyACM0 and having a CC2531 USB shown as online in the things section I am not able to find active Zigbee Bulbs (Hue) through PaperUI +

The documentation states: “Once the binding is installed, and an adapter is added, it automatically reads all devices that are set up on the ZigBee controller and puts them in the Inbox”

What kind of adapter is referenced here? Is it the USB stick? Therefore I should be able to find my bulbs right?

Yes, its the USB stick.

Any ideas why the discovery is not working?

The config of the stick thing looks a bit weird in PaperUI

In the thing text config I have this:

Thing zigbee:coordinator_cc2531:stick1 "Zigbee USB Stick" [zigbee_port="/dev/ttyACM0", zigbee_baud=38400, zigbee_panid=35637, zigbee_extendedpanid="118E309DE90CC829", zigbee_networkkey="14 c6 a2 c7 fb e0 c3 19 8e 7c 36 30 dc ad a5 96"]

Sorry - I’m not sure.

What is weird? It looks ok to me I think?

What do you see in the debug logs?

I am just confused because there is no networkaddress for example.

I see only:

2019-09-04 19:39:13.591 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Trying to start 2 scans with an aggregating listener.
2019-09-04 19:39:13.592 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Triggering scan for thing types '[zigbee:bitron-video-av2010-34, zigbee:bitron-video-902010-23, zigbee:smartthings_motionv4, zigbee:philips_sml001, zigbee:xiaomi_lumisensorht, zigbee:innr-rc-110]' on 'ZigBeeDiscoveryService'...
2019-09-04 19:39:13.593 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Starting ZigBee scan for zigbee:coordinator_cc2531:stick1
2019-09-04 19:39:31.607 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Triggering scan for thing types '[zigbee:coordinator_telegesis, zigbee:coordinator_ember]' on 'UsbSerialDiscoveryService'...
2019-09-04 19:39:36.608 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Finished 1 of 2 discovery services.
2019-09-04 19:39:45.983 [DEBUG] [trol.internal.handler.AccountHandler] - checkData amazonechocontrol:account:002c46fc finished
2019-09-04 19:39:46.764 [DEBUG] [trol.internal.handler.AccountHandler] - check login amazonechocontrol:account:002c46fc
2019-09-04 19:39:57.352 [DEBUG] [core.karaf.internal.FeatureInstaller] - Running scheduled sync job
...
2019-09-04 19:40:13.593 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Finished 2 of 2 discovery services.
2019-09-04 19:40:13.593 [DEBUG] [internal.discovery.DiscoveryResource] - Scan for binding 'zigbee' successfully finished.
2019-09-04 19:40:24.188 [DEBUG] [control.internal.WebSocketConnection] - Send Ping
2019-09-04 19:40:24.189 [DEBUG] [control.internal.WebSocketConnection] - Send message with length 98
2019-09-04 19:40:24.334 [DEBUG] [control.internal.WebSocketConnection] - Pong received

Afterwards PaperUI still shows no found items.

Are you triggering discovery?

what does that mean? I am clicking the “+” in the PaperUI and choosing my ZigBee Binding

yes, that is it

OK, super stupid question but the Hue lights are turned on right? (powered on)
Do you not own a Hue hub, only two Hue bulbs correct?
I have a Hue hub and use the Hue binding as well as zigbee binding

Yes they are turned on.

I own a Hue Hub as well and I am able to change the lighting using the Hue App

Not that there would be anything wrong with trying to use your Hue bulbs with your zigbee usb stick, I’ve never tried. I can not confirm if it will work. Hue devices use an enhanced version of zigbee protocol although it is fully compliant with the protocol as I understand it. I just use the Hue binding and it works a treat. It does require the Hue hub have internet access but if you are using the Hue app on your phone, you have already done so.

Yes - there is -:
image

While it probably won’t help, it would be really useful to have debug information enabled so we can see what is happening. Since nothing seems to be discovered, I’m not sure it will add a lot, but I’m not sure. Please take a look at the docs.

What I did was setting the log level to DEBUG in the org.ops4j.pax.logging.cfg. I will check again.

But I think you’ve only done it for the binding didn’t you?

I added this now to the log config:

# Zigbee binding
log:set DEBUG org.openhab.binding.zigbee

output during discovery:

2019-09-04 22:03:20.169 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Trying to start 2 scans with an aggregating listener.
2019-09-04 22:03:20.170 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Triggering scan for thing types '[zigbee:coordinator_telegesis, zigbee:coordinator_ember]' on 'UsbSerialDiscoveryService'...
2019-09-04 22:03:20.253 [DEBUG] [l.internal.UsbSerialDiscoveryService] - Discovered new USB-Serial device: UsbSerialDeviceInformation [vendorId=0x0451, productId=0x16A8, serialNumber=__0X00124B000766CFF7, manufacturer=Texas Instruments, product=TI CC2531 USB CDC, interfaceNumber=0x00, interfaceDescription=null, serialPort=/dev/ttyACM1]
2019-09-04 22:03:20.254 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Triggering scan for thing types '[zigbee:bitron-video-av2010-34, zigbee:bitron-video-902010-23, zigbee:smartthings_motionv4, zigbee:philips_sml001, zigbee:xiaomi_lumisensorht, zigbee:innr-rc-110]' on 'ZigBeeDiscoveryService'...
2019-09-04 22:03:20.255 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Starting ZigBee scan for zigbee:coordinator_cc2531:stick1
2019-09-04 22:03:25.171 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Finished 1 of 2 discovery services.
2019-09-04 22:03:42.113 [DEBUG] [core.karaf.internal.FeatureInstaller] - Running scheduled sync job
2019-09-04 22:04:02.027 [DEBUG] [control.internal.WebSocketConnection] - Send Ping
2019-09-04 22:04:02.028 [DEBUG] [control.internal.WebSocketConnection] - Send message with length 98
2019-09-04 22:04:02.160 [DEBUG] [control.internal.WebSocketConnection] - Pong received
2019-09-04 22:04:06.961 [DEBUG] [trol.internal.handler.AccountHandler] - checkData amazonechocontrol:account:002c46fc finished
2019-09-04 22:04:06.961 [DEBUG] [trol.internal.handler.AccountHandler] - check login amazonechocontrol:account:002c46fc
2019-09-04 22:04:20.255 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Finished 2 of 2 discovery services.
2019-09-04 22:04:20.256 [DEBUG] [internal.discovery.DiscoveryResource] - Scan for binding 'zigbee' successfully finished.

This is still just the binding debug information. We need to see all the debug information as per the binding documentation.

here you go:

log:set DEBUG org.openhab.binding.zigbee
log:set DEBUG com.zsmartsystems.zigbee
log:set INFO com.zsmartsystems.zigbee.dongle.ember.internal.ash

output during discovery:

2019-09-05 08:53:03.993 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Trying to start 2 scans with an aggregating listener.
2019-09-05 08:53:03.995 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Triggering scan for thing types '[zigbee:bitron-video-av2010-34, zigbee:bitron-video-902010-23, zigbee:smartthings_motionv4, zigbee:philips_sml001, zigbee:xiaomi_lumisensorht, zigbee:innr-rc-110]' on 'ZigBeeDiscoveryService'...
2019-09-05 08:53:03.997 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Starting ZigBee scan for zigbee:coordinator_cc2531:stick1
2019-09-05 08:53:04.231 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Triggering scan for thing types '[zigbee:coordinator_telegesis, zigbee:coordinator_ember]' on 'UsbSerialDiscoveryService'...
2019-09-05 08:53:04.316 [DEBUG] [l.internal.UsbSerialDiscoveryService] - Discovered new USB-Serial device: UsbSerialDeviceInformation [vendorId=0x0451, productId=0x16A8, serialNumber=__0X00124B000766CFF7, manufacturer=Texas Instruments, product=TI CC2531 USB CDC, interfaceNumber=0x00, interfaceDescription=null, serialPort=/dev/ttyACM1]
2019-09-05 08:53:09.233 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Finished 1 of 2 discovery services.
2019-09-05 08:53:17.863 [DEBUG] [core.karaf.internal.FeatureInstaller] - Running scheduled sync job
2019-09-05 08:53:41.553 [DEBUG] [trol.internal.handler.AccountHandler] - check login amazonechocontrol:account:002c46fc
2019-09-05 08:53:41.553 [DEBUG] [trol.internal.handler.AccountHandler] - checkData amazonechocontrol:account:002c46fc finished
2019-09-05 08:54:03.998 [DEBUG] [nternal.DiscoveryServiceRegistryImpl] - Finished 2 of 2 discovery services.
2019-09-05 08:54:03.999 [DEBUG] [internal.discovery.DiscoveryResource] - Scan for binding 'zigbee' successfully finished.
2019-09-05 08:54:17.865 [DEBUG] [core.karaf.internal.FeatureInstaller] - Running scheduled sync job

Very strange that even though you’ve apparently added all the debug now, there is still no debug from the zigbee system :confounded:. I’m afraid I’m not sure what is happening without seeing this - sorry.

hm ok.

I was looking forward to remove my Hue bridge.

The documenation states:

Do not use the values for zigbee_networkkey , zigbee_panid and zigbee_extendedpanid from this example, create random values for your own Zigbee network.

I guess this really means random so I just changed some values in these 3 parameters. Or do I need to generate them somehow?

Random is fine.