Problem with Fibaro CO sensor and Fibaro Wall Plug in OpenHAB2

Bredmich · January 31, 2019, 9:27am

I´m struggeling with the same problem here.
Just tried to get the CO sensor running…

Currently i only get the temperature and battery level.
The co level is still NaN…

I already tried to associate the channels to the Controller but that don´t change anything.

The description of some configuration parameters make me think that the CO sensor can´t report the actual CO level.
But the Fibaro website shows some screenshots where the value is shown in the Fibaro app…
On the other hand parameter 23 and 25 describe reporting the CO level in general and after a change of 10 ppm.

kind regards
Michael

HomeAutomation · February 22, 2019, 8:18am

have you ever fixed this? It is the same on my side. battery and temperatur is working well. CO-level and CO-alarm not.

How to test CO-alarm status? Is it triggered if I use the test button? In the doc is written, that this will be not the case.

Rintano · February 22, 2019, 10:10am

Sry. Till yet no fix

chris · February 22, 2019, 1:51pm

Please provide a debug log showing the data that is received.

HomeAutomation · February 22, 2019, 1:55pm

hi chris,

I will do this, but not sure how often the CO value will be send from device. Cound be a long log

HomeAutomation · February 22, 2019, 6:30pm

I made a debug log for the fibaro FGCD-001 CO-Sensor. The related node is 82. I pushed the test button on the device an force to send the CO Alarm status. But the item does not change from NULL to anything. Hopefully the log helps.

temperature and battery is working fine, CO alarm and CO value not.

