Fibaro Smoke Alarm

Configuration Z-Wave
1

Hi,

Sometimes the Fibaro smoke alarm starts without warning. We only have this with one sensor (there are 4 installed). The value’s in the entities do not match that to other examples here on the forum (when fire is detected).

This is my zwave log, how do I know which entity sends this alert?

**2020-11-04 19:35:15.212 Info, Node002, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Smoke event:2, status=255**
**2020-11-04 19:35:15.212 Detail, Node002, Refreshed Value: old value=0, new value=0, type=byte**
**2020-11-04 19:35:15.213 Detail, Node002, Changes to this value are not verified**
**2020-11-04 19:35:15.213 Detail, Node002, Refreshed Value: old value=0, new value=0, type=byte**
**2020-11-04 19:35:15.213 Detail, Node002, Changes to this value are not verified**
**2020-11-04 19:35:15.213 Detail, Node002, Refreshed Value: old value=0, new value=0, type=byte**
**2020-11-04 19:35:15.213 Detail, Node002, Changes to this value are not verified**
**2020-11-04 19:35:15.213 Detail, Node002, Refreshed Value: old value=254, new value=2, type=byte**
**2020-11-04 19:35:15.213 Detail, Node002, Changes to this value are not verified**
2020-11-04 19:35:15.213 Detail, Node002, Notification: ValueChanged
2020-11-04 19:35:15.220 Detail, Node002, Notification: ValueChanged
2020-11-04 19:35:15.227 Detail, Node002, Notification: ValueChanged
2020-11-04 19:35:15.235 Detail, Node002, Notification: ValueChanged
2020-11-04 19:35:19.235 Detail, Node002,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x02, 0x02, 0x98, 0x40, 0x2b
2020-11-04 19:35:19.235 Info, Node002, Received SecurityCmd_NonceGet from node 2
2020-11-04 19:35:19.236 Info, NONCES: 0x6c, 0x71, 0xa3, 0xf6, 0x6d, 0xca, 0x16, 0xbb
2020-11-04 19:35:19.236 Info, NONCES: 0x60, 0xa7, 0xeb, 0xd3, 0x68, 0x05, 0xbc, 0x56
2020-11-04 19:35:19.236 Info, NONCES: 0x25, 0x53, 0x50, 0xe8, 0x9d, 0x34, 0xf8, 0x64
2020-11-04 19:35:19.236 Info, NONCES: 0xb3, 0xd1, 0xb9, 0xee, 0xad, 0xf3, 0x5e, 0x81
2020-11-04 19:35:19.236 Info, NONCES: 0x63, 0x76, 0x2c, 0x86, 0x8e, 0xb4, 0xe0, 0x31
2020-11-04 19:35:19.236 Info, NONCES: 0xd9, 0x49, 0x6e, 0x4e, 0xdb, 0xfe, 0x81, 0xe2
2020-11-04 19:35:19.236 Info, NONCES: 0x18, 0xdc, 0x17, 0xbb, 0xd2, 0xe1, 0xaf, 0xf9
2020-11-04 19:35:19.236 Info, NONCES: 0x8c, 0xd0, 0x1f, 0x8f, 0x81, 0xb4, 0x8a, 0xb9
2020-11-04 19:35:19.236 Info, Node002, Sending (WakeUp) message (Callback ID=0x01, Expected Reply=0x00) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x02, 0x0a, 0x98, 0x80, 0xb3, 0xd1, 0xb9, 0xee, 0xad, 0xf3, 0x5e, 0x81, 0x05, 0x01, 0x5d:
2020-11-04 19:35:19.244 Detail,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-11-04 19:35:19.244 Detail,   ZW_SEND_DATA delivered to Z-Wave stack
2020-11-04 19:35:19.260 Detail,   Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x02, 0xe8
2020-11-04 19:35:19.260 Detail,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2020-11-04 19:35:19.281 Detail, Node002,   Received: 0x01, 0x24, 0x00, 0x04, 0x00, 0x02, 0x1e, 0x98, 0x81, 0xa5, 0x56, 0x62, 0x23, 0x95, 0xf0, 0x68, 0x38, 0x61, 0xfd, 0x1c, 0x44, 0x2b, 0xfa, 0x17, 0x2a, 0xa8, 0x04, 0x5f, 0xb3, 0x55, 0x0f, 0x75, 0x72, 0xb5, 0x5f, 0x74, 0x65, 0x93
2020-11-04 19:35:19.281 Info, Raw: 0x98, 0x81, 0xa5, 0x56, 0x62, 0x23, 0x95, 0xf0, 0x68, 0x38, 0x61, 0xfd, 0x1c, 0x44, 0x2b, 0xfa, 0x17, 0x2a, 0xa8, 0x04, 0x5f, 0xb3, 0x55, 0x0f, 0x75, 0x72, 0xb5, 0x5f, 0x74, 0x65, 0x93
2020-11-04 19:35:19.281 Detail, Node002, Decrypted Packet: 0x00, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x01, 0x00, 0x01, 0x02
2020-11-04 19:35:19.281 Detail,
**2020-11-04 19:35:19.281 Info, Node002, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Smoke event:0, status=255**
**2020-11-04 19:35:19.281 Detail, Node002, Refreshed Value: old value=0, new value=0, type=byte**
**2020-11-04 19:35:19.281 Detail, Node002, Changes to this value are not verified**
**2020-11-04 19:35:19.281 Detail, Node002, Refreshed Value: old value=0, new value=0, type=byte**
**2020-11-04 19:35:19.281 Detail, Node002, Changes to this value are not verified**
**2020-11-04 19:35:19.281 Detail, Node002, Refreshed Value: old value=0, new value=0, type=byte**
**2020-11-04 19:35:19.281 Detail, Node002, Changes to this value are not verified**
**2020-11-04 19:35:19.281 Detail, Node002, Refreshed Value: old value=2, new value=0, type=byte**
2020-11-04 19:35:19.281 Detail, Node002, Changes to this value are not verified
2020-11-04 19:35:19.281 Detail, Node002, Notification: ValueChanged
2020-11-04 19:35:19.287 Detail, Node002, Notification: ValueChanged
2020-11-04 19:35:19.294 Detail, Node002, Notification: ValueChanged
2020-11-04 19:35:19.300 Detail, Node002, Notification: ValueChanged
2

Node 2 it is, see all 4 entities, it shows the node id on the bottom if you click an entity

3

Hi, I know which device it is, (my fault should have said that), I meant the sensor entities (sensor.fibaro_system_fgsd002_smoke_sensor_smoke).

Is there an easy way to identify which sensor gets triggerd based on the zwave log?

2020-11-04 19:35:15.212 Info, Node002, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Smoke event:2, status=255**

4

Sorry I don’t get what your asking then. The zwave id is unique and linked to an entity (not the entity name). In home assistant you can see the zwave id when you click on the entity.