node-zwave-js: [question] Unknown manufacturer 0xXXXX listed for device in database

I have a device (Schlage Connect BE469) that is connected to my Zwave network. It works fine as far as I can tell and has for a few years. However, for some reason zwavejs2mqtt can’t seem to get the manufacturer or product. This is strange because in the debug info, the manufacturer and model are clearly shown in the hassDevices section. Is there a way to tell zwavejs what device this is? Or some debug logs I can generate to see why it’s not getting detected?

Thanks!

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 30 (13 by maintainers)

Most upvoted comments

@WhiteNight121 At the beginning of the interview, your stick is unable to transmit anything for several seconds. Right when the secure communication is figured out:

2022-05-11T21:44:09.568Z DRIVER » [Node 010] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      147
                                  └─[SecurityCCNonceGet]
2022-05-11T21:44:09.570Z SERIAL « [ACK]                                                                   (0x06)
2022-05-11T21:44:09.571Z SERIAL « 0x0104011300e9                                                       (6 bytes)
2022-05-11T21:44:09.572Z SERIAL » [ACK]                                                                   (0x06)
2022-05-11T21:44:09.572Z DRIVER « [RES] [SendData]
                                    was sent: false
2022-05-11T21:44:09.573Z CNTRLR   The controller response indicated failure after 1/3 attempts. Scheduling next 
                                  try in 100 ms.

(this goes on for a while).

As a result, Z-Wave JS is unable to communicate with the lock which is why it isn’t working properly.

Can you do the same again to see if it is reproducible? Please remove logs first though so you don’t have to transmit 30 MB and it is easier to compare.

AlCalzone on May 12, 2022

@WhiteNight121 in general the Z-Wave functionality should be mostly working even if the device isn’t identified due to a missing configuration file. For many devices, these are only cosmetical and/or convenience (labels and pre-defined configuration parameters).

If not, see my comment directly above yours.

AlCalzone on May 11, 2022