Rule with the Fibaro Smoke Sensor

[jaydee73 (Stefan)]

@chris: I’ve updated the binding, deleted the thing and the xml and added it again. It was found and initialized with a manual wake up. But I got some confusing log entries:

2016-12-12 21:22:13.039 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - NODE 8: setupNetworkKey useSchemeZero=false
2016-12-12 21:22:13.832 [ERROR] [curityCommandClassWithInitialization] - NODE 8: SECURITY_ERROR Invalid state! Secure inclusion has not completed and we are not in inclusion mode. Aborting
2016-12-12 21:22:14.167 [ERROR] [curityCommandClassWithInitialization] - NODE 8: SECURITY_ERROR Invalid state! Secure inclusion has not completed and we are not in inclusion mode. Aborting
2016-12-12 21:22:15.185 [ERROR] [curityCommandClassWithInitialization] - NODE 8: SECURITY_ERROR Invalid state! Secure inclusion has not completed and we are not in inclusion mode. Aborting
2016-12-12 21:22:17.609 [ERROR] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: Retries exceeded at DYNAMIC_VALUES
2016-12-12 21:22:18.168 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Initialising Thing Node…
2016-12-12 21:22:18.365 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
java.lang.IllegalStateException: Could not update status, because callback is missing
at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.updateStatus(BaseThingHandler.java:388)[103:org.eclipse.smarthome.core.thing:0.9.0.201612091054]
at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.updateStatus(BaseThingHandler.java:415)[103:org.eclipse.smarthome.core.thing:0.9.0.201612091054]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:1178)[179:org.openhab.binding.zwave:2.0.0.201612120809]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:567)[179:org.openhab.binding.zwave:2.0.0.201612120809]
at org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer.advanceNodeStage(ZWaveNodeInitStageAdvancer.java:1117)[179:org.openhab.binding.zwave:2.0.0.201612120809]
at org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer.handleNodeQueue(ZWaveNodeInitStageAdvancer.java:230)[179:org.openhab.binding.zwave:2.0.0.201612120809]
at org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer.ZWaveIncomingEvent(ZWaveNodeInitStageAdvancer.java:1306)[179:org.openhab.binding.zwave:2.0.0.201612120809]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:567)[179:org.openhab.binding.zwave:2.0.0.201612120809]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingResponseMessage(ZWaveController.java:293)[179:org.openhab.binding.zwave:2.0.0.201612120809]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:217)[179:org.openhab.binding.zwave:2.0.0.201612120809]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:208)[179:org.openhab.binding.zwave:2.0.0.201612120809]
at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1324)[179:org.openhab.binding.zwave:2.0.0.201612120809]
2016-12-12 21:22:18.514 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Size error 1<>2 from config_11_1
2016-12-12 21:22:18.516 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Size error 1<>2 from config_12_1
2016-12-12 21:22:18.556 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Initialising Thing Node…
2016-12-12 21:22:23.142 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Timeout while sending message. Requeueing - 2 attempts left!
2016-12-12 21:24:42.939 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Size error 1<>2 from config_11_1
2016-12-12 21:24:42.941 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Size error 1<>2 from config_12_1
2016-12-12 21:24:42.983 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Initialising Thing Node…

Some security command class messages I do not understand.

But the device seems to be ok. I get values for my defined items and I do see the “new” channels (low battery alarm, system alarm etc.).

I will leave it at that, but maybe it’s relevant for you, chris.

[chris (Chris Jackson)]

I guess you have security enabled in the controller? It’s probably best disabled at the moment.

[jaydee73 (Stefan)]

Hmm, I took a look and found this:

But I never changed this setting before. In fact, the advanced settings were always disabled.

So were does this setting come from? And in the description it’s mentioned that only entry control devices like locks will be included securely. So is this smoke sensor also an entry control device? Until now I thought that it isn’t.

And if it’s not, why does this produce error messages in the log?

I will switch over to “do not use security” and re-initialize the device again to see, if this prevents error messages in the log. But I can’t do this until this evening.

[chris (Chris Jackson)]

@jaydee73

So were does this setting come from?

What do you mean? It’s been there a long time already.

Maybe the error isn’t anything to do with this - I don’t know as there’s only 1 line really in the log so I’m guessing - sorry.

Some of the errors aren’t related to this, but generally having the security issue can prevent the device working properly so it’s best to eliminate this first.

[jaydee73 (Stefan)]

@chris

What do you mean? It’s been there a long time already.

Of course. I wanted to say “Is this the default setting?” So that the binding has defined this during the initial setup of the stick? Because I didn’t change the setting (AFAIK…).

Anyway. I will try again this evening with no security at all.

[chris (Chris Jackson)]

@jaydee73

I wanted to say “Is this the default setting?”

I’m not sure to be honest - at the moment, it really should be disabled completely as it just doesn’t work.

