The unknowns are coming from your other devices. I just needed to see manual operations only to confirm no traffic from the device. Is node 1 shown in the lifeline group?
No, the ZEN35 has blank for the lifeline group. My other dimmers say “controller”. Can I just type that in? Is there some special process to do that?
Edit: I put a 1 in the box, saved it and it shows controller now. Didn’t see a change in functionality immediately. Maybe I need to wait?
Edit 2: OMG! I got a scene number from it!
1 Like
Here’s what the logs look like after getting the scene updates working:
The “unknown command class 05” is super suspicious to me now when looking at the timing.
Thank you SOOO much @apella12 for helping me get this far!
zen35_scene_working.txt (122.9 KB)
1 Like
Ok, the ZEN35 is sending updates with the dimmer level, they are being sent as COMMAND_CLASS_BASIC, but the values are there.
This message shows up as “Unknown command class 03” in the log viewer:
2026-02-08 17:31:39.189 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 A8 00 01 1A 03 20 03 63 00 AD AE
2026-02-08 17:31:39.191 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=BridgeApplicationCommandHandler[168], type=Request[0], dest=26, callback=0, payload=00 01 1A 03 20 03 63 00 AD
2026-02-08 17:31:39.192 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=BridgeApplicationCommandHandler[168], type=Request[0], dest=26, callback=0, payload=00 01 1A 03 20 03 63 00 AD
2026-02-08 17:31:39.192 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2026-02-08 17:31:39.193 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 26: Application Command Request (ALIVE:DONE)
2026-02-08 17:31:39.193 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 26: resetResendCount initComplete=true isDead=false
2026-02-08 17:31:39.194 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 26: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
2026-02-08 17:31:39.194 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 26: SECURITY not supported
2026-02-08 17:31:39.194 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 26: Received COMMAND_CLASS_BASIC V1 BASIC_REPORT
2026-02-08 17:31:39.195 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 26: Basic report, value = 99
2026-02-08 17:31:39.195 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 26: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2026-02-08 17:31:39.195 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 26: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_BASIC, value=99
2026-02-08 17:31:39.196 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 26: Commands processed 1.
2026-02-08 17:31:39.196 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 26: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@583e2cde.
When following other sample XML files, I added the COMMAND_CLASS_BASIC to BOTH the dimmer and scene_number endpoints. Is that correct?
Again don’t worry about the rows with a “1”, that is a viewer problem. Here is the same snippet corrected.
What is also shown is that are you getting the basic report now, but it is not updating the UI. It should have a STATE UPDATE. Again the delete thing and scan might pick up that they are linked. (if you didn’t do that already.
EDIT: Saw your latest. I don’t think the basic should be tied to the scenes, just the switch.
Woohoo! Removed it and re-added and now the dimmer state updates!
1 Like