Zigbee binding

[jimo (Jim)]

I tried the CP210x USB to UART Bridge VCP Drivers from silabs but I couldn’t find one that would work with my stick.

The windows 10 driver was very hard to find. The company that makes the driver has changed names a couple of times. The current version is buried in this installation:
http://www.axialcontrol.com/download/downloadlist
The file you need is:
C:\Program Files (x86)\AxialControl.com\Axial Server\drivers\hubz\HUBZ_VCP_Installer_x64.exe

You have to install the driver manually. The Axial Server will try to install but will fail with a cryptic and useless message. Windows 10 won’t let you install it because it is unsigned. You have to go through a manual process to let windows 10 install unsigned drivers and install this one by hand.

Once installed you should see the zwave controller on one COM port and the zigbee controller on another COM port.

[jimo (Jim)]

I ran the zsmartsystems zigbee code from inside eclipse. I had to reduce the baud rate before it would talk to the zigbee controller but it did eventually spit out a bunch of log messages about the controller. It seemed to be able to communicate with it but I haven’t dug any deeper yet.

[chris (Chris Jackson)]

@TheNetStriker

Assuming bootloader is running and sending magic byte 0x01

This is an issue in the binding - it should now be fixed. The binding was setting the magic byte to 1 and not fe, but it’s not linked to the library.

Fix CC2531 magic number configuration

Let me know if it helps or not…

[chris (Chris Jackson)]

@jimo

I had to reduce the baud rate

Care to elaborate ;). What rate was required?

[jimo (Jim)]

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.

[chris (Chris Jackson)]

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 ).

[chris (Chris Jackson)]

FTR…

Add option to configure Ember baud rate

[TheNetStriker (David Masshardt)]

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.

[chris (Chris Jackson)]

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.

[chris (Chris Jackson)]

@curlyel

Is there an option to gather the current status of all channels from time to time or at least at some event (e.g. when a thing came online)?

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…

[AFromD (Arno)]

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.

[5iver (Scott Rushworth)]

Zigbee binding

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 ).

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?

[jimo (Jim)]

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.

[5iver (Scott Rushworth)]

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…

GitHub - openhab/org.openhab.binding.zigbee: openHAB binding for ZigBee

This post may help too…

How to install a SNAPSHOT version of a binding in a OH2b4 installation

For those who struggle with the description. I did the following Install z-wave binding via paper ui go to karaf console and uninstall the binding via console ssh openhab@localhost -p 8081 password is 'habopen’ list the installed bundles: bundle:list ... 184 | Active | 80 | 2.0.0.b4 | openHAB Dashboard UI 185 | Resolved | 80 | 2.0.0.b4 | openHAB Paper UI Theme Fragment, Hosts: 180 186 | Active | 80 | 0.9.10.v20160429-1435 | reflections (wrap) 187 | Acti…

[chris (Chris Jackson)]

@5iver

You got it! I can report that an OOTB HUSBZB-1 is controlling both my zwave and zigbee networks.

Nice one . Thanks for the feedback.

@5iver

Question: In the PaperUI, the bulb Things have switches for Enable Join and Leave Network. How would they be used?

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.

[5iver (Scott Rushworth)]

@chris

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?

[chris (Chris Jackson)]

@5iver

Does this mean I can start discovery from that bulb to expand the mesh from it?

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…

@5iver

does that mean the discovery from the controller will only include devices it can reach?

No.

When you enable discovery through HABmin / PaperUI, it will enable join on all routers - not just on the controller.

[5iver (Scott Rushworth)]

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.

[chris (Chris Jackson)]

@5iver

Is the energy metering yet to be implemented in the bindin

Yes - I’ll add it soon.

@5iver

Is this a normal message or something to be concerned about?

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.

@5iver

My rooted Wink hub has now gone to pasture.

Your dongle seems quite a nice option so I’m quite pleased it’s working well .

[5iver (Scott Rushworth)]

@chris

Your dongle seems quite a nice option so I’m quite pleased it’s working well .