I am using paper UI for the things configuration, but if I have added the nodes before via Z-wave
software or via push button on the stick, then the z-Wave binding search is only delivering “unknown device” instead of the correct Heimann sensor.
The update I tried to do via complete new installation in a different folder, not to loose my old data, and then just adding z wave binding and search for the nodes, but also in this case the already identified sensors in OH 2.4 were found as unknown devices In OH 2.5 meaning somehow the same like above if I do not include the devices in OH directly but use external inclusion, in this case OH 2.4
While running latest OH (2.5) ?
Then it will not have worked to do that with 2.4 and get the sensor properly identified.
Check if the sensor is in the zwave database and if not add it.
Not a good idea.
Use openhab-cli backup/restore to save/restore your config.
The Heimann smoke sensors are tricky! Once you start the inclusion you constantly have to press the button on the device like every second to keep the sensor awake.
If that fails exclude again and start over. I already had my own “fun” with these devices…
How did you identify the faulty node? How was it faulty? I’m running into this issue every night, and my network hasn’t completely healed in several days.
Well just as with any battery sensors, you eventually have to wake them up a couple of times to complete initialization, but my Heiman now is recognized just fine.
I’ve updated to the 2.5.1 snapshot linked in another thread and heal is still destroying my network causing me to have to restart my openHABIAN pi to bring all the nodes back online. You can see that my network needs to update the neighbors because the last 20 or so devices I’ve added haven’t correctly mapped their network. Heal doesn’t seem to be working on individual nodes, either.
Firstly that map does not necessarily reflect your network’s routing. It is a list of neighbours reported during a neighbour update. I ignore it as it looks nice but is not massively useful. Zwave routing is a bit more complex.
If your network is bad you can try this…
If you have a windows machine or run openHab on a windows machine. Download PC programme from silicon labs.
Take the usb stick and put it in your windows machine with the machine in exactly the same place as you normally have your openhab machine.
you can now manage your network outside of openHab
First backup NVM
Now go to
Now if you select Rediscovery your network will do a heal. When it is finished run a network health check. If good close down the program or look around and see what else you can do. If not this tool is good for sorting it out. Ping back if you have issues.
Take the usb out when you have finished and put it back in openHab machine and restart openHab. That little map thing will still be as useful as a chocolate teapot but if your nodes are all in range of each other and everything is working don’t worry. You can always look at the topology in PC programme.
I’ve used this software before but I can’t find where I downloaded it to and I can’t seem to download it from Silicon Labs. Can anyone suggest where I can download it? Google isn’t helping at moment…
Problem solved! I had to agree to the SIlicon Labs terms and conditions first by downloading their SDK, this then gave my account the necessary privileges to download the PC Controller software.
Remember that unless you have issues with heal in openHab it is a lot of hassle so I am not saying not to use heal in openHab. This is suggested as a workaround if it is not working.
It stopped working for me at around 120 physical devices but many things on a zwave network become interesting at that number of nodes.
I speculate it was at that point that the underlying traffic on the network from reports from devices clashed with the rate of the discover neighbours sent by openHab.
OR
Possibly also time it takes to rediscover neighbours goes up as the count of nodes goes up and it started to exceed the time openHab is set to consider too long.
I thought I’d try this program as well, seems like a good tool for managing z-wave. I fail on the first step however. The one where I should select which port my Z-stick is in. The list is simply empty. Tried putting the stick in different USB ports, clicking the detect and refresh buttons etc, just nothing. Anyone knows what to do? Do I need to install any special drivers? It’s a Aeotec Z-stick S2.
Dumb question… can someone paste a link to this tool on the silicon labs website? I’ve downloaded a few different tools but can’t seem to find this windows utility
The good old Aeotec. The slight odd boy among z-wave plus.
It is an older SDK and they may well not have implemented all of the options. I think Aeotec have their own utility but not definite. Someone may chip in but it may also be worth talking to them and seeing if they have a firmware that does or their own tool.
That mao is on a different tab and you need to press the reload button. This button calls the API and the controller passes the current topology to the PC Controller Program. On first visit it will be blank.
Aeotec use an old firmware and don’t (as far as I know) have anything newer (at least last time I spoke to them about this which was a few months back now, but at that point they had no plans to update it).
