- GE Link A19 (60W)
- GE Link BR30 (65W)
- GE Link PAR38 (90W)
- CentraLite 4257050-RZHAC plugin smart outlet (Smartthings)
Any idea of Xiaomi devices would work? They are supposed to be Zigbee as well.
This thread has a lot of information on the Zigbee binding, including discussions on currently functioning devices.
No - they are not ZigBee devices. They use part of the ZigBee protocol, but don’t fully support it and this causes problems where the ZigBee stack requires certain functionality.
I’ve been trying to get this to work as well.
Running the 2.2 snapshot: 2.2.0.201708292017
Seems like it’s talking with the coordinator just fine (Baud rate 57600), but the thing still shows ‘INITIALIZING’.
Here’s the debug logs (I also have these logs with AshFrameHandler set to DEBUG):
Set com.zsmartsystems.zigbee to debug and head over here with another log from startup…
Here you go:
Which version of OH are you running? Have you tried setting Reset to true on the coordinator? This should apply the configuration. I haven’t been able to change settings after the initial setup, so you may want to try deleting the coordinator and starting over. There have been a lot of changes to the binding since I first tried to get my HUSBZB-1 setup, and I haven’t tried starting from scratch since, so I don’t have any personal experience with the initial setup using the current binding, but you might find some helpful info in the Zigbee thread.
I’m not really sure why it’s not creating the network. I have a theory, but I’m not really sure it’s right… I’ll probably make a small change to see if it helps and we can take it from there…
@5iver 2.1, but a 2.2 snapshot for the ZigBee binding (2.2.0.201708292017). Yeah, I’ve tried several iterations of remove, restart, re-add (complete with removing the USB device too).
@chris Happy to try whatever.
Thanks!
UDEV rules for this device can be a little tricky. Here is what worked for me (although I specified an order to them):
KERNEL==“ttyUSB[0-9]", ATTRS{interface}==“HubZ Z-Wave Com Port”, SYMLINK+=“ttyUSB-5”, GROUP=“dialout”, MODE="0666"
KERNEL=="ttyUSB[0-9]”, ATTRS{interface}==“HubZ ZigBee Com Port”, SYMLINK+=“ttyUSB-55”, GROUP=“dialout”, MODE=“0666”
Note: On Linux; the extra Java command-line property is not required if you choose a symlink name that matches a standard Linux comm port prefix and ends with a combination of numerics + non-letters. E.g. “ttyUSB-9999”.
2 Likes
Hey,
I’ve just got one of these and though the aeotec backup/restore of my gen5 zstick seems to work. After I plug it into my OpenHAB machine, the binding only ever finds 1 node, not the 60+ nodes that are supposedly in the backup.
I downloaded the zensys tools and it only ever shows the controller node. Is there a special trick for doing the backup/restore?
Nothing special, the backup and restore was straight forward. Hmmm… what was the process. I think I shut the backup tool down after the backup, swapped the sticks, then did the restore. Did you get the latest version of the backup software? I used ZStick G5 BackupToolSetup Ver1.0_0_9 on a Windows 10 laptop. If no nodes are showing after a restore, I would suspect the backup to be the issue. You probably don’t have a spare zstick to test it with, so maybe Aeon Labs support could test it for you to confirm the backup was successful? I’d be willing to do a restore to my spare zstick using your file to see if the devices are in there, but you’re probably and understandably not going to trust a complete stranger from the Internet with your zwave network!
I guess it’s possible Nortek updated something, but I would expect a firmware update available if they had. You could compare the version of the libraries between the zstick and quickstick in Zensys Tools. Mine were identical. This is my zstick:
That is what my zstick looks like, the husbzb-1 has the identical libraries, but it’s z-wave device firmware is 4.05. I’ve tried the backup / restore on a different machine and it the whole process seems to succeed but the husbzb-1 is still un-restored. Does your husbzb-1 have a firmware version of 4.05?
Yes. Did you use the Windows driver or download the one from Silabs?
there doesn’t seem to be a compatible win10 driver inbox or from silabs, I had to get the one from axialcontrol.com (Zigbee binding) to and disable driver signature verification.
The silabs driver doesn’t support my devices PID (USB\VID_10C4&PID_8A2A&MI_00). I’ve tried forcing the silabs driver to install on the port, and though it works fine, the restore still does nothing.
I received a HUSBZB-1 stick on Friday. I also have a Zstick G5 and thus am very interested in this thread.
I will start playing with it tonight.
I do not own any PC or license to Windows (so running VMWare or such is also out of the question).
I only have a Mac desktop and laptop and a headless Intel Linux box.
Is it possible to do the backup-restore on something else than a Windows PC?
(use the one without serial enumeration)
I’m pretty sure I just manually installed the driver instead of running the setup. This is probably the same version as you’re running though. These instructions say to unplug the stick after the restore and plug it in again to initialize changes. Maybe you’re missing that step? The only other thing I can think of is that I was using a local admin account on my laptop and I’m on Win10 x64. If you can’t figure this out, you can set the quickstick up as secondary and then shift it to primary. If you use a Minimote, check out this thread…
It looks like Aeon Labs only has backup software for Windows, but you can do as I just suggested instead of doing a backup/restore. I use Zensys Tools for the primary shift, which is also a Windows app, so you will need to find some other software that can do the primary/secondary shift.
those are the ones I’ve tried, just to be sure I’m redownloading and reinstalling these drivers (since the PIDs in the INF don’t match my device, I’m forcing it to install the driver.
restoring it does do something at least, though all I can see is that it changes the Network Role from RealPrimary to None.
What is the PID of the device you are using? Mine is 8a2a