Comet Z-Wave without channels and device information

wiewior · November 17, 2023, 7:30pm

I recently bough a new z-vawe Thermostat from EUROTRONIC. I have old one (Spirit) which is working perfectly with my OH3.4 on Raspi 4.
Unfortunately I can not receive all data to the controler. The device is unknown. Even after pressing shortly preset button inside the battery space I can not retrieve more information.
Does someone have experience with this device

2023-11-17 20:18:44.459 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Application Command Request (ALIVE:DONE)
2023-11-17 20:18:44.460 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: resetResendCount initComplete=true isDead=false
2023-11-17 20:18:44.461 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2023-11-17 20:18:44.461 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: SECURITY NOT required on COMMAND_CLASS_ALARM
2023-11-17 20:18:44.462 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 46: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
2023-11-17 20:18:44.463 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 46: NOTIFICATION report - 0 = 0, event=0, status=255, plen=0
2023-11-17 20:18:44.464 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 46: Alarm Type = POWER_MANAGEMENT (0)
2023-11-17 20:18:44.464 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 46: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2023-11-17 20:18:44.465 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 46: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2023-11-17 20:18:44.466 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Commands processed 1.
2023-11-17 20:18:44.467 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@19866cc.
2023-11-17 20:18:44.715 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Application Command Request (ALIVE:DONE)
2023-11-17 20:18:44.715 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: resetResendCount initComplete=true isDead=false
2023-11-17 20:18:44.716 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2023-11-17 20:18:44.717 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: SECURITY NOT required on COMMAND_CLASS_ALARM
2023-11-17 20:18:44.717 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 46: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
2023-11-17 20:18:44.718 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 46: NOTIFICATION report - 0 = 0, event=0, status=255, plen=1
2023-11-17 20:18:44.719 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 46: Alarm Type = SYSTEM (0)
2023-11-17 20:18:44.719 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 46: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2023-11-17 20:18:44.720 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 46: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2023-11-17 20:18:44.721 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Commands processed 1.
2023-11-17 20:18:44.722 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1f0b889.
2023-11-17 20:18:44.746 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Application Command Request (ALIVE:DONE)
2023-11-17 20:18:44.747 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: resetResendCount initComplete=true isDead=false
2023-11-17 20:18:44.747 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: Incoming command class COMMAND_CLASS_THERMOSTAT_MODE, endpoint 0
2023-11-17 20:18:44.748 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: SECURITY NOT required on COMMAND_CLASS_THERMOSTAT_MODE
2023-11-17 20:18:44.749 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 46: Received COMMAND_CLASS_THERMOSTAT_MODE V1 THERMOSTAT_MODE_REPORT
2023-11-17 20:18:44.749 [DEBUG] [lass.ZWaveThermostatModeCommandClass] - NODE 46: Thermostat Mode report, value = 1
2023-11-17 20:18:44.750 [DEBUG] [lass.ZWaveThermostatModeCommandClass] - NODE 46: Thermostat Mode Report, value = Heat
2023-11-17 20:18:44.751 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 46: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2023-11-17 20:18:44.752 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 46: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_THERMOSTAT_MODE, value=1
2023-11-17 20:18:44.752 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Commands processed 1.
2023-11-17 20:18:44.753 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@a23be5.
2023-11-17 20:18:44.779 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Application Command Request (ALIVE:DONE)
2023-11-17 20:18:44.779 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: resetResendCount initComplete=true isDead=false
2023-11-17 20:18:44.780 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: Incoming command class COMMAND_CLASS_PROTECTION, endpoint 0
2023-11-17 20:18:44.781 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: SECURITY NOT required on COMMAND_CLASS_PROTECTION
2023-11-17 20:18:44.781 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 46: Received COMMAND_CLASS_PROTECTION V1 PROTECTION_REPORT
2023-11-17 20:18:44.782 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 46: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2023-11-17 20:18:44.783 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 46: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_PROTECTION, value=UNPROTECTED
2023-11-17 20:18:44.784 [DEBUG] [andclass.ZWaveProtectionCommandClass] - NODE 46: Received protection report local:UNPROTECTED
2023-11-17 20:18:44.784 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Commands processed 1.
2023-11-17 20:18:44.785 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@12c8f69.
2023-11-17 20:18:56.727 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Application Command Request (ALIVE:DONE)
2023-11-17 20:18:56.728 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: resetResendCount initComplete=true isDead=false
2023-11-17 20:18:56.729 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
2023-11-17 20:18:56.729 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 46: SECURITY NOT required on COMMAND_CLASS_SENSOR_MULTILEVEL
2023-11-17 20:18:56.730 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 46: Received COMMAND_CLASS_SENSOR_MULTILEVEL V10 SENSOR_MULTILEVEL_REPORT
2023-11-17 20:18:56.731 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 46: Sensor Type = Temperature(1), Scale = 0
2023-11-17 20:18:56.731 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 46: Sensor Value = 23
2023-11-17 20:18:56.732 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 46: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2023-11-17 20:18:56.733 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 46: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=23
2023-11-17 20:18:56.734 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Commands processed 1.
2023-11-17 20:18:56.734 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 46: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@12e632d.

wiewior · November 17, 2023, 7:40pm

I changed polling time to 60sec but nothing came after few polling tries…

2023-11-17 20:38:31.973 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 46: Polling...

Would reinitialise or heal device help?

apella12 · November 17, 2023, 7:45pm

The device is in the DB, but I think had a period when it was modified and dropped. What version of OH4 are you on? could try the latest 4.1m3.

wiewior · November 17, 2023, 7:47pm

I am still with OH3.4.2

apella12 · November 17, 2023, 8:04pm

Well that explains it. Upon further review it should be available on the stable OH4.

The other option is to follow this guide to update your OH3.4.2 zwave binding.

wiewior · November 17, 2023, 8:15pm

hmmm. I am not the fan of updating running properly systems.
If I make an update device will be known based on received z-wave information?

apella12 · November 17, 2023, 8:24pm

Not sure I understand. If you update the binding with the device XML it will be found (most likely ). Also if there is a problem you can go back to the original binding. It should be unchanged if you copy it to the modifying folders. Could also make a copy and put somewhere safe.

Or you can wait until you are ready to update to OH4

wiewior · November 17, 2023, 8:24pm

Update to 4.0.4 (latest stable) seems to solve the problem.
@apella12 Many Thanks!

system · December 29, 2023, 12:25pm

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.