Discovery Failed for Zigbee Binding

[ptmuldoon (Paul Muldoon)]

I’v been struggling to get the Zigbee binding working, so thought I would go back to square 1. I have removed my old testing 2.2 binding and have the 2.3 binding installed via paperUI / Habmin. In Karaf it shows the 2.3 and only the 2.3 binding as active.

I have the HUSBZB-1 dual zwave/zigbee stick. Zwave is USB0 and working well. Zigbee is setup as the Ember EM35x on port ttyUSB1 with baud rate of 57600 and shows online in both PaperUI and Habmin.

But when I try to start a discovery, Habmin says “Discovery Failed for Zigbee Binding”

I’ve enabled debug logging and this is what I see when I try to start the discovery

2018-03-20 18:59:10.620 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameAck [ackNum=3, notRdy=false]
2018-03-20 18:59:19.574 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 50137: Node SVC Discovery NetworkAddressRequest returned null
2018-03-20 18:59:19.574 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 7CB03EAA00B0013D: Node SVC Discovery request NWK_ADDRESS failed. Retry 10, wait 8956ms before retry.
2018-03-20 18:59:28.531 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 7CB03EAA00B0013D: Node SVC Discovery running
2018-03-20 18:59:28.531 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: NetworkAddressRequest [0/0 -> 65533/0, cluster=0000, TID=0D, ieeeAddr=7CB03EAA00B0013D, requestType=0, startIndex=0]
2018-03-20 18:59:28.532 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65533/0, profile=0000, cluster=0, addressMode=DEVICE, radius=31, sequence=13, payload=00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:28.532 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EzspSendBroadcastRequest [destination=65533, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY, EMBER_APS_OPTION_RETRY, EMBER_APS_OPTION_ENABLE_ADDRESS_DISCOVERY], groupId=0, sequence=13], radius=31, messageTag=13, messageContents=00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:28.532 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: TX EZSP queue: 1
2018-03-20 18:59:28.532 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - TX EZSP: EzspSendBroadcastRequest [destination=65533, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY, EMBER_APS_OPTION_RETRY, EMBER_APS_OPTION_ENABLE_ADDRESS_DISCOVERY], groupId=0, sequence=13], radius=31, messageTag=13, messageContents=00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:28.533 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameData [frmNum=4, ackNum=3, reTx=false, data=0D 00 36 FD FF 00 00 00 00 00 00 40 11 00 00 0D 1F 0D 0B 00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:28.652 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=3, ackNum=5, reTx=false, data=0D 80 36 00 6A]
2018-03-20 18:59:28.653 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: Frame acked and removed AshFrameData [frmNum=4, ackNum=3, reTx=false, data=0D 00 36 FD FF 00 00 00 00 00 00 40 11 00 00 0D 1F 0D 0B 00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:28.653 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - RX EZSP: EzspSendBroadcastResponse [status=EMBER_SUCCESS, sequence=106]
2018-03-20 18:59:28.653 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspSendBroadcastResponse [status=EMBER_SUCCESS, sequence=106]
2018-03-20 18:59:28.654 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Unhandled EZSP Frame: EzspSendBroadcastResponse [status=EMBER_SUCCESS, sequence=106]
2018-03-20 18:59:28.654 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameAck [ackNum=4, notRdy=false]
2018-03-20 18:59:28.654 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=4, ackNum=5, reTx=false, data=0D 90 45 05 00 00 00 00 00 00 08 01 00 00 6A FF 00 00 00 FF FF 0B 00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:28.657 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - RX EZSP: EzspIncomingMessageHandler [type=EMBER_INCOMING_BROADCAST_LOOPBACK, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=106], lastHopLqi=255, lastHopRssi=0, sender=0, bindingIndex=255, addressIndex=255, messageContents=00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:28.657 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspIncomingMessageHandler [type=EMBER_INCOMING_BROADCAST_LOOPBACK, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=106], lastHopLqi=255, lastHopRssi=0, sender=0, bindingIndex=255, addressIndex=255, messageContents=00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:28.660 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=0/0, profile=0000, cluster=0, addressMode=null, radius=0, sequence=13, payload=00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:28.661 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: NetworkAddressRequest [0/0 -> 0/0, cluster=0000, TID=NULL, ieeeAddr=7CB03EAA00B0013D, requestType=0, startIndex=0]
2018-03-20 18:59:28.661 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameAck [ackNum=5, notRdy=false]
2018-03-20 18:59:29.621 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=5, ackNum=5, reTx=false, data=0D 90 3F 04 FD FF 00 00 00 00 00 00 08 01 00 00 6A 0D 00 00]
2018-03-20 18:59:29.623 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - RX EZSP: EzspMessageSentHandler [type=EMBER_OUTGOING_MULTICAST_WITH_ALIAS, indexOrDestination=65533, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=106], messageTag=13, status=EMBER_SUCCESS, messageContents=]
2018-03-20 18:59:29.624 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspMessageSentHandler [type=EMBER_OUTGOING_MULTICAST_WITH_ALIAS, indexOrDestination=65533, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=106], messageTag=13, status=EMBER_SUCCESS, messageContents=]
2018-03-20 18:59:29.624 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Unhandled EZSP Frame: EzspMessageSentHandler [type=EMBER_OUTGOING_MULTICAST_WITH_ALIAS, indexOrDestination=65533, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=106], messageTag=13, status=EMBER_SUCCESS, messageContents=]
2018-03-20 18:59:29.624 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameAck [ackNum=6, notRdy=false]
2018-03-20 18:59:38.533 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 50137: Node SVC Discovery NetworkAddressRequest returned null
2018-03-20 18:59:38.534 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 7CB03EAA00B0013D: Node SVC Discovery request NWK_ADDRESS failed. Retry 11, wait 15673ms before retry.
2018-03-20 18:59:54.208 [DEBUG] [internal.ZigBeeNodeServiceDiscoverer] - 7CB03EAA00B0013D: Node SVC Discovery running
2018-03-20 18:59:54.208 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX CMD: NetworkAddressRequest [0/0 -> 65533/0, cluster=0000, TID=0E, ieeeAddr=7CB03EAA00B0013D, requestType=0, startIndex=0]
2018-03-20 18:59:54.209 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - TX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=65533/0, profile=0000, cluster=0, addressMode=DEVICE, radius=31, sequence=14, payload=00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:54.209 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EzspSendBroadcastRequest [destination=65533, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY, EMBER_APS_OPTION_RETRY, EMBER_APS_OPTION_ENABLE_ADDRESS_DISCOVERY], groupId=0, sequence=14], radius=31, messageTag=14, messageContents=00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:54.212 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: TX EZSP queue: 1
2018-03-20 18:59:54.213 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - TX EZSP: EzspSendBroadcastRequest [destination=65533, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY, EMBER_APS_OPTION_RETRY, EMBER_APS_OPTION_ENABLE_ADDRESS_DISCOVERY], groupId=0, sequence=14], radius=31, messageTag=14, messageContents=00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:54.213 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameData [frmNum=5, ackNum=6, reTx=false, data=0E 00 36 FD FF 00 00 00 00 00 00 40 11 00 00 0E 1F 0E 0B 00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:54.332 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=6, ackNum=6, reTx=false, data=0E 80 36 00 6B]
2018-03-20 18:59:54.332 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: Frame acked and removed AshFrameData [frmNum=5, ackNum=6, reTx=false, data=0E 00 36 FD FF 00 00 00 00 00 00 40 11 00 00 0E 1F 0E 0B 00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:54.333 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - RX EZSP: EzspSendBroadcastResponse [status=EMBER_SUCCESS, sequence=107]
2018-03-20 18:59:54.333 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspSendBroadcastResponse [status=EMBER_SUCCESS, sequence=107]
2018-03-20 18:59:54.334 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Unhandled EZSP Frame: EzspSendBroadcastResponse [status=EMBER_SUCCESS, sequence=107]
2018-03-20 18:59:54.334 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameAck [ackNum=7, notRdy=false]
2018-03-20 18:59:54.334 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=7, ackNum=6, reTx=false, data=0E 90 45 05 00 00 00 00 00 00 08 01 00 00 6B FF 00 00 00 FF FF 0B 00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:54.335 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - RX EZSP: EzspIncomingMessageHandler [type=EMBER_INCOMING_BROADCAST_LOOPBACK, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=107], lastHopLqi=255, lastHopRssi=0, sender=0, bindingIndex=255, addressIndex=255, messageContents=00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:54.335 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspIncomingMessageHandler [type=EMBER_INCOMING_BROADCAST_LOOPBACK, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=107], lastHopLqi=255, lastHopRssi=0, sender=0, bindingIndex=255, addressIndex=255, messageContents=00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:54.335 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX APS: ZigBeeApsFrame [sourceAddress=0/0, destinationAddress=0/0, profile=0000, cluster=0, addressMode=null, radius=0, sequence=14, payload=00 3D 01 B0 00 AA 3E B0 7C 00 00]
2018-03-20 18:59:54.336 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - RX CMD: NetworkAddressRequest [0/0 -> 0/0, cluster=0000, TID=NULL, ieeeAddr=7CB03EAA00B0013D, requestType=0, startIndex=0]
2018-03-20 18:59:54.336 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameAck [ackNum=0, notRdy=false]
2018-03-20 18:59:55.314 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - <-- RX ASH frame: AshFrameData [frmNum=0, ackNum=6, reTx=false, data=0E 90 3F 04 FD FF 00 00 00 00 00 00 08 01 00 00 6B 0E 00 00]
2018-03-20 18:59:55.317 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - RX EZSP: EzspMessageSentHandler [type=EMBER_OUTGOING_MULTICAST_WITH_ALIAS, indexOrDestination=65533, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=107], messageTag=14, status=EMBER_SUCCESS, messageContents=]
2018-03-20 18:59:55.318 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - RX: EzspMessageSentHandler [type=EMBER_OUTGOING_MULTICAST_WITH_ALIAS, indexOrDestination=65533, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=107], messageTag=14, status=EMBER_SUCCESS, messageContents=]
2018-03-20 18:59:55.318 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - Unhandled EZSP Frame: EzspMessageSentHandler [type=EMBER_OUTGOING_MULTICAST_WITH_ALIAS, indexOrDestination=65533, apsFrame=EmberApsFrame [profileId=0, clusterId=0, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY], groupId=0, sequence=107], messageTag=14, status=EMBER_SUCCESS, messageContents=]
2018-03-20 18:59:55.319 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameAck [ackNum=1, notRdy=false]