[skeal (Thomas)]

It seems to be default. My installation is defaulted to this, too.

[stivbert]

rule “smokeAlert”

when
Item zwave_device_158e8e1f486_node5_alarm_smoke received update ON
then
sendSms("+4530220000", “Alarm Brand”)
sendNotification(“alarm@mail.nu”, “så er der Alarm”)
end

use to work for me in oh1, but doesn’t seem to work in oh2

[stivbert]

in Association Groups
3: Device Status
it says pending…

i set Secure Inclusion Mode to do not use and reinitialised

[jaydee73 (Stefan)]

@stivbert

Item zwave_device_158e8e1f486_node5_alarm_smoke received update ON

I am surely no rule specialist, but I’ve never seen this expression. I know “received update” and I know “changed from OFF to ON”, but not your version. Maybe you’ll try changed off/on?

And pending means, that the new setting hasn’t yet been transmitted to the device. This happens automatically with the next wake up. If you want to transmit it now, you have to wake up the device manually (3x button press)

[stivbert]

wake up has been done… i don’t see any changes or updates form node 5 in my events

2016-12-13 17:45:36.427 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 5: Unknown command class 0x91
2016-12-13 17:45:52.128 [ERROR] [alization.ZWaveNodeInitStageAdvancer] - NODE 5: Node advancer: Retries exceeded at SET_ASSOCIATION
2016-12-13 17:46:05.921 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising Thing Node…
2016-12-13 17:46:06.462 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising Thing Node…

[stivbert]

well the rule works with the tamper(general alarm).

[mstormi (Markus Storm)]

@jaydee73

I am surely no rule specialist, but I’ve never seen this expression. I know “received update” and I know “changed from OFF to ON”, but not your version. Maybe you’ll try changed off/on?

That syntax is supposed to work. See here.

[mrohmann (Manuel Rohmann)]

I just read this threat since I’m also struggling with the fibaro smoke sensor. Just to be sure, I installed today the latest snapshot of openhab2 online distribution 2.0.0.201701091302

I’m not quite sure wether to open another threat or not, but I thinks it’s worth first to try it within this one.

Every time the device wakes up and every time i press the button in order to force an update of the temperature for example I get all alarms the sensor is able to send.

This is quite annoying. I’m not quite sure if a real alarm is fired the same way, but at the end currently the alarm channels are triggered with each wake up.

Perhaps I make something wrong, but I have no clue what this might be.

Any hints are very appreciated.
Thanks in advance.

Relevant lines from the trace log:

2017-01-08 14:25:53.355 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 11: Incoming command class ALARM
2017-01-08 14:25:53.359 [TRACE] [ssage.ApplicationCommandMessageClass] - NODE 11: Found Command Class ALARM, passing to handleApplicationCommandRequest
2017-01-08 14:25:53.363 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Received ALARM command V3
2017-01-08 14:25:53.375 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Process NOTIFICATION_REPORT V3
2017-01-08 14:25:53.379 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: NOTIFICATION report - 0 = 0, event=254, status=255
2017-01-08 14:25:53.383 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Alarm Type = BURGLAR (0)
2017-01-08 14:25:53.387 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2017-01-08 14:25:53.394 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-01-08 14:25:53.398 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2017-01-08 14:25:53.404 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:53.409 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:53.414 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 254, type OnOffType
2017-01-08 14:25:53.419 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating channel state zwave:device:876267ab:node11:alarm_tamper to ON [OnOffType]
2017-01-08 14:25:53.427 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:53.433 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:53.438 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:53.445 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Messa

2017-01-08 14:25:52.678 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 11: Incoming command class ALARM
2017-01-08 14:25:52.683 [TRACE] [ssage.ApplicationCommandMessageClass] - NODE 11: Found Command Class ALARM, passing to handleApplicationCommandRequest
2017-01-08 14:25:52.696 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Received ALARM command V3
2017-01-08 14:25:52.701 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Process NOTIFICATION_REPORT V3
2017-01-08 14:25:52.706 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: NOTIFICATION report - 0 = 0, event=254, status=255
2017-01-08 14:25:52.710 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Alarm Type = SMOKE (0)
2017-01-08 14:25:52.715 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2017-01-08 14:25:52.725 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-01-08 14:25:52.729 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2017-01-08 14:25:52.735 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:52.740 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 254, type OnOffType
2017-01-08 14:25:52.745 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating channel state zwave:device:876267ab:node11:alarm_smoke to ON [OnOffType]
2017-01-08 14:25:52.764 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:52.769 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:52.775 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:52.779 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:52.789 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=11, callback=78, payload=0B 05 71 04 00 01 01

