I’d like to get two Neo-coolcam Z-Wave PIR sensors added to the database because they currently show up as unknown device.
OpenHAB tells me “the database must be updated and you should raise an issue to get this addressed” but doesn’t explain where I should raise an issue. I also couldn’t find any better guidance online, which is why I am filing this here.
I have two different types of these:
One with device manufacturer 600, version 0.0, id 4227 and type 3.
The other is device manufacturer 600, version 0.0, id 4237 and type 3.
(the id is different between these two)
I believe that is all the info you need to add it to the database. Let me know if I need to provide anything else.
I looked and both devices appear to be in the DB. As battery devices they may need to be wakened again (or a few times) to be recognized. There could be more information if you set the Zw binding to debug prior to pressing the button.
EDIT you can search the DB directly from here. The numbers are in hex, so mfg 0x0258 and 4227 (0x1083) and 4237 (0x108d)
Thanks. That does lead to more questions than answers though:
Does that mean the error message is wrong?
Why does OpenHAB not recognize the device if it already has all the information needed to recognize it?
I’ve left them on for two days now and pressed the buttons repeatedly but they are still Unknown Devices.
I have many z-wave devices. If I turn on debugging, I get an unreadable amount of messages from all these devices, with no obvious way to filter the ones I should be looking at for more information. A quick glance over these messages shows they are terse and cryptic, suggesting one needs advanced knowledge of the z-wave plugin to make sense of them. Is there some page explaining what they mean, which messages I should be looking for and how to interpret them?
Assuming all the others and the controller work? What version of OH? What model of Z-stick?
Besides the log viewer, you could either attach a log file or put some lines in code fences (</> icon) here and I could take a look. To limit the file size, set the binding to debug, press the button (read manual - it could be three quick presses to wake), then set back to INFO after 20 seconds.
On a first pass I’d look for the device to show it is awake and what stage initialization is in and that the timer is started. Something like
2023-01-10 14:05:45.697 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Is awake with 0 messages in the queue, state IDENTIFY_NODE
2023-01-10 14:05:45.699 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - awakeMax for this Timer Task 20 in 0.5 second intervals
2023-01-10 14:05:45.699 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Start sleep timer with 500ms interval
2023-01-10 14:05:45.700 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 4: Node Status event - Node is AWAKE
