[Beta] Zigbee Edge Driver compatible with Lidl, Ecosmart, Osram, SmartThings & Others

Can you update to when status change to dry or wet ?
Easier to test…If possible

Making it update with wet or dry messages implies that need to duplicate the code of the default handlers, which are already written in the Hub’s firmware, and write them again in the driver.

This metrics functionality in the IDE was updated in zwave once a day and in zigbee once or twice a day, depending on the hub firmware, which is updated with the battery reports 4 times a day, I think that is enough.
It also tries to read the battery when a refresh is done in the app, if the device responds the metrics will also be updated.
As the capability events have GMT date and time you can see how often it is updated.

On the other hand, to save a driver I have merged the Zigbee Aqara Water Leak Sensor Mc driver with the Zigbee Moisture Sensor Mc

───────────────────────────────────────────────────
 Name         Zigbee Moisture Sensor Mc
 Version      2022-11-25T16:47:15.69183962
───────────────────────────────────────────────────
  - id: "Lumi/SJCG11LM"
    deviceLabel: Aqara Water Leak Sensor
    manufacturer: LUMI
    model: lumi.sensor_wleak.aq1
    deviceProfileName: moisture-battery

Thank you very much @Mariano_Colmenarejo I was testing the driver, but this not show CO2 information. I have added screenshot.

Hola Victor

Sorry, I swapped the manufacturer and model in subdriver can_handle :man_facepalming:
Fixed in this driver version, but is a CO detector not CO2 detector

───────────────────────────────────────────────────
 Name         Zigbee Smoke/CO Detector Mc
 Version      2022-11-25T20:16:23.321979139        
───────────────────────────────────────────────────

Hey.
About a month and a half ago you added support for the circuit breaker I requested. Everything was working great until about a month ago.
What happens is that after I add the device it works for 10 minutes and then does not update and does not respond to any command.
Attach a photo of a fingerprint.
I would appreciate your help, because my whole house is based on these circuit breakers.
Thank you.


Hi @raz6498635

You may be experiencing the firmware 45.11 issue that some users are experiencing with zigbee device disconnections.

Try rebooting the hub when it happens to see if that fixes it.

try to change zigbee channel in IDE.

These are some of the things I’ve read on the forum

Thank you very much @Mariano_Colmenarejo this new driver is working fine with the HEIMAN CO Sensor -EF-3.0. :grinning: :+1:

1 Like

Thanks,
This is working and displaying the RSSI. These sensors are in usually in hidden places like under the washing machine. Knowing the signal reception level is very helpful.
:+1: :pray:

1 Like

Hey,
I changed the channel several times and rebooted several times without success.
I don’t think that’s the problem.
Because when I send a command using the app it doesn’t respond at all and displays a message “Network error try again later” but when I physically press the circuit breaker it refreshes and changes the status immediately in the app as well.
But does not respond at all to any command from the application.
Thank you very much for your help

To focus the problem.
In the App It doesn’t work when you execute the command from the child device or from the triple parent device or from any of them?

If you send me the logs of when you press on or off in the app with the error, I can analyze it and see if it has to do with the driver or if the command does not reach the driver or device from the App

It only works for about 5 minutes after I pair it with the device and immediately stops after that.
I would love to receive a guide on how to extract a log from CLI to send to you.

What drivers are you using?

This is a guide to install CLI and see logs

@Mariano_Colmenarejo
iam use Zigbee Multi Switch and Child Mc
here waht i get on cli

