Looking forward to mine arriving, but hoping that there’s an incoming firmware that also lets the unit use the ESP32’s antenna as a BT proxy.
Just ordered. I don’t have compatible devices yet, but I believe supporting your team is a moral duty. In the same way, I had bought the Sky Connect.
3 Likes
I slept one night over it, tried again. Finally found a use for it:
No, seriously, with the kind en lightning fast help of @freshcoast I got successfully migrated from an old 500 series zwave.me UZB stick and all is running fine 
18 Likes
Because I wanted to play with it over the weekend, I decided to accept the 17% markup because of it being in stock and shipped immediately and ordered yesterday at noon. Only to find out HAShop failed to drop the package at the parcels office. Now I’m lucky if I get it tuesday. 
I’m starting to wonder if they are lying about it being in stock now. HAShop is a no go for me from now on.
1 Like
So I did this the wrong way round! I ordered a ZWA-2 (from Everything Smart Home) assuming that I still had that Z-Wave device at the back of the drawer that I picked up in a “box” of Zigbee stuff! Wrong!
I have two reasons for the purchase, supporting Nabu Casa and Z-Wave interest.
So now I’ve ordered a Z-Wave dimmer and relay from Shelly, with the intention that these will be direct replacements for some older Sonoff Zigbee switches.
Be interesting to see how these perform buried in a metal box in the wall! One of the relays periodically disconnected but since I’ve upgraded to the SMLight SLZB-06P7 from the Sonoff USB ZBDongle-P it’s been rock solid.
Yes it would have been “better” if this was PoE for reasons already stated, but I hope I’m supporting future development by continuing to support Nabu Casa.
1 Like
I am currently using the HomeSeer SmartStrick G8, on the Z-Wave 800 platform, and it is working well. How easy is it to switch over to this product? I would not like to encounter a lot of problems changing the interface.
Hopefully this new Z-Wave radio adapter will work magic for you but be aware that a electrical junction box that is made of conductive material like metal will basically act like a faraday cage and will block most signals.
Because of this I previously replaced all my metal junction boxes with plastic junction boxes for that very reason.
I installed Qubino Flush Dimmer modules based on Z-Wave 500 behind each wall switch and reception was very poor with different Z-Wave Controller adapters until I went ahead and retrofited plastic junction boxes for all of them.
This is just the physics of radio signals and a faraday cage:
Yes, the metal back box conundrum! To fix several (non critical) issues we contemplated a whole house rewire earlier this year to bring the electrics up to current standards and improve some availability of sockets. Postponed it for now, maybe forever!
There are no critical issues with our current wiring but it was an excuse to bring a neutral to all light switches! However, I don’t have a definitive answer to are plastic back boxes, not in plasterboard, ok? Different sparkies give different answers. My interpretation is that it doesn’t matter, but for now it’s a moot point as we aren’t redecorating or rewiring.
Interesting though that the SMLight performs better than the Sonoff, so size really does matter!!! In which case ZWA-2 won’t give me any issues, will it??
Of course the periodic drop offs could just be Zigbee and WiFi doing their thing.
I live in Sweden and here it is code to get retrofit boxes installed and there are loads of choices for such retrofit boxes for the continental style of electrical retrofit boxes used here. They are approved for all types of builing materials.
For any docker users migrating here are some tips
I migrate from aeotec gen 5(not plus) on 1.2 firmware to uzb
I think one of 2 options would work
OPTION 1 backup and restore
backup old USB controller
stop container and restart with new controller attached
restore backup to UZB. All nodes restored without issue
This is basically what I did, it was quick and just worked.
HA wanted to migrate to controller at its LAN IP. I did just to see what happened and eventually reentered the docker network hostname. You can probably remove the message somehow.
OPTION 2 Migration
start a 2nd docker zwavejsui container with uzb that HA can see. HA will discover this container and ask if you want to migrate. I presume this will work but have not tested.
I add udev rules for my usb devices and for the uzb I added below to a file at /etc/udev/rules.d/99-usb-serial.rules on my host
SUBSYSTEM=="tty", ATTRS{idVendor}=="303a", ATTRS{idProduct}=="4001", MODE="0660", GROUP="zwave", SYMLINK+="zwaveuzb"
i then mount /dev/zwaveuzb:/dev/zwaveuzb in my container
I’ve always had Z-Wave issues in my home. I think the problems were a combination of thick, brick exterior walls and interference. I had implemented some LR devices for places that were particularly troublesome, especially in my detached garage, where the switches are in metal boxes. All of the indoor switches are also in metal boxes. I was previously using the Zooz 800 series stick. I upgraded to this device, followed the instructions for Z-Wave-JS-UI, and it converted flawlessly. First impressions are a very noticeable improvement in reliability and speed.
2 Likes
Did your current provisioning transfer directly from your zooz stick or did you have to re-provision all your devices?
It all transferred as advertised. Make & download the NVM backup as instructed, and then upload it to the new device. The entire process took less than 5 minutes. The only additional step was to activate battery-powered devices once to get them to start really working. i.e., I had to open/close a door with a sensor once for the door sensor to work, trip a motion sensor once, etc. If you went through the trouble of the wake-up process for each device, I’m sure that would do it too, but tripping them did the trick for me.
3 Likes
Migration from my Aeotec Gen5 1.2 also went smooth like butter. However I noticed that there might be an issue with OTA updates for devices. I wanted to update some Shelly Wave Shutter with an pre-released version from their support. I did that with one device already with the Aeotec stick and it went fine.
With the now migrated to ZWA-2 it is stuck at 0.01%. Tested multiple times with ZWave JS UI and the HA integration both won’t procedd beyond this percentage.
I’m not sure if this is ZWave JS related as it worked with the previous adapter.
Is anyone else facing this problem? Or at least can tell me how to figure out where the problem shouls be addressed at, HA or ZWave JS? Thanks!
anyone here with a UZB Zwave.me stick ?
Mine is on FW: v5.39 SDK: v6.82.1 according to ZwaveJS UI.
Can I do a NVM backup and restore to this new Zwave antenna ?
Also I noticed I can’t do a NVM backup of that UZB stick on my ESXi HA instance.
A NVM backup of the UZB stick only works on a real PC. (did one on my Windows PC and a compiled Windows version of ZwaveJS), so probably I’ll have to follow the same Windows PC/ZwaveJS to restore that UZB NVM backup to the new HA Zwave Antenna ?
Strange I always thought you had to first unpair from old Zwave controller before being able to pair a device to a new controller.
Unplug ZWA-2 and try again
If that doesn’t work backup NVM of aeotech >>! Enable ZWA-2 in zwavejsui >> restore Aeotech NVM to the ZWA-2
1 Like
I also have this stick, with FW 5.25 and the backup works in Zwave JS UI.
Maybe try to power cycle the stick?
Thanks, checked that and also power-cycled the system. Still the same issue, firmware upgrade for the Shutter is stuck and does not proceed with the ZWA-2
Folks looking for an Ethernet connection… Grab a Raspberry Pi with Ethernet. Install ser2net, use the following YAML as ser2net config:
# /etc/ser2net/ser2net.yaml
connection: &zwave
accepter: tcp,3333
enable: on
connector: serialdev,/dev/serial/by-id/usb-Nabu_Casa_ZWA-2_DEVICEADDR-if00,115200N81,nobreak,local
options:
kickolduser: true
And specify tcp://yourraspberrypi.lan:3333 in zwave.js. Done.
Note that your device-id may differ. So does the FQDN of your Raspberry.
2 Likes
I’ also using proxmox… there are usb over ip devices on the market, but they usually have drivers for Windows. Anyone knows such a driver that will run on home assistant os?