2017-01-08 14:25:53.929 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 11: Incoming command class ALARM
2017-01-08 14:25:53.932 [TRACE] [ssage.ApplicationCommandMessageClass] - NODE 11: Found Command Class ALARM, passing to handleApplicationCommandRequest
2017-01-08 14:25:53.933 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Received ALARM command V3
2017-01-08 14:25:53.945 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Process NOTIFICATION_REPORT V3
2017-01-08 14:25:53.948 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: NOTIFICATION report - 0 = 0, event=254, status=255
2017-01-08 14:25:53.952 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Alarm Type = POWER_MANAGEMENT (0)
2017-01-08 14:25:53.956 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2017-01-08 14:25:53.969 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-01-08 14:25:53.973 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2017-01-08 14:25:53.978 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:53.989 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:53.992 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:53.996 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 254, type OnOffType
2017-01-08 14:25:54.009 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating channel state zwave:device:876267ab:node11:alarm_battery to ON [OnOffType]
2017-01-08 14:25:54.015 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:54.019 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION

2017-01-08 14:25:54.818 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 11: Incoming command class ALARM
2017-01-08 14:25:54.821 [TRACE] [ssage.ApplicationCommandMessageClass] - NODE 11: Found Command Class ALARM, passing to handleApplicationCommandRequest
2017-01-08 14:25:54.824 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Received ALARM command V3
2017-01-08 14:25:54.831 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Process NOTIFICATION_REPORT V3
2017-01-08 14:25:54.822 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Message is valid, sending ACK
2017-01-08 14:25:54.845 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT
2017-01-08 14:25:54.849 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Received SOF
2017-01-08 14:25:54.858 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: NOTIFICATION report - 0 = 0, event=1, status=255
2017-01-08 14:25:54.864 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Alarm Type = SYSTEM (0)
2017-01-08 14:25:54.868 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2017-01-08 14:25:54.875 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-01-08 14:25:54.887 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2017-01-08 14:25:54.891 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:54.880 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 0B 09 71 05 00 00 00 FF 04 FE 00 87
2017-01-08 14:25:54.877 [INFO ] [e.model.script.ZWave Daten empfangen] - 14:25:54 08.01.2017
2017-01-08 14:25:54.905 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 0F 00 04 00 0B 09 71 05 00 00 00 FF 04 FE 00 87
2017-01-08 14:25:54.909 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0x87
2017-01-08 14:25:54.917 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Checksum matched
2017-01-08 14:25:54.907 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:54.921 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:54.924 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:54.928 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 1, type OnOffType
2017-01-08 14:25:54.934 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Message payload = 00 0B 09 71 05 00 00 00 FF 04 FE 00
2017-01-08 14:25:54.937 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Message is valid, sending ACK
2017-01-08 14:25:54.939 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating channel state zwave:device:876267ab:node11:alarm_system to ON [OnOffType]
2017-01-08 14:25:54.948 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT
2017-01-08 14:25:54.952 [INFO ] [e.model.script.ZWave Daten empfangen] - 14:25:54 08.01.2017
2017-01-08 14:25:54.957 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION

2017-01-08 14:25:55.160 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 11: Incoming command class ALARM
2017-01-08 14:25:55.165 [TRACE] [ssage.ApplicationCommandMessageClass] - NODE 11: Found Command Class ALARM, passing to handleApplicationCommandRequest
2017-01-08 14:25:55.169 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Received ALARM command V3
2017-01-08 14:25:55.174 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Process NOTIFICATION_REPORT V3
2017-01-08 14:25:55.179 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: NOTIFICATION report - 0 = 0, event=254, status=255
2017-01-08 14:25:55.183 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 11: Alarm Type = HEAT (0)
2017-01-08 14:25:55.188 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2017-01-08 14:25:55.193 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-01-08 14:25:55.197 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2017-01-08 14:25:55.202 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:55.207 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:55.212 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:55.216 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:55.221 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-01-08 14:25:55.225 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 254, type OnOffType
2017-01-08 14:25:55.230 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating channel state zwave:device:876267ab:node11:alarm_heat to ON [OnOffType]

[chris (Chris Jackson)]

I think you are not using the latest binding? I see the binding is using the event 254 and I added a check for this last weekend.

Please update to the latest version and see if this works better - if not please post another log and I’ll take a look when I get a chance (might be Friday now though).

[mrohmann (Manuel Rohmann)]

Hi Chris, thanks a lot for ypur support. I will do so. I suggest to continue the conversation on the other thread if neccessary, because it’s completely relates to the fibaro smoke sensor.
Thanks for now.

Zwave Fibaro Smoke sensor / state change during regular wakeup

Sorry @mrohmann, but what are you talking about? Haven’t seen anything else in this thread from you. Is this related to the initial issue described in this thread?

[sintei (Nicke)]

I’m strugling with this smoke detector.

The TAMPER and TEMPERATURE is working.
However, SMOKE alarm is not.