2019-02-22 19:20:45.757 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 52 02 84 07 20 
2019-02-22 19:20:45.762 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=82, callback=0, payload=00 52 02 84 07 
2019-02-22 19:20:45.764 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=82, callback=0, payload=00 52 02 84 07 
2019-02-22 19:20:45.765 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-02-22 19:20:45.767 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Application Command Request (ALIVE:DONE)
2019-02-22 19:20:45.768 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: resetResendCount initComplete=true isDead=false
2019-02-22 19:20:45.770 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Is awake with 0 messages in the queue
2019-02-22 19:20:45.771 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Start sleep timer at 1000ms
2019-02-22 19:20:45.772 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2019-02-22 19:20:45.789 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 82: Node Status event - Node is AWAKE
2019-02-22 19:20:45.790 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Commands processed 1.
2019-02-22 19:20:45.790 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@6afcbf.
2019-02-22 19:20:45.791 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-02-22 19:20:45.792 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-02-22 19:20:45.792 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:20:45.797 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-02-22 19:20:46.272 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: WakeupTimerTask 0 Messages waiting, state DONE
2019-02-22 19:20:46.772 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: WakeupTimerTask 0 Messages waiting, state DONE
2019-02-22 19:20:46.774 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: No more messages, go back to sleep
2019-02-22 19:20:46.776 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 82: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2019-02-22 19:20:46.778 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: SECURITY NOT required on COMMAND_CLASS_WAKE_UP
2019-02-22 19:20:46.779 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured
2019-02-22 19:20:46.781 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@1fe760b
2019-02-22 19:20:46.786 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Bump transaction 16428 priority from Immediate to Immediate
2019-02-22 19:20:46.788 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Adding to device queue
2019-02-22 19:20:46.790 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Added 16428 to queue - size 40
2019-02-22 19:20:46.792 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-02-22 19:20:46.804 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 52 02 84 08 25 75 69 
2019-02-22 19:20:46.809 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 82: Sending REQUEST Message = 01 09 00 13 52 02 84 08 25 75 69 
2019-02-22 19:20:46.811 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2019-02-22 19:20:46.813 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2019-02-22 19:20:46.813 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 16428: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 117
2019-02-22 19:20:46.815 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2019-02-22 19:20:46.818 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2019-02-22 19:20:46.820 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 16428: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 117
2019-02-22 19:20:46.821 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2019-02-22 19:20:46.821 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2019-02-22 19:20:46.822 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:20:46.824 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2019-02-22 19:20:46.824 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2019-02-22 19:20:46.825 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2019-02-22 19:20:46.826 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 16428: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 117
2019-02-22 19:20:46.827 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2019-02-22 19:20:46.828 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 16428: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 117
2019-02-22 19:20:46.830 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2019-02-22 19:20:46.831 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 82: sentData successfully placed on stack.
2019-02-22 19:20:46.832 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 16428: Advanced to WAIT_REQUEST
2019-02-22 19:20:46.834 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: TID 16428: Transaction not completed
2019-02-22 19:20:46.835 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:20:46.836 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2019-02-22 19:20:46.836 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 75 00 00 02 9C 
2019-02-22 19:20:46.840 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=117, payload=75 00 00 02 
2019-02-22 19:20:46.842 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=117, payload=75 00 00 02 
2019-02-22 19:20:46.843 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 16428: [WAIT_REQUEST] priority=Immediate, requiresResponse=true, callback: 117
2019-02-22 19:20:46.844 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2019-02-22 19:20:46.845 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 16428: [WAIT_REQUEST] priority=Immediate, requiresResponse=true, callback: 117
2019-02-22 19:20:46.847 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 16428: (Callback 117)
2019-02-22 19:20:46.849 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2019-02-22 19:20:46.850 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 16428: callback 117
2019-02-22 19:20:46.851 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=117, payload=75 00 00 02 
2019-02-22 19:20:46.853 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 82: SendData Request. CallBack ID = 117, Status = Transmission complete and ACK received(0)
2019-02-22 19:20:46.854 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: resetResendCount initComplete=true isDead=false
2019-02-22 19:20:46.854 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 16428: Transaction COMPLETED
2019-02-22 19:20:46.855 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Response processed after 42ms
2019-02-22 19:20:46.856 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: TID 16428: Transaction completed
2019-02-22 19:20:46.857 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: notifyTransactionResponse TID:16428 DONE
2019-02-22 19:20:46.858 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2019-02-22 19:20:46.859 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:20:46.859 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 16428: Transaction event listener: DONE: DONE -> 
2019-02-22 19:20:46.860 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-02-22 19:20:46.860 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Went to sleep COMPLETE
2019-02-22 19:20:47.541 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 52 02 84 07 20 
2019-02-22 19:20:47.544 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=82, callback=0, payload=00 52 02 84 07 
2019-02-22 19:20:47.545 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=82, callback=0, payload=00 52 02 84 07 
2019-02-22 19:20:47.546 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-02-22 19:20:47.547 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Application Command Request (ALIVE:DONE)
2019-02-22 19:20:47.548 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: resetResendCount initComplete=true isDead=false
2019-02-22 19:20:47.549 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Is awake with 0 messages in the queue
2019-02-22 19:20:47.549 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Start sleep timer at 1000ms
2019-02-22 19:20:47.550 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2019-02-22 19:20:47.562 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 82: Node Status event - Node is AWAKE
2019-02-22 19:20:47.563 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Commands processed 1.
2019-02-22 19:20:47.564 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@ee7bd4.
2019-02-22 19:20:47.564 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-02-22 19:20:47.565 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-02-22 19:20:47.566 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:20:47.567 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-02-22 19:20:48.051 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: WakeupTimerTask 0 Messages waiting, state DONE
2019-02-22 19:20:48.551 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: WakeupTimerTask 0 Messages waiting, state DONE
2019-02-22 19:20:48.553 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: No more messages, go back to sleep
2019-02-22 19:20:48.554 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 82: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2019-02-22 19:20:48.555 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: SECURITY NOT required on COMMAND_CLASS_WAKE_UP
2019-02-22 19:20:48.556 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured
2019-02-22 19:20:48.557 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@edae91
2019-02-22 19:20:48.559 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Bump transaction 16429 priority from Immediate to Immediate
2019-02-22 19:20:48.563 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Adding to device queue
2019-02-22 19:20:48.565 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Added 16429 to queue - size 40
2019-02-22 19:20:48.567 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-02-22 19:20:48.571 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 52 02 84 08 25 76 6A 
2019-02-22 19:20:48.574 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 82: Sending REQUEST Message = 01 09 00 13 52 02 84 08 25 76 6A 
2019-02-22 19:20:48.576 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2019-02-22 19:20:48.577 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 16429: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 118
2019-02-22 19:20:48.577 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2019-02-22 19:20:48.579 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2019-02-22 19:20:48.581 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2019-02-22 19:20:48.582 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 16429: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 118
2019-02-22 19:20:48.583 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2019-02-22 19:20:48.584 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:20:48.585 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2019-02-22 19:20:48.585 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2019-02-22 19:20:48.587 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2019-02-22 19:20:48.589 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2019-02-22 19:20:48.590 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 16429: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 118
2019-02-22 19:20:48.591 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2019-02-22 19:20:48.592 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 16429: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 118
2019-02-22 19:20:48.593 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2019-02-22 19:20:48.593 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 82: sentData successfully placed on stack.
2019-02-22 19:20:48.594 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 16429: Advanced to WAIT_REQUEST
2019-02-22 19:20:48.594 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: TID 16429: Transaction not completed
2019-02-22 19:20:48.595 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:20:48.595 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2019-02-22 19:20:48.600 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 76 00 00 03 9E 
2019-02-22 19:20:48.602 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=118, payload=76 00 00 03 
2019-02-22 19:20:48.603 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=118, payload=76 00 00 03 
2019-02-22 19:20:48.603 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 16429: [WAIT_REQUEST] priority=Immediate, requiresResponse=true, callback: 118
2019-02-22 19:20:48.604 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2019-02-22 19:20:48.605 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 16429: [WAIT_REQUEST] priority=Immediate, requiresResponse=true, callback: 118
2019-02-22 19:20:48.605 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 16429: (Callback 118)
2019-02-22 19:20:48.606 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2019-02-22 19:20:48.606 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 16429: callback 118
2019-02-22 19:20:48.607 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=118, payload=76 00 00 03 
2019-02-22 19:20:48.608 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 82: SendData Request. CallBack ID = 118, Status = Transmission complete and ACK received(0)
2019-02-22 19:20:48.609 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: resetResendCount initComplete=true isDead=false
2019-02-22 19:20:48.609 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 16429: Transaction COMPLETED
2019-02-22 19:20:48.610 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Response processed after 33ms
2019-02-22 19:20:48.610 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: TID 16429: Transaction completed
2019-02-22 19:20:48.611 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: notifyTransactionResponse TID:16429 DONE
2019-02-22 19:20:48.612 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2019-02-22 19:20:48.612 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:20:48.612 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 16429: Transaction event listener: DONE: DONE -> 
2019-02-22 19:20:48.613 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-02-22 19:20:48.613 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Went to sleep COMPLETE
2019-02-22 19:20:49.225 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 52 02 84 07 20 
2019-02-22 19:20:49.228 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=82, callback=0, payload=00 52 02 84 07 
2019-02-22 19:20:49.230 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=82, callback=0, payload=00 52 02 84 07 
2019-02-22 19:20:49.231 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-02-22 19:20:49.232 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Application Command Request (ALIVE:DONE)
2019-02-22 19:20:49.233 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: resetResendCount initComplete=true isDead=false
2019-02-22 19:20:49.235 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Is awake with 0 messages in the queue
2019-02-22 19:20:49.236 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Start sleep timer at 1000ms
2019-02-22 19:20:49.237 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2019-02-22 19:20:49.254 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 82: Node Status event - Node is AWAKE
2019-02-22 19:20:49.254 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Commands processed 1.
2019-02-22 19:20:49.255 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1bfcf2a.
2019-02-22 19:20:49.256 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-02-22 19:20:49.256 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-02-22 19:20:49.257 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:20:49.257 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-02-22 19:20:49.738 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: WakeupTimerTask 0 Messages waiting, state DONE
2019-02-22 19:20:50.239 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: WakeupTimerTask 0 Messages waiting, state DONE
2019-02-22 19:20:50.241 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: No more messages, go back to sleep
2019-02-22 19:20:50.242 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 82: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2019-02-22 19:20:50.243 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: SECURITY NOT required on COMMAND_CLASS_WAKE_UP
2019-02-22 19:20:50.243 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured
2019-02-22 19:20:50.244 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@135eb07
2019-02-22 19:20:50.245 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Bump transaction 16430 priority from Immediate to Immediate
2019-02-22 19:20:50.246 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Adding to device queue
2019-02-22 19:20:50.247 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Added 16430 to queue - size 40
2019-02-22 19:20:50.247 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-02-22 19:20:50.249 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 52 02 84 08 25 77 6B 
2019-02-22 19:20:50.251 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 82: Sending REQUEST Message = 01 09 00 13 52 02 84 08 25 77 6B 
2019-02-22 19:20:50.252 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2019-02-22 19:20:50.253 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 16430: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 119
2019-02-22 19:20:50.253 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2019-02-22 19:20:50.254 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2019-02-22 19:20:50.255 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2019-02-22 19:20:50.255 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 16430: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 119
2019-02-22 19:20:50.256 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2019-02-22 19:20:50.256 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:20:50.257 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2019-02-22 19:20:50.260 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2019-02-22 19:20:50.261 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2019-02-22 19:20:50.262 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2019-02-22 19:20:50.263 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 16430: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 119
2019-02-22 19:20:50.264 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2019-02-22 19:20:50.265 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 16430: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 119
2019-02-22 19:20:50.266 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 
2019-02-22 19:20:50.267 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 82: sentData successfully placed on stack.
2019-02-22 19:20:50.267 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 16430: Advanced to WAIT_REQUEST
2019-02-22 19:20:50.268 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: TID 16430: Transaction not completed
2019-02-22 19:20:50.268 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:20:50.269 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2019-02-22 19:20:50.277 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 77 00 00 02 9E 
2019-02-22 19:20:50.279 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=119, payload=77 00 00 02 
2019-02-22 19:20:50.280 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=119, payload=77 00 00 02 
2019-02-22 19:20:50.281 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 16430: [WAIT_REQUEST] priority=Immediate, requiresResponse=true, callback: 119
2019-02-22 19:20:50.281 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2019-02-22 19:20:50.282 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 16430: [WAIT_REQUEST] priority=Immediate, requiresResponse=true, callback: 119
2019-02-22 19:20:50.283 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 16430: (Callback 119)
2019-02-22 19:20:50.284 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2019-02-22 19:20:50.285 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 16430: callback 119
2019-02-22 19:20:50.286 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=119, payload=77 00 00 02 
2019-02-22 19:20:50.287 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 82: SendData Request. CallBack ID = 119, Status = Transmission complete and ACK received(0)
2019-02-22 19:20:50.288 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: resetResendCount initComplete=true isDead=false
2019-02-22 19:20:50.288 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 16430: Transaction COMPLETED
2019-02-22 19:20:50.289 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: Response processed after 37ms
2019-02-22 19:20:50.290 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: TID 16430: Transaction completed
2019-02-22 19:20:50.291 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 82: notifyTransactionResponse TID:16430 DONE
2019-02-22 19:20:50.293 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 82: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2019-02-22 19:20:50.294 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:20:50.294 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-02-22 19:20:50.299 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 16430: Transaction event listener: DONE: DONE -> 
2019-02-22 19:20:50.300 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 82: Went to sleep COMPLETE
2019-02-22 19:21:06.766 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 4D 04 30 03 00 0C 87 
2019-02-22 19:21:06.769 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=77, callback=0, payload=00 4D 04 30 03 00 0C 
2019-02-22 19:21:06.770 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=77, callback=0, payload=00 4D 04 30 03 00 0C 
2019-02-22 19:21:06.771 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-02-22 19:21:06.772 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 77: Application Command Request (ALIVE:DONE)
2019-02-22 19:21:06.773 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 77: resetResendCount initComplete=true isDead=false
2019-02-22 19:21:06.773 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 77: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2019-02-22 19:21:06.774 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 77: SECURITY NOT required on COMMAND_CLASS_SENSOR_BINARY
2019-02-22 19:21:06.774 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 77: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
2019-02-22 19:21:06.775 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 12
2019-02-22 19:21:06.776 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is MOTION
2019-02-22 19:21:06.776 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 77: Sensor Binary report, type=Motion, value=0
2019-02-22 19:21:06.778 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 77: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2019-02-22 19:21:06.778 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 77: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_BINARY, value = 0
2019-02-22 19:21:06.779 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 77: Updating channel state zwave:device:15a7a49f3a6:node77:sensor_binary to OFF [OnOffType]
2019-02-22 19:21:06.780 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 77: Commands processed 1.
2019-02-22 19:21:06.781 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 77: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@56c77c.
2019-02-22 19:21:06.782 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-02-22 19:21:06.782 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-02-22 19:21:06.783 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-22 19:21:06.784 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