? Select a driver. 24
2022-11-26T14:43:38.482537804+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-11-26T14:43:38.523811137+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x86F6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -57, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xF2, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-11-26T14:43:38.615043804+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:43:38.621382804+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-11-26T14:43:38.633859471+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-11-26T14:43:38.698765471+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2022/11/26 Time: 14:43
DNI: 0x86F6 LQI: 136 RSSI: -57dbm
”},“visibility”:{“displayed”:false}}
2022-11-26T14:43:38.738145471+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 2 value = false
2022-11-26T14:43:38.753978471+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-11-26T14:43:38.796154471+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:43:38.804245471+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:43:40.791242805+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-11-26T14:43:40.904934138+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-11-26T14:43:41.055439805+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:43:54.731693145+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T14:43:54.741170145+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“main”,“positional_args”:{}}
2022-11-26T14:43:54.747586478+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:43:54.819034145+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:44:25.711015160+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T14:44:25.748542826+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“switch2”,“positional_args”:{}}
2022-11-26T14:44:25.785330160+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:44:25.890969826+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:44:50.074652838+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T14:44:50.083764838+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“switch3”,“positional_args”:{}}
2022-11-26T14:44:50.089789838+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:44:50.102482171+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:45:28.371706190+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T14:45:28.385270856+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{“value”:“All On”},“capability”:“legendabsolute60149.switchAllOnOff1”,“command”:“setSwitchAllOnOff”,“component”:“main”,“positional_args”:[“All On”]}
2022-11-26T14:45:28.397313523+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:45:28.403785523+00:00 PRINT Zigbee Multi Switch and Child Mc command >>>>> table: 0x1d8e828
2022-11-26T14:45:28.408927856+00:00 PRINT Zigbee Multi Switch and Child Mc command.args.value >>>>> All On
2022-11-26T14:45:28.415060523+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-11-26T14:45:28.435854523+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x86F6, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-11-26T14:45:28.451117856+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x86F6, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-11-26T14:45:28.513459523+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x86F6, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-11-26T14:45:28.533181523+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:45:42.188426863+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T14:45:42.197080530+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“switch2”,“positional_args”:{}}
2022-11-26T14:45:42.203057530+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:45:42.225847530+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:45:42.641775863+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-11-26T14:45:42.667165196+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x86F6, src_endpoint: 0x03, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x8E, rssi: -60, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xF3, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-11-26T14:45:42.742034196+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:45:42.760307196+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-11-26T14:45:42.770775530+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-11-26T14:45:42.778561196+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2022/11/26 Time: 14:45
DNI: 0x86F6 LQI: 142 RSSI: -60dbm
”},“visibility”:{“displayed”:false}}
2022-11-26T14:45:42.804447196+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 3 value = false
2022-11-26T14:45:42.816128530+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch3”,“state”:{“value”:“off”}}
2022-11-26T14:45:42.843961863+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:45:42.854701863+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:45:43.170147863+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-11-26T14:45:43.208215863+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x86F6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x8A, rssi: -56, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xF4, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-11-26T14:45:43.243353530+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:45:43.259293530+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-11-26T14:45:43.286426197+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-11-26T14:45:43.320541530+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2022/11/26 Time: 14:45
DNI: 0x86F6 LQI: 138 RSSI: -56dbm
”},“visibility”:{“displayed”:false}}
2022-11-26T14:45:43.375053197+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 1 value = false
2022-11-26T14:45:43.413259197+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-11-26T14:45:43.488214197+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:45:43.501202530+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:45:44.848719864+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-11-26T14:45:44.855359864+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-11-26T14:45:44.872729197+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:45:45.606815198+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-11-26T14:45:45.695526865+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-11-26T14:45:45.781193198+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:45:51.211720200+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T14:45:51.248531200+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“switch3”,“positional_args”:{}}
2022-11-26T14:45:51.261176867+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:45:51.340714201+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:45:52.530676868+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T14:45:52.547747868+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“main”,“positional_args”:{}}
2022-11-26T14:45:52.553622201+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:45:52.603671868+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:46:39.673074647+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-11-26T14:46:39.697215981+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x86F6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x8A, rssi: -61, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xF5, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-11-26T14:46:39.719715314+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:46:39.738638314+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-11-26T14:46:39.745652314+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-11-26T14:46:39.753405314+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2022/11/26 Time: 14:46
DNI: 0x86F6 LQI: 138 RSSI: -61dbm
”},“visibility”:{“displayed”:false}}
2022-11-26T14:46:39.805913647+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 1 value = true
2022-11-26T14:46:39.824705314+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-11-26T14:46:39.891093981+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:46:39.916792981+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:46:39.939201314+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-11-26T14:46:39.957053647+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x86F6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -61, body_length: 0x0003, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x11, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-11-26T14:46:40.055918647+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:46:40.065444314+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-11-26T14:46:40.081804647+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x86F6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x82, rssi: -54, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xF6, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-11-26T14:46:40.102163314+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:46:40.107567981+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-11-26T14:46:40.120442981+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-11-26T14:46:40.139578648+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2022/11/26 Time: 14:46
DNI: 0x86F6 LQI: 130 RSSI: -54dbm
”},“visibility”:{“displayed”:false}}
2022-11-26T14:46:40.164698648+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 2 value = true
2022-11-26T14:46:40.191477314+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-11-26T14:46:40.259298314+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:46:40.284069648+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-11-26T14:46:40.325511314+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x86F6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x8C, rssi: -61, body_length: 0x0003, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x11, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-11-26T14:46:40.468659648+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:46:40.505695648+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:46:41.878984982+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-11-26T14:46:41.885553982+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:"S1:On S2:On "}}
2022-11-26T14:46:41.934061982+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:46:42.256970315+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-11-26T14:46:42.263545315+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:"S1:On S2:On "}}
2022-11-26T14:46:42.278796982+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:46:56.911711322+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T14:46:56.920222989+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“off”,“component”:“switch2”,“positional_args”:{}}
2022-11-26T14:46:56.931229656+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:46:56.956606322+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:46:57.603807989+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T14:46:57.614020656+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“off”,“component”:“main”,“positional_args”:{}}
2022-11-26T14:46:57.630808323+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:46:57.665138656+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T14:46:59.460454657+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T14:46:59.469839323+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“switch3”,“positional_args”:{}}
2022-11-26T14:46:59.493809657+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T14:46:59.524335990+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled

@raz6498635

Please, could You remove the </> format to logs.
For me is better see logs as CLI format

Sure edit now.
Thank you

1 Like

I don’t know exactly what physical maneuvers in the app or device these logs correspond to.

I see on or off commands from the app being sent to the device and no response from the device.

I see responses from the device, which since they are not preceded by sending a command, I suppose they are on or off performed on the physical device.

Could you please capture logs by pressing on and after a few seconds press off in main switch in the app?

Could you capture a different Log with all the switches being off in the app and clicking on App All On switch?

first log u ask:

? Select a driver. 24
connecting… connected
2022-11-26T16:18:20.533710621+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T16:18:20.542635288+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“main”,“positional_args”:{}}
2022-11-26T16:18:20.549065954+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T16:18:20.577044621+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-11-26T16:18:48.520943674+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T16:18:48.620240964+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“main”,“positional_args”:{}}
2022-11-26T16:18:48.635863772+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T16:18:48.722751861+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled

second log:

? Select a driver. 24
connecting… connected
2022-11-26T16:29:08.175576254+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-11-26T16:29:08.185350921+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> received command: {“args”:{“value”:“All On”},“capability”:“legendabsolute60149.switchAllOnOff1”,“command”:“setSwitchAllOnOff”,“component”:“main”,“positional_args”:[“All On”]}
2022-11-26T16:29:08.191299588+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-11-26T16:29:08.196424921+00:00 PRINT Zigbee Multi Switch and Child Mc command >>>>> table: 0x1ced8a8
2022-11-26T16:29:08.201613254+00:00 PRINT Zigbee Multi Switch and Child Mc command.args.value >>>>> All On
2022-11-26T16:29:08.207713921+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-11-26T16:29:08.228102588+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x86F6, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-11-26T16:29:08.251440921+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x86F6, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-11-26T16:29:08.275286588+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: de833a20-ca47-4052-871f-f64fb4c6d5a5 [0x86F6] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x86F6, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-11-26T16:29:08.315783254+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled

If the device has not been turned on or off with these commands, These logs confirm what I told you before.

On and Off commands are sent to the device but the device does not respond:

  • Possibly The command does not arrive with enough quality and power for the device can process it.

  • The messages sent from the device to inform the physical changes, Yes they arrive at the Hub or the Hub has more sensitivity in its radio reception hardware.

  • The device is not marked as offline because every 5 minutes the device will send a status report, which is received by the Hub and therefore considered Online.

Try putting repeaters between the hub and device
Test with the device outside of its electrical box on the wall.
Try changing the wifi channel on your router in case it interferes or temporarily disable it to test

None of these devices work for you or only some?

none off them work…
also try to chnge channel on st hub
And the strange part is that until a month ago everything was working perfectly without any problems.
What’s even weirder is that when I physically turn on the switch, the app is immediately updated.
In addition, I tried to connect to TUYA HUB and it works perfectly.
Frustrated

I understand!!

Now that you have the CLI working try doing this:

  • I have compiled and published a new version, it has no changes, but you are going to install it with the CLI so that all the devices are reconfigured.
  • Prepare a window with the CLI to capture the driver installation log
  • Open another window with the CLI to install the new version
  • In this window, Type smartthings edge:drivers:install and press enter
  • Follow the steps to choose the number corresponding to the Hub, then to the channel where the driver is installed and finally the driver you want to install.
  • Open the log window and after about 10 seconds or more you will see the installation and configuration process of all the devices with the driver.
  • Capture the log of at least 30 sec and send it to me in case I can see any errors
  • I don’t know if this will make them work again or not.
───────────────────────────────────────────────────
 Name         Zigbee Multi Switch and Child Mc
 Version      2022-11-26T16:55:20.155189529
───────────────────────────────────────────────────