[chris (Chris Jackson)]

The log isn’t really related to discovery, so I’m not sure what I can comment on - sorry. I’m happy to look at a log if you have something to look at. I’d suggest to enable discovery, then reset whatever device you are trying to add.

It would also be worth providing some information about what device you’re adding.

[ptmuldoon (Paul Muldoon)]

I’ve been trying to add some Lightify RGBW bulbs, 1 of them is a A19 bulb, and the others are the Lightify Recessed RGBW bulbs.

I also have 2 older GE Link bulbs. But so far with the 2.3 binding I’m stuck trying to get anyone to pair up.

I just thought to pull the Stick out of the server/box, reboot it and replug back in and see what happens. I know I can control the Zwave side of things on the dual stick. So not sure if its the Stick, my OH2 settings, or something else.

But I’ll keep working at it, and see what happens.

And I really with Lightify would make their USA bulbs compatible with Hue. It would make things so much easier. I hate the Lightify Bridge and App, yet forced to use with their bulbs till I get OH2 to take these over.

So after a reboot, and readding the stick, I still get the same error. I guess I could try and revert back to the 2.2 binding and see if same occurs?

[chris (Chris Jackson)]

I think there was a change recently with the discovery service in ESH that broke things. While I’m not 100% sure, I think if you’re using a recent binding with an older runtime, or vice-versa, then this is what happens. You probably need to update your runtime to the latest (ie from this week) to solve this, or change back to an older binding from a few weeks ago.