I have a gen5 stick so it’s + compatible.
Latest snapshot of OH2 and from there I installed the z-wave binding so it’s also the latest.
Detector is in only one association group (1 and it is openhab controller).

Switch Fibaro1SmokeDectSmoke "Corridor Smoke Dect [%s]" (ZWave, gSmokeDetector) {channel="zwave:device:e25d115d:node14:alarm_smoke" }
Switch Fibaro1SmokeDectHeat  "Corridor Heat Dect [%s]" (ZWave, gSmokeDetector) {channel="zwave:device:e25d115d:node14:alarm_heat" }
Switch Fibaro1SmokeDectTamper  "Corridor Smoke Dect Tamper [%s]" (ZWave, gSmokeDetector) {channel="zwave:device:e25d115d:node14:alarm_tamper" }
Number  Fibaro1SmokeDectBattery  "Corridor Smoke Dect Battery level [%d %%]" (ZWave, gSmokeDetector) {channel="zwave:device:e25d115d:node14:battery-level", mqtt=">[brokerXXX:state:*:${state}]" }
Number  Fibaro1SmokeDectTemp  "Corridor Smoke Dect Temp [%.1f °C]" (ZWave, gSmokeDetector) {channel="zwave:device:e25d115d:node14:sensor_temperature", mqtt=">[brokerXXX/state:state:*:${state}]" }

When I blow smoke in the detector and it goes off, nothing happens.
But when it goes silent, it sends “OFF”.
Am I missing something really silly in my items file or configuration of the device?

According to logs I can see that it sends 255

@chris, you had one of these detectors, how did you set it up?

13:09:49.067	14	
RX REQ ApplicationCommandHandler SENSOR_MULTI_LEVEL_REPORT TEMPERATURE=34
13:09:49.069	14	
STATE UPDATE zwave:device:e25d115d:node14:sensor_temperature 25.5 [DecimalType]
13:09:49.582	14	
RX REQ ApplicationCommandHandler ALARM_REPORT SMOKE
13:09:49.670	14	
RX REQ ApplicationCommandHandler SENSOR_ALARM_REPORT SMOKE=255
13:09:49.711	14	
RX REQ ApplicationCommandHandler SENSOR_ALARM_REPORT SMOKE=255
13:09:49.835	14	
RX REQ ApplicationCommandHandler BASIC_SET
13:09:49.873	14	
RX REQ ApplicationCommandHandler BASIC_SET
13:10:12.252	14	
RX REQ ApplicationCommandHandler SENSOR_MULTI_LEVEL_REPORT TEMPERATURE=34
13:10:12.255	14	
STATE UPDATE zwave:device:e25d115d:node14:sensor_temperature 26.7 [DecimalType]
13:10:32.367	14	
RX REQ ApplicationCommandHandler SENSOR_MULTI_LEVEL_REPORT TEMPERATURE=34
13:10:32.369	14	
STATE UPDATE zwave:device:e25d115d:node14:sensor_temperature 27.8 [DecimalType]
13:11:08.978	14	
RX REQ ApplicationCommandHandler SENSOR_MULTI_LEVEL_REPORT TEMPERATURE=34
13:11:08.980	14	
STATE UPDATE zwave:device:e25d115d:node14:sensor_temperature 28.8 [DecimalType]
13:11:50.309	14	
RX REQ ApplicationCommandHandler ALARM_REPORT SMOKE
13:11:50.311	14	
STATE UPDATE zwave:device:e25d115d:node14:alarm_smoke OFF [OnOffType]
13:11:50.397	14	
RX REQ ApplicationCommandHandler SENSOR_ALARM_REPORT SMOKE=0
13:11:50.439	14	
RX REQ ApplicationCommandHandler SENSOR_ALARM_REPORT SMOKE=0
13:11:50.563	14	
RX REQ ApplicationCommandHandler BASIC_SET
13:11:50.601	14	
RX REQ ApplicationCommandHandler BASIC_SET
13:12:48.814	14	
RX REQ ApplicationCommandHandler SENSOR_MULTI_LEVEL_REPORT TEMPERATURE=34
13:12:48.817	14	
STATE UPDATE zwave:device:e25d115d:node14:sensor_temperature 27.8 [DecimalType]
13:15:28.764	14	
RX REQ ApplicationCommandHandler SENSOR_MULTI_LEVEL_REPORT TEMPERATURE=34
13:15:28.767	14	
STATE UPDATE zwave:device:e25d115d:node14:sensor_temperature 26.8 [DecimalType]

Full log can be found here: https://www.dropbox.com/s/6adodsvs0vg2x94/openhab.log?dl=0

[chris (Chris Jackson)]

Can you provide the XML file for this device. It looks like it’s using a different event than other devices.

[sintei (Nicke)]

@Chris, sure thing.
xml file is here:

node14.xml

[sintei (Nicke)]

Hey @chris, did you see anything to get this resolved?