I suppose I should have said earlier
57600 is the only one that seems to work for me. I found that number in some pdf for the uart chip. Iām looking for it now.
Thanks. I think this UART chip goes a lot higher, but something I noticed earlier is that the Ember chip inside this stick is the EM3581 which doesnāt support USB natively. So, it probably has a fixed UART speed programmed into the NCP code. I tend to use the EM3588 here which has USB internal to the Ember and therefore the baud rate doesnāt matter.
Iāll add an option to change the rate on the Ember.
( and nice find ).
FTRā¦
Iāve just compiled this but still getting the same errors, sorry. I also tried to replace the libās with the oneās from the console app, but that doesnāt help either.
Iām not surprised - as I said earlier I didnāt think it would make any difference as the correct magic byte was already being sent elsewhere.
So, the binding (in theory) should configure a device for automatic reporting - a nice feature of Zigbee (a bit like ZWaves associations). It configures the bulb to send updates automatically rather than having to pollā¦
Unfortunately, it seems that many devices donāt support this - including Hue bulbsā¦ So Iāll have a think about doing some polling which is a little more complicated, but clearly necessaryā¦
I am having this problem as well. Stick stays in the bootloader for a long time, and then Zigbee bindung gives up. I know it is being worked on, just a āme tooā. Would be great if it would work at some point.
You got it! I can report that an OOTB HUSBZB-1 is controlling both my zwave and zigbee networks. The Ember EM35x Coordinator needs the baud rate set to 57600 when it is first created. I tested the others, but the binding would hang and Java would do a core dump when the binding was stopped. The coordinator would need to be deleted at this point. The coordinator stayed in Initializing after it was created, but after a restart it went Online. I have only tested GE Link bulbs. Changing the name of the Thing took them Offline (at least in the UIā¦ it was still controllable), but they went Online after a restart.
Question: In the PaperUI, the bulb Things have switches for Enable Join and Leave Network. How would they be used?
Awesome! I want to try this. Please forgive the newbie questionā¦
How do I get the updated code? Is it as simple as getting the latest OH nightly build snapshot? Or do I have to build something myself and then somehow point my existing OH at some repo to find the new code?
Feel free to point me to existing docs.Thanks for the help.
Yes, itās in the nightly snapshot. Iām using 2.1 release right now, so I just grab it from here (youāll need to uninstall it from the UI, if you have it already, and drop this into Addonsā¦ but make sure you still have the serial bindng)ā¦ https://openhab.ci.cloudbees.com/job/openHAB2-Bundles/lastSuccessfulBuild/artifact/bindings/org.openhab.binding.zigbee/target/org.openhab.binding.zigbee-2.2.0-SNAPSHOT.jar
Or build it from hereā¦
This post may help tooā¦
Nice one . Thanks for the feedback.
If you want it to leave the network, then click leave. If you want to enable inclusion for this router only, then you can click the join button.
This is on the bulb though. Does this mean I can start discovery from that bulb to expand the mesh from it? If so (super cool), does that mean the discovery from the controller will only include devices it can reach?
Yes.
Zigbee inclusion isnāt so simple (wrt Z-Wave)ā¦ You can enable inclusion for each router - a device can join a router that has association enabled and it can join the network this way. Once in the network, the device may rejoin on a different router without join being enabled, so you canāt guarantee that the mesh stays the way you create itā¦
No.
When you enable discovery through HABmin / PaperUI, it will enable join on all routers - not just on the controller.
Thank you for the education! I now have 24 GE Link bulbs and 1 SmartThings Outlet on the network. Iām battling with another bulb that refuses to join. It flashes during discovery, but never shows up in the Inbox. There was another bulb that did this but eventually showed up, so I probably just need to wait. Another bulb joined but is not responding to ON/OFF. WIP.
The SmartThings Outlet came up as CentraLite 4257050-RZHAC. Is the energy metering yet to be implemented in the binding (this device is capable)?
Also, I see a lot of these in the logā¦ the last line of it anyway. Is this a normal message or something to be concerned about?
2017-07-05 16:04:04.000 [AshFrameHandler ] - TX EZSP: EzspSendUnicastRequest [type=EMBER_OUTGOING_DIRECT, indexOrDestination=43726, apsFrame=EmberApsFrame [profileId=0, clusterId=49, sourceEndpoint=0, destinationEndpoint=0, options=[EMBER_APS_OPTION_ENABLE_ROUTE_DISCOVERY, EMBER_APS_OPTION_ENABLE_ADDRESS_DISCOVERY, EMBER_APS_OPTION_RETRY], groupId=0, sequence=253], messageTag=253, messageContents=00 07]
2017-07-05 16:04:04.010 [AshFrameHandler ] - RX EZSP: EzspSendUnicastResponse [status=EMBER_SUCCESS, sequence=200]
2017-07-05 16:04:04.010 [ZigBeeDongleEzsp ] - RX: EzspSendUnicastResponse [status=EMBER_SUCCESS, sequence=200]
2017-07-05 16:04:04.010 [ZigBeeDongleEzsp ] - Unhandled EZSP Frame: EzspSendUnicastResponse [status=EMBER_SUCCESS, sequence=200]
Thank you for this awesome binding! My rooted Wink hub has now gone to pasture.
Yes - Iāll add it soon.
Itās normal - donāt worry about it. At some point Iāll add support for this to improve the system a little more, but I donāt process all messages as many arenāt necessary.
Your dongle seems quite a nice option so Iām quite pleased itās working well .
Here are some NPEs from Karaf. Got it 6 times:
Exception in thread "pool-47-thread-6" java.lang.NullPointerException
at com.zsmartsystems.zigbee.internal.ZigBeeNetworkMeshMonitor.getAssociatedNodes(ZigBeeNetworkMeshMonitor.java:305)
at com.zsmartsystems.zigbee.internal.ZigBeeNetworkMeshMonitor.access$500(ZigBeeNetworkMeshMonitor.java:59)
at com.zsmartsystems.zigbee.internal.ZigBeeNetworkMeshMonitor$2.run(ZigBeeNetworkMeshMonitor.java:233)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Not sure if this one is from this binding. Got it 4 times:
Exception in thread "pool-47-thread-7" java.lang.NullPointerException
After stopping the binding, this comes up:
get_java_var: invalid file descriptor
And then these cycle continuously until OH is shutdown:
Exception in thread "pool-49-thread-703" java.lang.IllegalStateException: Could not update status, because callback is missing
at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.updateStatus(BaseThingHandler.java:388)
at org.openhab.binding.zigbee.handler.ZigBeeCoordinatorHandler.networkStateUpdated(ZigBeeCoordinatorHandler.java:645)
at com.zsmartsystems.zigbee.ZigBeeNetworkManager$3.run(ZigBeeNetworkManager.java:709)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Here is what is in the log at the same time (sorryā¦ wasnāt in debug). The first one repeats many times and the log ends with the last one:
2017-07-05 18:16:08.827 [AshFrameHandler ] - AshFrameHandler IOException:
java.io.IOException
at gnu.io.RXTXPort$SerialInputStream.read(RXTXPort.java:1274)[184:com.neuronrobotics.nrjavaserial:3.12.0.OH]
at com.zsmartsystems.zigbee.dongle.ember.ash.AshFrameHandler$1.run(AshFrameHandler.java:151)[222:org.openhab.binding.zigbee:2.2.0.201707042200]
2017-07-05 18:16:08.828 [AshFrameHandler ] - AshFrameHandler IOException:
java.io.IOException
at gnu.io.RXTXPort$SerialInputStream.read(RXTXPort.java:1274)[184:com.neuronrobotics.nrjavaserial:3.12.0.OH]
at com.zsmartsystems.zigbee.dongle.ember.ash.AshFrameHandler$1.run(AshFrameHandler.java:151)[222:org.openhab.binding.zigbee:2.2.0.201707042200]
2017-07-05 18:16:08.828 [AshFrameHandler ] - AshFrameHandler exception count exceeded
Had a couple of these unhandled exceptions in the console this morning:
Exception in thread "pool-37-thread-245" java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
at java.util.ArrayList$Itr.next(ArrayList.java:851)
at org.openhab.binding.zigbee.handler.ZigBeeThingHandler.nodeUpdated(ZigBeeThingHandler.java:302)
at com.zsmartsystems.zigbee.ZigBeeNetworkManager$11.run(ZigBeeNetworkManager.java:1356)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Iād recommend that you try re-flashing your stick and provide the name of the file that youāre flashing to it. Can you also confirm what hardware config youāre on? I had some issues with VMWare ESXI 6.5 that I resolved through setting the USB to high priority.