The metrics was working fine until the device lost connectivity with the hub I just wanted to be informed when the metrics stopped reporting. My battery is still showing 100% and reported twice today (before it disconnected again).
@Mariano_Colmenarejo
Here are my CLI logs. I am using the wifi hub. Any reason why the hub thinks it is offline? Tapping the physical button works, so it has enough power to run the actuators. Last time it worked, it said the battery was 100%. Any thoughts? During the logs, I tried sending a command from the app, and that didn’t work. Physical presses also didn’t register in the app.
The device name is “Finger Urn”
2024-03-03T02:17:13.814988323+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2024-03-03T02:17:43.850664792+00:00 INFO Zigbee Switch Mc Doing health check read for [A04D]:0006:0000
2024-03-03T02:17:43.853377507+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 9f34167c-4b3c-490e-8059-ab9d5a1a6b4f [0xA04D] (Finger Urn)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xA04D, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2024-03-03T02:17:43.856836037+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2024-03-03T02:18:13.847126728+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2024-03-03T02:18:38.578624338+00:00 TRACE Zigbee Switch Mc Received event with handler capability
2024-03-03T02:18:38.586712838+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 9f34167c-4b3c-490e-8059-ab9d5a1a6b4f [0xA04D] (Finger Urn)> received command: {"args":{},"capability":"switch","command":"off","component":"main","positional_args":{}}
2024-03-03T02:18:38.588326196+00:00 TRACE Zigbee Switch Mc Found CapabilityCommandDispatcher handler in Zigbee_Switch_Mc
2024-03-03T02:18:38.595025401+00:00 DEBUG Zigbee Switch Mc Finger Urn device thread event handled
2024-03-03T02:18:43.840678769+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2024-03-03T02:19:13.846957018+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2024-03-03T02:19:43.824709078+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2024-03-03T02:20:13.835383151+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2024-03-03T02:20:29.814292408+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2024-03-03T02:20:29.817535874+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 74db3cf3-8965-4427-a4d3-251013ad6f3d [0xF527] (Logans Bed Shaker)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF527, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x98, rssi: -62, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x59, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2024-03-03T02:20:29.833438144+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc
2024-03-03T02:20:29.834107479+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2024-03-03T02:20:29.835400545+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 74db3cf3-8965-4427-a4d3-251013ad6f3d [0xF527] (Logans Bed Shaker)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"<em table style='font-size:70%';'font-weight: bold'</em><b>GMT: </b>2024/03/03 Time: 02:20<BR><b>DNI: </b>0xF527 <b> LQI: </b>152 <b>RSSI: </b>-62dbm</em><BR>"},"visibility":{"displayed":false}}
2024-03-03T02:20:29.844902674+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 74db3cf3-8965-4427-a4d3-251013ad6f3d [0xF527] (Logans Bed Shaker)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2024-03-03T02:20:29.861771717+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 74db3cf3-8965-4427-a4d3-251013ad6f3d [0xF527] (Logans Bed Shaker)> emitting event: {"attribute_id":"power","capability_id":"powerMeter","component_id":"main","state":{"unit":"W","value":0}}
2024-03-03T02:20:29.871096991+00:00 DEBUG Zigbee Switch Mc Logans Bed Shaker device thread event handled
2024-03-03T02:20:43.844685794+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2024-03-03T02:21:13.860457196+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2024-03-03T02:21:43.871068556+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2024-03-03T02:21:50.311793500+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2024-03-03T02:21:50.315975927+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 4f9ddbc5-8923-4a9d-a5f9-33384e3c10e4 [0x5AAD] (Front Lock Hub)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5AAD, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0xFF, profile: 0x0104, cluster: OnOff >, lqi: 0x6C, rssi: -73, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x7B, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2024-03-03T02:21:50.336422563+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch_Mc
2024-03-03T02:21:50.337327315+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2024-03-03T02:21:50.339260154+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 4f9ddbc5-8923-4a9d-a5f9-33384e3c10e4 [0x5AAD] (Front Lock Hub)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"<em table style='font-size:70%';'font-weight: bold'</em><b>GMT: </b>2024/03/03 Time: 02:21<BR><b>DNI: </b>0x5AAD <b> LQI: </b>108 <b>RSSI: </b>-73dbm</em><BR>"},"visibility":{"displayed":true}}
2024-03-03T02:21:50.348123947+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 4f9ddbc5-8923-4a9d-a5f9-33384e3c10e4 [0x5AAD] (Front Lock Hub)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2024-03-03T02:21:50.366802057+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 4f9ddbc5-8923-4a9d-a5f9-33384e3c10e4 [0x5AAD] (Front Lock Hub)> emitting event: {"attribute_id":"power","capability_id":"powerMeter","component_id":"main","state":{"unit":"W","value":0}}
2024-03-03T02:21:50.372815969+00:00 DEBUG Zigbee Switch Mc Front Lock Hub device thread event handled
2024-03-03T02:22:13.838415321+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2024-03-03T02:22:43.841249191+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2024-03-03T02:23:13.855527879+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
Thanks!
Hello I have installed device fingerbot and choose pilote zigbee switch mc but it seems not to work correctly. the command values not seems to be set. i tried to unplug plug the battery to reset values but it doesn’t work
perhaps a conflict with another driver?
could you help me thanks?
I confirm it was a conflict with another driver channel.
after desinstall it and reinstall it it works
1 Like
Your device does not send or the hub does not receive the periodic reports and the Health Check is being activated.
The Health Check questions the device, but it does not respond and that is why it ends up going offline
When you activate it manually, the message is received in the Hub but with poor signal quality LQI: 0x98 (152) (maximum value 255)
It may also be that the device was not configured correctly during installation.
You can try uninstalling it and pairing it near Hub so that it configures correctly
You may need a repeater installed between the Hub and the device or you may have some wifi signal interference with the device it is physically placed on, since the signal strength is not bad rssi=-62
@Mariano_Colmenarejo,
Thank you for the response. I have repeaters throughout the house, including 2 feet away. Those metrics were lqi 188, rssi - 53.
I think the metrics you got from the logs were for a different device. This one is called “Finger Urn”.
Because of the nature of the device, I can’t really move it back to the hub. It is stuck to a hot and heavy urn. I did delete the device and readded it. It worked fine for over 4 hours. However, I did notice that it did stop sending signals exactly 30 minutes after the device was turned off. That seemed weird to me. Any ideas with regard to this? The metrics at the time were lqi 164 and rssi - 59. I thought those values weren’t bad, no?
You are right, those metrics are from the attribute report of another device.
When the off command is received in the driver, the default switch_handler must send the command to the device, although it is not seen in the logs and the device, just like when reading the attribute, does not respond at all.
I don’t know why it doesn’t respond, if the network is fine, as you say, then it may be defective
Since the person asking the question said they have a “Wi-Fi hub“ if they mean one of the hubs which is also a Wi-Fi mesh router, those are stuck back around version 47 of the firmware, so may not have the same edge driver support that the V2, V3, and Aeotec hubs have, all of which are above version 50 at this point.
There have been multiple reports in the forum that the Wi-Fi mesh router hubs have some compatibility issues that the other hubs do not. And There have definitely been changes in how health check works for Zigbee devices in the recent firmware updates. 
I think that in this case the type of hub is not important, device and driver use default cluster onOff libraries, which have not changed for several firmware versions.
I also understood that it works for a while and then stops responding, then either the network is not correct where this device is or the device stops receiving and transmitting messages to the network.
2 Likes