Heiman DX1CG-Z CH4 gas sensor won't announce alarm

HI,

This is what I am getting in the log:

2019-04-23 05:03:35.906 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 02 0A 71 05 00 00 00 FF 12 00 01 02 79
2019-04-23 05:03:35.907 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0A 71 05 00 00 00 FF 12 00 01 02
2019-04-23 05:03:35.907 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0A 71 05 00 00 00 FF 12 00 01 02
2019-04-23 05:03:35.907 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-04-23 05:03:35.907 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2019-04-23 05:03:35.907 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2019-04-23 05:03:35.908 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2019-04-23 05:03:35.908 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2019-04-23 05:03:35.908 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_ALARM V7 NOTIFICATION_REPORT
2019-04-23 05:03:35.908 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 0 = 0, event=0, status=255, plen=1
2019-04-23 05:03:35.908 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = null (0)
2019-04-23 05:03:35.908 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2019-04-23 05:03:35.908 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2019-04-23 05:03:35.908 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
2019-04-23 05:03:35.909 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2019-04-23 05:03:35.909 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@47a7088b.
2019-04-23 05:03:35.909 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-04-23 05:03:35.909 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-04-23 05:03:35.909 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-04-23 05:03:35.909 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-04-23 05:03:37.896 [DEBUG] [rg.quartz.core.QuartzSchedulerThread] - batch acquisition of 0 triggers

BR

Janko

It might be easier to read the attachment: I am getting 2 events, event 2 and event 0 (I guess the event 2 is an alarm on and event 0 is alarm off)

Thanks

Janko

zwave sequence.txt (5.42 KB)

Please use code fences when pasting in logs so that they are readable - I’ve edited your post.

Looking into the log sequence of a working sensor (NODE 2) and non-working sensor (NODE 4).

In case of node 2 the alarm is getting processed and it updates the channel state, while in the case of node 4 alarm is getting processed but the part where it should update the channel state is missing.

NODE 2:

[ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
**[ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter NOTIFICATION event is 0, type OnOffType**

NODE 4

[ternal.converter.ZWaveAlarmConverter] - NODE 4: Alarm converter processing NOTIFICATION

Any idea why? Any suggestion how to fix this?

Thanks

2019-04-23 20:08:58.600 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 02 0A 71 05 00 00 00 FF 01 00 01 02 6A
2019-04-23 20:08:58.601 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0A 71 05 00 00 00 FF 01 00 01 02
2019-04-23 20:08:58.601 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0A 71 05 00 00 00 FF 01 00 01 02
2019-04-23 20:08:58.601 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-04-23 20:08:58.601 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:REQUEST_NIF)
2019-04-23 20:08:58.601 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2019-04-23 20:08:58.601 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2019-04-23 20:08:58.601 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2019-04-23 20:08:58.601 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 0 = 0, event=0, status=255, plen=1
2019-04-23 20:08:58.601 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = SMOKE (0)
2019-04-23 20:08:58.602 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2019-04-23 20:08:58.602 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2019-04-23 20:08:58.602 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
2019-04-23 20:08:58.602 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter NOTIFICATION event is 0, type OnOffType
2019-04-23 20:08:58.602 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:16a4ac842da:node2:alarm_smoke to OFF [OnOffType]
2019-04-23 20:08:58.602 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2019-04-23 20:08:58.602 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@35ecb558.
2019-04-23 20:10:10.683 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 04 09 71 05 00 00 00 FF 12 02 00 62
2019-04-23 20:10:10.684 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 09 71 05 00 00 00 FF 12 02 00
2019-04-23 20:10:10.685 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 09 71 05 00 00 00 FF 12 02 00
2019-04-23 20:10:10.685 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-04-23 20:10:10.685 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:DONE)
2019-04-23 20:10:10.685 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: resetResendCount initComplete=true isDead=false
2019-04-23 20:10:10.685 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2019-04-23 20:10:10.685 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported
2019-04-23 20:10:10.685 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_ALARM V7 NOTIFICATION_REPORT
2019-04-23 20:10:10.685 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: NOTIFICATION report - 0 = 0, event=2, status=255, plen=0
2019-04-23 20:10:10.686 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: Alarm Type = null (0)
2019-04-23 20:10:10.686 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2019-04-23 20:10:10.686 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2019-04-23 20:10:10.687 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 4: Alarm converter processing NOTIFICATION
2019-04-23 20:10:10.687 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
2019-04-23 20:10:10.687 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@16694a22.

Hi Everybody,

I made some progress here and hope this helps!?

I have figured out that the item status of the switch item “ALARM” that should be OFF or ON, is “NULL” in fact. If you set the Item manually to status “OFF”, then the alarm is triggering and the sensor works as expected.

You can set this value via openHAB REST API like this for example:

curl -X PUT --header "Content-Type: text/plain" --header "Accept: application/json" -d "OFF" "http://192.168.0.150:8080/rest/items/ZWaveNode036DX1CGZCH4GasSensor_Alarm/state"

I assume the configuration file is not correct, because if openhab or the Thing/Item is initialising again (i.g. after restart) the status will be “NULL” and the sensor wouldn’t work anymore…

Does anybody know how to get this fixed in general?

Many thanks!
BR
Uwe

The state of the switch on startup should not matter - the binding should set the state when an update is received even if it is NULL. On startup, all channel information is not set (ie it’s null) unless you have configured persistence.

I would suggest to use something like mapdb to restore the states on startup

I am trying to configure the DX1CG-Z CH4 Gas Sensor as Node 12

Synology DS214play DSM 6.2.2-24922 Update 3
openhab 2.4.0.002 (I think it’s the newest version for Synology)
zwavebinding 2.5.0.201912030406

Inclusion: ok
thing:


item:
Switch SW_Gas_01_Alarm “Gas Sensor 01 Alarm [%s]” [“Switchable”] { channel = “zwave:device:7ea27444:node12:alarm_general”}

But there is no Alarm coming to the item . What’s wrong with my installation? Any idea? Thanks!

Here my first zwave-log:

The last two lines are the Alarm (10:06) when I push the Testbutton.

?
am I wrong here?

Please can you provide the log image last two lines again, but this time please click on the line to expand the information.

The database will need to be updated to reflect the correct channels.


like this?

Hi chris, do my lines help you to update the database?

I will need to update the code in the binding and then the database. I’ve raised an issue and will try to do this over the next few days as it should be quite simple (feel free to hassle me if it’s not updated toward the end of next week).

This should be included in the next binding update (tonight/tomorrow). Please let me know if it resolves the issue.

Thank you so much.
Please - can you help me to find the org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar file? I can download the directories from https://github.com/openhab/org.openhab.binding.zwave/tree/2.5.x - but i don’t underständ, how to get the jar-file to install the new binding.

There will not be a 2.5 snapshot - you will need to use the 2.5.1 SNAPSHOT which is on Jenkins CI -:

https://ci.openhab.org/view/Integration%20Builds%20(2.5.x)/job/openHAB2.5.x-ZWave/

so happy - it works fine. Thank you so much!!!

1 Like