Aeotec Z-Wave Stick 10 working with Home Assistant?

Configuration Z-Wave
1

Bought a Aeotec Z-Stick 10 and wanted to migrate from Aeotec Z-Stick gen5+ to the new stick.
Made a NVM Backup of the gen5+ stick and wanted to restore it to the Z-Stick 10 using Z-Wave-JS. Unfortunately this doesn’t work.

For the Z-Stick 10 it is shown under Product code “Unknown product 0x003c” in the Control Panel. Firmware information got extracted fine.

Doing the NVM Restore from the gen5+ stick to the Z-Stick 10 all nodes are also shown as “Unknown manufacturer” and “Unknown Product 0xXXXX”.

grafik
grafik2454×360 47.5 KB

Doing the same Restore to another 800 stick (Zooz) the restore works fine. So I assume it has something to do with the Z-Stick10 adaption in Z-Wave-JS.

It is not yet known to Home-Assistant? Or I am doing things wrong?

Thx for feedback and help.

SH

2

I did a fresh install and have the same unknown device for the Aeotec Z-Stick 10 Pro ;
“Aeotec Ltd. , 0x0004, Unknown product 0x003c”.
I have also updated to the last firmware (1.2)

3

I did a check, and the ZWA060 doesn’t seem to be in the zwavejs database (not yet anyway) which would explain why the stick has unknown product id.
It seems the remaining node-ids were restored in the ZStick, but the rest of the nodes will be unknown if they have not been interviewed, so my guess is that there is a comm problem? Any logs?

4

Sounds like an issue with the Z-Stick 10 firmware (or the SDK). See comments in:

5

I have the Z-stick up and running, but with a lot of lag. The stick is still a “unknown” product after FW update to fw 1.2, SDK: v7.23.2
Should one choose RF Region Europe (Long Range) when in Europe (not using long range) for the Aeotec Z-Stick 10 Pro, or should this be left unselected, which is the default after I installed it in Home Assistant?

Aeotec Z-stick 10 pro RF region_EU
Aeotec Z-stick 10 pro RF region_EU1920×1036 118 KB

6

i just got my ZStick 10 Pro too…updated on PC to latest firmware, then plugged into my HA…did before a NVME Backup of my ZW090 stick…and enabled then the ZStick 10 Pro…NVME Restore went flawless…also after i restarted zwave addon… all 101 devices were recognized

ONE issue i still have…my lights…which i do switch with fibaro FGS213 OR FGS223 there are no entities valid anymore in all my widget…the device itself is there and switchable…which is bad…bcz a lot of automations use this entities…

7

So you don’t find your lights entities? Then you have to “Create helper” in “Devices & services” with the “Change device type of a switch”

IMG_3286
IMG_32861288×1764 147 KB

8

i had entities…they did work…however…after i switched the sicks…they were gone…i had to change my automations to the new entities…anyway…working now…maybe more stable than my zstick7 but still i get the jammed issue…so i did swap back to my gen 5 controller

9

It should be on Europe (Long Range)
Also for Normal power level I was recommended +14 from Aeotec support so both on+14. My default was 0 and it improved range a lot for me.

z-wave
z-wave651×300 5.37 KB

10

I’m still just stuck on the firmware update; I assume the “Button” I have to press in the documentation is in this tiny little pinhole on the side?

11

For clarification: does the Z-Stick 10 work simultaneously as a Z-Wave and as a Zigbee controller with Home Assistant (and does it do it on a Raspberry Pi)?

1 Like
12

Yes both Z-Wave and Zigbee work in Home Assistant simultaneously. Not sure about Raspberry Pi as i run it on a VM/Unraid setup.

1 Like
13

Just an FYI, ZWaveJS has now added support for this stick

It is in version 15.8.0

2 Likes
14

Can the z-stick 10 pro be connected directly to a USB 2 or 3 port, without an extra cable?

15

The USB connector on the computer PCB, particularly one supporting USB 3, emits a fair bit of RF interference in and around the connector. That’s why as a general practice it is a good idea to have a extension cable, so that the ZStick is further away from this interference. If you can’t use an extension cable, then using a USB 2.x port is your better bet.

16

Did you ever figure this out? I can’t get the bootloader text to show up in teraterm, so I’m unable to upload the firnware.

17

I’m also trying to figure this out. There is indeed a button in the pinhole down but pressing it while plugging it into my PC doesn’t make it show up in Tera Term.

18

Just replying here to say that I’ve been running the Aeotec Z-Stick 10 Pro for a few months now and it works great. Upgraded to firmware v7.23.2 which I recall being a bit of a faff (mostly because I don’t have a Windows machine, so had to cobble one together temporarily), but since then it seems to be working great.

I run Z-Wave JS UI & HomeAssistant as Docker containers on an Unraid host. I use a USB2 extension cable to keep the dongle away from the host a little ways.

19

I thought I’d share my experience upgrading my Aeotec Z-Stick gen5 (not plus!) to 10 pro on Z-wave JS UI (docker version). It eventually worked out, but it you need to follow lots of very specific instructions. Aeotec has nice how-to’s, but you need several to get the full picture. The main process can be found here: Z-Stick 10 Pro Migration: A Guide coming from Z-Wave 500/700 Networks : Aeotec Help Desk

But first: make sure your old gen5 stick has 1.02 firmware (not mentioned in the article above). You need a Windows PC for this. Just stop your Z-wave JS and unplug the stick. Follow these steps: Z-Stick Gen5+ V1.02 firmware update : Aeotec Help Desk

Anything this manual says you “might” need to do: expect it to happen. Windows really likes to just use a generic serial driver and it won’t work. You will get the “press reset button” issue. You really need to install the Sigma driver and force Windows to use it.

Then replug the (old) stick and restart your container to make the NVM backup with Z-wave JS UI. Older backups won’t work!

After this: stop your container again and unplug the old stick. Plug the new stick in, find the device mount point (something with /dev/…) and restart the container with the mount point of the new device. If the mount point has changed, the UI will show an error about the missing device. You can solve this error by checking/updating the mount point of your stick in the UI settings.

When the new stick is connected, the device list will be empty, but don’t worry! It will all be fine later. It will even be ok again if you -for some reason- need to revert back to your old stick.

Do not start with restoring your NVM backup yet! First, update the firmware of your new stick. Yes it’s brand new, but most likely, the firmware isn’t. You need at least 7.23.2 It can be done from Z-wave JS UI: Z-Stick 10 Pro Update - Z-Wave (V7.23.2) with Windows : Aeotec Help Desk

When your new stick also has new firmware, you can restore the NVM backup and your devices will pop-up immediately.

If you forget to update the firmware of your new stick, you might be able to restore the NVM Backup, but in my case all devices were marked “sleeping” and got “ProtocolInfo” state forever. Even after upgrading the firmware it did not accept the backup anymore. I first had to factory reset the device.

Lessons learned:

  1. Don’t think: I’ll just try it with current firmware: update first.
  2. Don’t worry about starting and stopping the docker container often and connecting and disconnecting sticks. Your device list might dissappear, but everything is still there in the background and will reappear when the NVM backup is restored properly.
20

Hey sorry, I stalled out because I still don’t have any Z-Wave devices to test with. I’ll try to report back whenever I get back to it…