HomeAutomation · February 22, 2019, 6:42pm

Update:
Tamper in also not working.

brononius · May 26, 2019, 7:26pm

Did you manage to read the CO value?
Same issue over here, battery & temperature values are OK. But no CO2 values…

Rintano · May 27, 2019, 1:44pm

No, the only thing it works is the temperature sensor. Even the battery shows the whole time 100% even if the CO sensor already give out beeping noices because the battery need to be changed.

I changed the CO sensor with a candle, with CO spray… no value from the device. There is something broken

chris · May 27, 2019, 2:19pm

Sorry - I’ve just seen this (I don’t get notifications if it’s not sent as a reply).

This log only have a single binary sensor report in it, and this is updated correctly.

I don’t know what the report actually is, but this is the only thing in the log, and it does update the binary sensor channel.

brononius · July 5, 2019, 7:09am

I checked with Fibaro helpdesk, and this was their answer:

You need to change the value of parameter 23. CO meter activation to 1.
Also parameter 14 can be adjusted. It might now be sending reports as long as there is no expected level of CO in the environment.

In my case, Parameter 23 was 1, Parameter 14 = 25 and Parameter 17 = 10.
So at first sight, everything seems OK.

But what I don’t get, is the 4th group option. Does this mean that only in this group will values be sent? Or does OpenHAB picks this up nevertheless?
If not, is it enought to put this to ‘controller’? With other words, does controller means openhab? Or the zwave dongle? I’m asking because I use 2 usb Gen5 sticks.