Zigbee binding

@chris, I’m not sure where the other issues got to, but I opened one here. Discovery fails after the latest ESH changes.

[5iver (Scott Rushworth)]

@chris

I think there was a change recently with the discovery service in ESH that broke things.

As of right now, it is still broken. The Zigbee binding has not had a new build since March 16th, so if a rebuild is going to fix it, that hasn’t happened yet. I’m on 1232. Chris, can you kick off the builds?

[chris (Chris Jackson)]

Ok, I didn’t check but I’d assumed that a rebuild had been done after the breaking change. I’ll kick this off in a few minutes.

[5iver (Scott Rushworth)]

Same error on 2.3.0.201803211535 and 1232.

[chris (Chris Jackson)]

Damn. I’ll try and look at this over the coming days. Since the binding has not changed I can only assume the problem is with the ESH change

[5iver (Scott Rushworth)]

It’s odd that @Kai reported that he did not get the error (and then closed the issue ).

[chris (Chris Jackson)]

I see from the report that Kai probably just ran the binding - here we have issues starting discovery which tells me that the binding started, but the problem was later, so maybe the issue is elsewhere.

I see you’ve not raised the issue against the binding either, but against another repo that Kai has created (I was wondering why you put #1 wahoo in the issue - now I know).

[5iver (Scott Rushworth)]

I did my normal search to find the issues list, opened the issue, and that was what came up. Whta’s with the new repository? I recreated it in the correct location. I just tested with the REST API and it gives the same error and returns 500.

[ptmuldoon (Paul Muldoon)]

Thought I would check back based on your guys expertise above.

I am running java 1.8.0_161 on the current latest OH2 build 1238. And it sounds like the zigbee 2.3 binding may not work with this java version?

And if you want to discover new zigbee devices with the latest OH2 build, we should stick with the 2.2 binding?

Do I have that correct or did I confuse myself?

[5iver (Scott Rushworth)]

There was something included in the last ESH updates that broke Zigbee discovery. TMK, it has nothing to do with Java version, but I’ll play with that tonight… currently using OpenJDK Runtime Environment (build 1.8.0_141-b16). Downgrading the binding might be messy. I’m sure Chris will make quick work of it this weekend!

Issue: Expected static field org.openhab.binding.zigbee.discovery.ZigBeeDiscoveryService.scheduler

[chris (Chris Jackson)]

@5iver

I’m sure Chris will make quick work of it this weekend!

Don’t bank on it - sorry. I don’t think there is anything I can do to resolve this - I’m not experiencing the issue here with the refactored source, and it’s quite a lot of work to change the workspace to the old system. I’ve not changed any source code to make it work, so if I spent the time to change everything back, I can’t see that there’s anything I can change (and Kai said it was source compatible, which is consistent with what I’m seeing at least).

I just spent some time to understand the issue, and indeed, there can be no change in the binding source, so a recompile should resolve this. If it isn’t, then I guess somewhere there is an inconsistency between your OH/ESH runtime, and the binding (and I know you’ll probably say that’s not the case, so at this point I’m out of suggestions).

So, I’m not sure what I can do to resolve this .

[ptmuldoon (Paul Muldoon)]

So…

I run OH2 as a VM within ESXi.

Today I set up fresh Ubuntu VM install, installed OH2 and then moved my HUSBZB-1 stick over to the new VM. Added the user openhab to dialout and tty, and then installed the zigbee binding via PaperUI.

Result… Discovery seems to work. At least I did not receive the failed message. I still need to reset a lightbulb and try and pair it, but again no error.

So that leads to believe something in my existing OH2 Ubuntu install? But unsure yet where to begin looking to troubleshoot that.

So like Chris said, their is probably nothing wrong with the binding and just need to identify what else could be causing the error.

[ptmuldoon (Paul Muldoon)]

Ugh… Now I get the failed message on my test VM machine

And all I did was try and pair an Osram Lightify bulb. All I can possible think is that I tried to pair via PaperUI vs Habmin, and I was also doing it via my phone, vs an actual PC web browser. Not that either should make a difference.

The light flashed 4 times like it paired but never showed in OH2, and now gives the failed message again during discovery.

So now I’m back to guessing why I get the error. 2 separate VM’s and installs, and got the error on both.

[5iver (Scott Rushworth)]

I just tested with Zulu (was previously using straight openJDK) and it made no difference. I had two bulbs that I had unpaired and that’s when the issue started. I also get the error on a perfectly fresh manual install with the binding in addons. Same error starting discovery though the REST API too. Do you also see the exceptions in the Karaf console? They come up for me soon after startup, without the long nasty exceptions in the log. And there are two of them, and two exceptions in the log, and I had removed two bulbs.

[ptmuldoon (Paul Muldoon)]

@5iver

Do you also see the exceptions in the Karaf console?

How would I go about checking and seeing the exceptions in the Karaf console?

Also, are you using the same dual Zwave/Zigbee HUSBZB-1 stick? Perhaps an issue with the stick itself? I can try and reset the stick before trying again and see what happens.

[chris (Chris Jackson)]

@ptmuldoon

Perhaps an issue with the stick itself?

It’s not an issue with the stick. The issue is with the change of class in ESH so it won’t be dependent on hardware.

I did a fresh install this morning and also found no issues - it just seems to be you @5iver .

[5iver (Scott Rushworth)]

@ptmuldoon

How would I go about checking and seeing the exceptions in the Karaf console?

https://docs.openhab.org/administration/console.html
or

openHAB VS Code Extension 0.3.5

What’s new Fixed issues with non-root workspaces (#62) Fixed issues with REST connection (#58) Added some Type Conversion snippets (#60) Added ‘Open Karaf console’ feature (#59) Optionally open Classic UI for sitemap preview (#54) Quick Karaf console access demo [image] Installation This extension is available on the Visual Studio Marketplace -> https://marketplace.visualstudio.com/items?itemName=openhab.openhab You can also install it manually: Download openhab-0.3.5.vsix on your hard dr…

@ptmuldoon

Also, are you using the same dual Zwave/Zigbee HUSBZB-1 stick?

Yep

@chris

I did a fresh install this morning and also found no issues

Which version of Java and which OS?