i am trying to add the WallMote from Aeotec (Quad Switch) to OH, but it only discovers an “unknown device”. I tried to delete and re-search it a few times as well as leaving it besides the z-wave controller for some time, but it didnt change. I believe there are some different versions of that switch, mine is a FT130-C, bought a few days ago. My OH is 2.3.0.
Is there some way to add it? Can i somehow manually add it?
It did not generate a XML file there for the unknown device. The device it the database looks promising (didnt find it in other databases…).
Do i have to export from the website and just generate the xml myself? Should i add it as unknown device before or should i add the xml with the switch in the inbox? I seem to be rather inexperienced with z-wave
edit: the XML export (OH2) from that website looks very different to my existing nodes i have in OH, i assume that’s not good
ZWave battery devices can be a bit difficult to operate as they need some configuration before they will periodically wake up. Until this configuration is programmed, you need to manually wake the device - this is normally required a few times after the initial inclusion.
What do you recommend to accomplish that? I set the wakeup interval to 20sec via habmin (paperui returns error 500 when i set the parameter). I had it like that sitting besides the z-wave stick for the night. I also used the “send wakeup notification” of the devioce (hold action button for 3 sec), but that didnt trigger the configuration either. Not sure, if i am doing the right things
So basicly you say i should wait for the device to get fully in contact with OH, right? Do i use the XML sihui pointed me to after that or should it complete the configuration on its own?
edit: the device shows up on the z-wave network viewer in habmin, but still no XML.
You need to read the manual - every device has a different way to do it.
Did you wake up the device after setting the configuration in HABmin? If the device is still asleep, then the setting won’t change.
Yes, this is needed, but you can’t wait for this - you need to actively wake up the device if it is not already configured. If the device sleeps, and wakeup has not been configured yet, then it will just sleep forever (and forever is quite a long time to wait ).
It is possible that the device is waking up, but there’s some other issue that is preventing it initialising - if this is the case, then you’ll need to enable debug so we can work out what is happening.
Well thats what i did, pressing the button for 3 sec. Did it like 10+ times now the stick changes its blinking pattern for a short amount of time (not for every 3-sec-attempt though), so the button-press is definitly recognized (sometimes). Still no XML yet …
Which logs are best to debug this? Sorry for my probably basic questions, but this is my first contact with z-wave.
You can also get a good indication from the ID in the URL - at the moment we’re at the top of the 800’s, so it gives an idea of how old entries are at least (this is 860, so it’s only 20 or 30 entries ago - probably just a few weeks).
You need to update the binding to the latest snapshot. You will need to do this manually if you are using the 2.3 runtime as uninstalling, and reinstalling when you are on a stable build will just reinstall the same version.