TomS · August 3, 2019, 12:44pm

Anyone managed to get this Fibaro CO sensor to send the CO values to OpenHab? Also tried the same but no luck so far…

From the PDF (available also here: https://manuals.fibaro.com/content/manuals/en/FGCD-001/FGCD-001-EN-T-v1.1.pdf) I can see the following description on page 15:

FromManualCoMeterActivation

On page 10 I can also read the following
“Association ensures direct transfer of control commands between devices, is performed without participation of the main controller and requires associated device to be in the direct range.”

With this I really don’t assume we have to associate the controler with any association group to receive the CO values. Still I tried to assign the Controller via HABmin to all association groups but still no luck.

Also Zwave debug logs shows me that OH receives temperature and battery level but NO CO values.

Anyone managed to get the values?

TomS · August 3, 2019, 1:24pm

Just managed to get values for co meter reported to OH!

the Fibaro CO sensor will only report CO values in case the value is above paramter 26. which is per default 30 ppm. As in my environment or sensor location (living room plus Ventilation) it looks like per default the CO value is always less than 10 ppm or close to 0 even, never a value was reported to the controller.

CoMeterParamter

I lowered the threshold to 10 and quickly did some tests to increase the CO value for a moment ( don’t ask how; but my car was involved ) and suddenly I got values reported. No special association group config etc. was req.

My in use parameters:
Parameter 25: 2 (lowest possible parameter)
Parameter 26: 10 ppm (lowest possible parameter)

Example from events.log:
2019-08-03 14:53:17.685 [vent.ItemStateChangedEvent] - CoSensor01_AlarmCO changed from NULL to ON
2019-08-03 14:53:23.029 [vent.ItemStateChangedEvent] - CoSensor01_CarbonMonoxideSensor changed from NULL to 3514
2019-08-03 14:53:43.901 [vent.ItemStateChangedEvent] - CoSensor01_CarbonMonoxideSensor changed from 3514 to 1280
2019-08-03 14:54:20.686 [vent.ItemStateChangedEvent] - CoSensor01_CarbonMonoxideSensor changed from 1280 to 68
2019-08-03 14:54:44.549 [vent.ItemStateChangedEvent] - CoSensor01_CarbonMonoxideSensor changed from 68 to 45
2019-08-03 14:55:14.862 [vent.ItemStateChangedEvent] - CoSensor01_CarbonMonoxideSensor changed from 45 to 31
2019-08-03 14:55:50.539 [vent.ItemStateChangedEvent] - CoSensor01_AlarmCO changed from ON to OFF
2019-08-03 14:56:15.478 [vent.ItemStateChangedEvent] - CoSensor01_CarbonMonoxideSensor changed from 31 to 17
2019-08-03 14:58:11.386 [vent.ItemStateChangedEvent] - CoSensor01_CarbonMonoxideSensor changed from 17 to 0

As you can see the Sensor went back to CarbonMonoxideSensor value 0 at the very end and will not report any values to OH anymore unless value is above 10 again.

I hope this helps others as well!

Regards,
Thomas

sihui · August 3, 2019, 3:18pm

You definitely have to associate the lifeline association group to your controller. If you are using a recent 2.5 snapshot zwave binding this is done automatically, you won’t even notice.

That causes trouble and errors in your setup. The other association groups are for direct associations to other devices, not to your controller. If you set these to your controller you likely get problems.

TomS · August 5, 2019, 6:39pm

Thanks a lot, did some more reading and I assume I got it (at least high level). For me the discussion here ZWave - Lifeline vs Controller updates vs Device status was quite helpful to understand whats going on.
In short: With ZwavePlus devices (like the Fibaro CO Sensor), the so called “Lifeline” accociation group (with ID 1 according ZwavePlus spec) is responsible to send (ALL) updates to the controller. In this Lifeline group the controller (node_1) must be listed so OpenHAB receives ALL updates from the Device.

This is the case in PaperUI (Things -> MyCOSensor1 -> Edit -> Association Groups and I still have node_1 in all the other association groups. I will remove node_1 again from all Association groups and will only keep Group 1 (Lifeline) assigned to node_1 and will give it a try again (will check if I still receive the alerts and CO values) as recommended by you.

What confused me was that in HABmin all the accociation groups are empty, in PaperUI they are still populated. Maybe an issue with HABmin?

Anyway I will ignore HABmin as I assume its more or less not maintained anymore and will focus on PaperUI.

Regards,
Thomas

PS: I use OH 2.4 stable

sihui · August 5, 2019, 7:11pm

Just a display bug.
HABmin is specially designed for zwave and fully functional.
Changing config parameters for zwave devices via PaperUI can cause trouble. Use HABmin

ei_Gelb_Geek · August 5, 2019, 9:08pm

3514 ppm ?!?! Is this really a valid Value ???

Technical Data of the Sensor: CO concentration measurement range: 0 – 450 ppm

TomS · August 6, 2019, 7:08pm

you are right, according the pdf (Operating Manual) from above it only measures up to 450 ppm?! But on the other side according to e.g. https://www.detectcarbonmonoxide.com/co-health-risks/ and the table the value reported could be fine or at least is not implausible.

Also ZWAVE Debug has the same value:
event.log
2019-08-03 14:53:23.029 [vent.ItemStateChangedEvent] - CoSensor01_CarbonMonoxideSensor changed from NULL to 3514

Zwave debug:

I hope simply the PDF is incorrect or they try to say above 450ppm the value in not too accurate anymore. No idea…

robmac · August 8, 2019, 8:31pm

Regarding the high levels I am not sure why you would be interested unless you are making sure the atmosphere is dangerous. As to the other end of the scale there is a general issue with CO sensors. They do not actually detect WHO recommended levels of CO.

From a conversation regarding CO sensor with Fibaro.

Me

[Posted May 8, 2017](https://forum.fibaro.com/topic/25294-co-sensor-fgcd-001/?

It was the note in the manual about this unit not protecting from long term low level so I decided to do a bit of research to see what that might be about. Think this explains potential risks this device does not protect you from.

I am guessing this is a general issue for all CO sensors. I will have to check out the ones I have installed.

"The World Health Organisation issued the following guidelines for levels of CO in the air, to prevent blood COHb levels from rising above 2.5%

100 mg/m3 (87.1 ppm) for 15 minutes

60 mg/m3 (52.3 ppm) for 30 minutes

30 mg/m3 (26.1 ppm) for 1 hour

10 mg/m3 (8.7 ppm) for 8 hours."

Alarm settings on Fibaro device 50ppm 60-90 minutes when WHO are setting 30 minutes as the length of exposure at this concentration. That is from 2 to 3* the recommended exposure time before the alarm sounds.

Can anyone from @Fibaro explain why the difference in these figures. Is it just that making a CO sensor to WHO levels is not possible? Have I lived under a false sense of security for my family for years using CO sensors? Are Fibaro just managing the same level as other sensors or is this below par?

Reply from Fibaro

Posted May 8, 2017

There are strict norms which device like this should maintain - as our CO Sensor will be certified we just must comply with them.

WHO issued quidelines, those are not norms.

To test CO detection in safe way you can use a candle and glass bowl - just light the candle, but it near CO Detector and cover both of them with a bowl.

I did then check other sensors on the market and Fibaro are not being disingenuous. Their sensor is normal and WHO levels are not achieved by any retail CO sensor I could find. The EU and US standards are both outside WHO levels.

Also another way to test your CO sensor than sticking it up your car exhaust. Almost as much fun.

Florian_Spatz · May 25, 2020, 2:02pm

I just installed 2 Fibaro CO Sensors and as the other people reported they are not working as expected at all. Did anyone manage to fix this?
I have also multiple Fibaro Smoke Sensors in use and they behave absolutely as expected.
I’m seeing the following issues:

No reporting of Tamper Alarm
CO Alarm does not switch back to off
no reporting of CO ppm (that might be OK as the levels are too low)

Configuration: I put only the Controller in the Lifeline Assosciation group, no other assosciation group
Device Firmware 3.2

When looking at the attached log it seems that all data is received but the other channels other than the CO channel are not correct in the database.

Any help here would be really appreciated.

fibaro_co.log (3.1 KB)