-
|
I just moved from openzwave to zwave js ui. During the migration i have 2 nodes i cannot get to work properly. One of them is a neo coolcam wallplug. i couldn't find this wallplug when i did the migration. So the status now is Dead (and interview stage is protocolinfo). However when i try to activate it there is now way i can get the interviewing to finish. I did try
The other device is a Heiman smoke detector. This one did finish the interview stage (after waking up, cause it's a battery powered device), but only exported the "battery is low" switch to mqtt, and not the other properties. So i wanted to reinterview (node/advanced/reinterview node). But also on this one i immediately get the "API Refresh info ended succesfully". But then nothing happens, so no "interview stage completed" and no "interview failed". Actually nothing happents in the tab events. I have more Heiman smoke detector and Neo Coolcam wallplugs which all work correctly, so something really seemed to be going wrong during interviewing stage. How can i trigger a proper re-interview? |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 7 replies
-
|
Please make a driver log, loglevel |
Beta Was this translation helpful? Give feedback.
-
|
Tx that you are willing to take a look. here's the log file (it is about node 185: The smoke sensor). It is very weird, cause i have different behaviour now: the interviewing finished. However it is still nog complete, cause i am still missing discovery messages e.g. but this failing one only shows Also the discovery message for the battery level is missing. You can forget about the Neo Coolcam i mentioned above. I did a factory reset and it turns out that node is dead, so no way to do representative testing on that one... |
Beta Was this translation helpful? Give feedback.
-
|
@AlCalzone Is the maintainer of the driver, please be patinet until he can take some time to review your logs. For what I can see seems your node 185 suports S2 but you have no key setup on settings:
Try to add the S2 keys on settings, exclude and include the node again to see if the issues persists |
Beta Was this translation helpful? Give feedback.
-
|
tx.. i will try the reinclude with S2 security. Although i do not think this will have impact. The other Heiman smoke detecters in my network do finish correctly (also without S2) |
Beta Was this translation helpful? Give feedback.
-
|
If it was definitely included without S2, there's no need to change that. That log message is more of a hint/warning. |
Beta Was this translation helpful? Give feedback.
-
|
it was indeed included without s2. Tx for the help. i'll be patient ;-) |
Beta Was this translation helpful? Give feedback.
-
|
Node 185 does not support Binary Sensor CC, but it supports Notification CC. You should have a notification value for Smoke Alarm[Sensor status]. |
Beta Was this translation helpful? Give feedback.
-
|
tx for investigating. I see the indeed no binary sensor in the ui. I now checked, cause i have several of these smoke detectors, all on the same hardware (Heiman). But i now checked. Not all have the same firmware. The ones with fw 1.1 have binary sensor support. The ones with more recent firmware (3.1.1) do not... so it's indeed a thing in the device. Sorry to mention this as an issue on zwave js ui. (and tx for the support!) BTW: I switched from openzwave to zwave js ui. It was quite a hassle to make it work, but now that it's working it's a big step forward. Much more options in the ui and the network is more stable and responsive. Tx a lot for all the hard work!! |
Beta Was this translation helpful? Give feedback.
-
|
Out of curiosity what has been the most difficult part in configuring Z-UI for you? Did you checked the official docs? You feedback could help me improving them if something is not clear |
Beta Was this translation helpful? Give feedback.
-
|
I think the docs are quote clear and so is the product itself most difficult part in moving from openzwave to zwavejsui for me was
|
Beta Was this translation helpful? Give feedback.
-
|
About the first bug there are many different ways to setup an mqtt broker container but I could integrate that in the docker setup. About the second part the reasons could be multiple. It could be there is no config file in db for those devices yet, the device has some compatibilty problem, connectivity is bad (usually this can be fixed by using an usb extension cord), driver issue. |
Beta Was this translation helpful? Give feedback.
-
|
although never say never, but i think for 2nd networking or uncompatibility issues to be the cause is quite unlikely. When i started doing the migration again at first i just started up the docker with just docker compose -d. (So basically recreated the container based on the release of a year ago) and it gave me exactly the same result (interview stage not finished, lots of device not recognized). but then i did a docker compose down, docker compose pull and docker compose up -d again (so recreate image on latest releases version) and then it all worked... anyway a year ago (which is a very rough estimate, i don't know exactly. It was a long time ago) I did not spend a lot of time on diagnosing. I just checked if it worked because of some remarks of OpenZwave no more being maintained, but since the conversion gave me problems and domoticz still supported it at that time i just left it for a later time... And very happy to see it work now! and also much more stable and responsive than openZwave with better ui to manage the zwave network, so big step forward..!!! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your feedback 🙏🏼 |
Beta Was this translation helpful? Give feedback.
Node 185 does not support Binary Sensor CC, but it supports Notification CC. You should have a notification value for Smoke Alarm[Sensor status].