Please post configurations (if applicable):
None that seams to give any clues.
If logs where generated please post these here using code fences:
None even though zwave logging was set to Debug.
Background:
I bought a Neeo controller to manage home theatre setup and also z-wave components. Then the Neeo company got bought and servers would be taken down after two years, so I started to look for a new z-wave controller. I ended up with a z-stick connected to rPi. I then transfered control of all z-wave components to the rPi running Home Assistant and I think I left the Neeo as a “secondary controller”. I had some problems with HA, so I switched to OpenHAB. I think one of the components that got transfered to rPi from Neeo was a Hank SCN01 scene controller. Just recently I tried to get it to work with OpenHAB but it didn’t play well with the controller (it was only reported as “unknown device”) so I reset it and removed it from the z-stick with the Simplicity Studio PC Controller software. There was no problem then to include it again with OpenHAB and it was fully recognized.
Current issue
Now I’m trying to create rules that react to the Hank SCN01 when pressing the button. I have no success. The rule works if I play it, but nothing happens if I press the button. I can see that the device is online, but the only “sensor” is battery level and it is reported as 0%. I have set zwave to Debug level for logging, but I see nothing in the logs when the button is pressed. The top side led is only blinking blue a lot. Something I don’t understand when investigating the manual.
Now you have the problem that the other posters were writing about in your other thread, the battery device is not fully configured. Discovered, yes. IDed Yes. Configured No. How to tell is on the UI page you need 5 lines.
You need to use the wake-up button protocol, probably several times about 30 seconds apart. You can set the zwave to Debug and follow the progress (hopefully there will be progress). Also can you post the lower section of the UI page that shows Association group and wake-up interval? If the initial configuration gets those set, it’s only a matter of time. If not, it could be an adventure.
Ok, definitely not fully configured and with the lifeline & wake-up not assigned, it could be an adventure. Also, no activity in Debug is not good.
Try to set the lifeline to controller in the UI and then wake. Also try both the wake and the include protocols from the manual on the button.
I’m not sure about that Debug message, except it is also saying initialization is not complete. We have to get it started. Edit: you will know when it gets going because the Debug log will get big.
Not quite there then. Do whatever you did a few more times. Might also try to remove battery, wait 10 seconds and replace it (besides the wake pushes)
Bob
edit: I looked up > Device initialisation complete< in the ZwaveThingHandler class and it means the channels have been recognized. Where it needs to go next is Static Values and you can see by your Debug snippet the static stages are not complete, so it needs reawake. IMO- I don’t think restarting OH will help.
Kind of neutral. The device has gotten far enough along to set a polling interval, but until it makes further progress, it is going to defer. What we need to see is a device wake-up message. Are the button push protocols, not working? Maybe try the setting of controller as node one again as that at least generated something.
Took a look at the manual ( do not have device). The button I’m talking about is not the scene button, it looks there is a very small button in the center. Is that what you are using?
Bob
Edit: reading further the wake touting is to press and hold until a green led. Is that what you are trying?
