HS-WS100+ coming up as "Unknown"?

[rwa]

I have a bunch of HomeSeer HS-WS100+ wall switches, as well as HS-WS200+ switches. The former always come back as "Unknown" for Manufacturer, Product, and Product Code. The HS-WS200+ are recognized fine.

I have tried excluding and re-including, re-interviewing, nothing seems to work. Has anyone else seen this?

[kpine]

The product IDs need to match an entry in the device database. Do they match? The only entry for the WS100+ has IDs 0x4447:0x3033. https://devices.zwave-js.io/?jumpTo=0x000c:0x4447:0x3033:0.0

There is one model not in the zwave-js DB, but exists in the ZWA DB. It has IDs 0x4447:0x3034, any chance that's yours? https://products.z-wavealliance.org/products/1731

If it's the second one, the IDs would need to be added to the zwave-js DB. Contribute it yourself, or submit a request.

[kpine]

It appears that WS100+ I posted is actually a WD100+, so scratch that. The ID 0x4447:0x3034 is entered here: https://devices.zwave-js.io/?jumpTo=0x000c:0x4447:0x3034:0.0. Looks like the ZWA is wrong here.

[rwa]

I don't know. How do I query the actual Product ID?

When I look under the Node tab in the control panel, it shows "undefined-undefined-undefined (0xXXXX-0xXXXX-0xXXXX)" next to "Device ID". Perusing through the rest of the information doesn't turn up anything that looks like a Product ID.

Under "Manufacturer Specific" I see "[45-114-0-productId] Product ID undefined". I don't know how to interpret this or if it means anything.

[kpine]

The "0xXXXX-0xXXXX-0xXXXX" would be the IDs, I presume it literally is showing the Xs, not numbers? You might need to go to the driver debug logs to see what's happening in this case. If you're using zwavejs2mqtt, the instructions for getting driver logs are here.

[rwa]

Yes, the X's are literal.

After enabling logging, should I re-interview the node? Or maybe exclude, start logging, and include?

[kpine]

Re-interview is easiest, but either works. I would just enable debug logging permanently.

[rwa]

zwavejs2mqtt-log.zip

My inexperienced reading of the log suggests it does not get a return message when querying manufacturer specific info.

I have 8 of these devices, and they all behave this way under zwave-js. They were all recognized normally using the older openzwave implementation, so it's hard to understand what's going on here.

The relevant snippet being:

2021-10-24T19:43:17.935Z CNTRLR » [Node 061] querying manufacturer information...
2021-10-24T19:43:17.952Z SERIAL » 0x010900133d027204251f96                                            (11 bytes)
2021-10-24T19:43:17.952Z DRIVER » [Node 061] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      31
                                  └─[ManufacturerSpecificCCGet]
2021-10-24T19:43:17.962Z SERIAL « [ACK]                                                                   (0x06)
2021-10-24T19:43:17.967Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2021-10-24T19:43:17.967Z SERIAL » [ACK]                                                                   (0x06)
2021-10-24T19:43:17.968Z DRIVER « [RES] [SendData]
                                    was sent: true
2021-10-24T19:43:18.029Z SERIAL « 0x010500131f00f6                                                     (7 bytes)
2021-10-24T19:43:18.029Z SERIAL » [ACK]                                                                   (0x06)
2021-10-24T19:43:18.030Z DRIVER « [REQ] [SendData]
                                    callback id:     31
                                    transmit status: OK
2021-10-24T19:43:21.549Z SERIAL « 0x0118000400191232022174000000000000000000000002080780              (26 bytes)
2021-10-24T19:43:21.557Z SERIAL » [ACK]                                                                   (0x06)
2021-10-24T19:43:28.033Z CNTRLR   [Node 061] Timed out while waiting for a response from the node
2021-10-24T19:43:28.037Z CNTRLR   [Node 061] [+] [Manufacturer Specific] interviewComple [Endpoint 0] [internal]
                                  te: true
2021-10-24T19:43:28.082Z CNTRLR   [Node 061] Interviewing Version...

[rwa]

After some googling, I also tried:

Using a USB extension cord to move the stick off the back of the PC to reduce interference.
Using another zwave stick I own.

Neither produced a different result. Still "unknown" for this particular device but fine for every other one.

Is there a way to increase the timeout interval, so I can see if this device is just slow to respond sometimes?

[rwa]

A factory reset of the switch resolves the issue. Argh. Thanks for the assistance.