(EDGE Driver-Mc): Zigbee Drivers for Motion, Open/Close, Moisture, Smoke-Co Sensors and others Devices

@Sylvain @Mariano_Colmenarejo @nayelyz Interesting is that my screenshot shows older date but when I switched to OLD and switched back to exactly same driver it shows new date.
Same driver.


@Sylvain, @Ashley69,

Let’s see I just arrived to home and I’m going step by step.

Something must not have worked in the published new version yesterday. I also had the same version as you. Something strange happened or something I did wrong, of course.

I have just made a new version with the space corrections in the Chinese characters and it seems that it has installed me hub correct versionl.

This is the one I just posted.

β”‚ Name β”‚ Zigbee Switch Mc β”‚
β”‚ Version β”‚ 2021-11-16T17:28:54.464928

1 Like

@milandjurovic71

Yes it’s strange

This is the last version date

2021-11-16T11:30:01.098338

I just realized that as soon as I just swapped driver on one device, it did made date update on all devices with the same driver.

Yes, if all devices are in the same driver, the same date must appear in all devices

@GiacomoF,
Yes, I changed in this driver, but in my github is not updated yet.
Updated github

1 Like

It took about 5 min to update in my hub , reboot hub and the switch work . Thank you

1 Like

I have all my plugs and switches offline. Rebooted hub few minutes ago. Let’s see if they start coming back online.

@Sakari
Working after reboot?

No. I rebooted twice ans deleted cache. Easier to pair them again.

Edit: One switch started to work after deleted one plug and pair it again. But all other plugs still not working.

How odd!

Yesterday there was a firmware update of the hub to 40.06. I don’t know if the problem would coincide with that update and something was wrong.

As soon as I can, I publish the zigbee switch Mc- (OLD) version again in the channel, you install it in the hub.
Change your plugs to that version with a driver change, so you don’t lose anything.

Delete the original version from the hub, do a reboot and reinstall it.
Then change the plugs again to see if they already work

UPDATE: It is published in case you want to try

Thanks. I’ll try it shortly.

Edit: Nope, couldn’t make this work. All plugs are offline so therr is no way I can change drivers. I just need to delete and pair them again. Thanks for the help.

Around 1 AM EST the 5 devices controlled by β€œZigBee Switch MC” went offline. One device controlled an alarm, and it made a couple chirping sounds.
After a hub reboot 4 of the 5 devices came back online.
The 5th device a Tuya relay did not come back online. It is buried in a multi gang switch box. I tried to force into pairing mode by deleting it but that didn’t work. So when I get time I will need to physically access it to put it into pairing mode.

All my plugs work fine

I have 6 switches and plugs connected to the driver and they all work fine.

Will it have something to do with the hub firmware update?

OK Mariano…so here are my latest findings…

Everything now working since latest hub firmware except:

1 2015 ST motion sensor pairs with zigbee motion sensor driver but reports no battery
2 2015 ST smart plug reverts to stock DTH upon pairing…wont pair with drive
3 Ecolink contacty sensor reports contact and temp…will not report battery

The battery reports have a very long default reporting interval, 21600 seconds (6 hours).

If you want to speed it up, you can try to remove the battery, leave it removed for a few minutes so that the lack of charge causes the voltage to rise a bit and reinstall it.

Regarding the smartthings plug, do you mean this one?

  - id: "SmartTings/outletv4"
    deviceLabel: SmartTings outletv4
    manufacturer: SmartTings
    model: outletv4
    deviceProfileName: switch-power-plug

Update on devices going off line with"ZigBee Switch MC":

11-16-2021, 12:21 PM EST - firmware updates to 40.00006
11-17-2021, 12:52 AM EST - some sort of hub update
11-17-2021, 01:11 AM EST - Alarm briefly sounds and 5 devices go offline. The LEDs on 3 devices that were visible were flashing like they were in pairing mode.

4 of 5 devices go back on line after hub reboot. Tuya relay remainder offline.

The 5th device (Tuya relay) has since been successfully repaired with ZigBee Switch MC

1 Like

Hi Mariano,

could you please add the Aqara contact sensor back to the driver? Or was it not working?

I tried to add the sensor with ST driver which it did not work with, but attaching logs here if it helps.

β”Œβ”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ # β”‚ Driver Id β”‚ Name β”‚
β”œβ”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ 1 β”‚ 0fd9a9a4-8863-4a83-97a7-5a288ff0f5a6 β”‚ Virtual Devices V2 β”‚
β”‚ 2 β”‚ c42a476b-bcc0-4d40-8c6e-21a85bb52a80 β”‚ Xiaomi Sensors β”‚
β”‚ 3 β”‚ e165119d-d6ee-4bac-80e8-7412bb72df80 β”‚ Zigbee Contact β”‚
β”‚ 4 β”‚ d620900d-f7bc-4ab5-a171-6dd159872f7d β”‚ Zigbee Motion Sensor β”‚
β”‚ 5 β”‚ 92f39ab3-7b2f-47ee-94a7-ba47c4ee8a47 β”‚ Zigbee Power/Meter β”‚
β”‚ 6 β”‚ b36f1d7a-1144-4a1d-bf8b-f7d69dee8909 β”‚ Zigbee Switch Mc β”‚
β”‚ 7 β”‚ 7fcf0d61-252d-4152-b001-a9901011acf5 β”‚ Zigbee Temp Humidity Sensor Mc β”‚
β”‚ 8 β”‚ f82dec82-e5fa-487f-8f0f-22c3e4a8bd89 β”‚ Zigbee Water Leak Sensor β”‚
β””β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
? Select a driver. 3
2021-11-17T15:19:15.315425049+00:00 TRACE Zigbee Contact Received event with handler zigbee health poll
2021-11-17T15:19:45.312843313+00:00 TRACE Zigbee Contact Received event with handler zigbee health poll
2021-11-17T15:20:15.315595994+00:00 TRACE Zigbee Contact Received event with handler zigbee health poll
2021-11-17T15:20:45.336852675+00:00 TRACE Zigbee Contact Received event with handler zigbee health poll
2021-11-17T15:21:15.329984648+00:00 TRACE Zigbee Contact Received event with handler zigbee health poll
2021-11-17T15:21:45.328507262+00:00 TRACE Zigbee Contact Received event with handler zigbee health poll
2021-11-17T15:22:15.324507151+00:00 TRACE Zigbee Contact Received event with handler zigbee health poll
2021-11-17T15:22:17.529440110+00:00 TRACE Zigbee Contact Received event with handler device_lifecycle
2021-11-17T15:22:17.539121360+00:00 WARN Zigbee Contact Device does not support cluster 0x0001 not adding configured attribute
2021-11-17T15:22:17.542679527+00:00 WARN Zigbee Contact Device does not support cluster 0x0001 not adding monitored attribute
2021-11-17T15:22:17.547189652+00:00 WARN Zigbee Contact Device does not support cluster 0x0500 not adding configured attribute
2021-11-17T15:22:17.550549777+00:00 WARN Zigbee Contact Device does not support cluster 0x0500 not adding monitored attribute
2021-11-17T15:22:17.553824777+00:00 INFO Zigbee Contact <ZigbeeDevice: 2a4d8042-7e0f-4147-acf0-676010229d90 [0xC103] (Aqara Open/Closed Sensor)> received lifecycle event: added
2021-11-17T15:22:17.561629319+00:00 TRACE Zigbee Contact Received event with handler device_lifecycle
2021-11-17T15:22:17.565014194+00:00 INFO Zigbee Contact <ZigbeeDevice: 2a4d8042-7e0f-4147-acf0-676010229d90 [0xC103] (Aqara Open/Closed Sensor)> received lifecycle event: doConfigure
2021-11-17T15:22:17.570656735+00:00 TRACE Zigbee Contact <ZigbeeDevice: 2a4d8042-7e0f-4147-acf0-676010229d90 [0xC103] (Aqara Open/Closed Sensor)> received unhandled lifecycle event: added
2021-11-17T15:22:17.573642860+00:00 DEBUG Zigbee Contact Aqara Open/Closed Sensor device thread event handled
2021-11-17T15:22:17.578979152+00:00 TRACE Zigbee Contact <ZigbeeDevice: 2a4d8042-7e0f-4147-acf0-676010229d90 [0xC103] (Aqara Open/Closed Sensor)> received unhandled lifecycle event: init
2021-11-17T15:22:17.581910694+00:00 DEBUG Zigbee Contact Aqara Open/Closed Sensor device thread event handled
2021-11-17T15:22:17.592872194+00:00 TRACE Zigbee Contact Found DeviceLifecycleDispatcher handler in zigbee_contact
2021-11-17T15:22:17.597472110+00:00 TRACE Zigbee Contact Found CapabilityCommandDispatcher handler in zigbee_contact
2021-11-17T15:22:17.601198902+00:00 DEBUG Zigbee Contact Aqara Open/Closed Sensor device thread event handled
2021-11-17T15:22:17.615963444+00:00 DEBUG Zigbee Contact Aqara Open/Closed Sensor device thread event handled
2021-11-17T15:22:17.776325444+00:00 TRACE Zigbee Contact Received event with handler device_lifecycle
2021-11-17T15:22:17.783306235+00:00 INFO Zigbee Contact <ZigbeeDevice: 2a4d8042-7e0f-4147-acf0-676010229d90 [0xC103] (Aqara Open/Closed Sensor)> received lifecycle event: infoChanged
2021-11-17T15:22:17.788840319+00:00 TRACE Zigbee Contact <ZigbeeDevice: 2a4d8042-7e0f-4147-acf0-676010229d90 [0xC103] (Aqara Open/Closed Sensor)> received unhandled lifecycle event: infoChanged
2021-11-17T15:22:17.791722069+00:00 DEBUG Zigbee Contact Aqara Open/Closed Sensor device thread event handled
2021-11-17T15:22:20.079499153+00:00 TRACE Zigbee Contact Received event with handler zigbee
2021-11-17T15:22:20.085752153+00:00 INFO Zigbee Contact <ZigbeeDevice: 2a4d8042-7e0f-4147-acf0-676010229d90 [0xC103] (Aqara Open/Closed Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC103, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8033 >, lqi: 0xFF, rssi: -59, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x13 >, < MgmtBindResponse || Status: 0x84 > > >
2021-11-17T15:22:20.095447445+00:00 DEBUG Zigbee Contact Aqara Open/Closed Sensor device thread event handled
2021-11-17T15:22:45.330859874+00:00 TRACE Zigbee Contact Received event with handler zigbee health poll
2021-11-17T15:22:55.702743087+00:00 TRACE Zigbee Contact Received event with handler zigbee
2021-11-17T15:22:55.746883628+00:00 INFO Zigbee Contact <ZigbeeDevice: 2a4d8042-7e0f-4147-acf0-676010229d90 [0xC103] (Aqara Open/Closed Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC103, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xFF, rssi: -59, body_length: 0x0040, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x1C, mfg_code: 0x115F, seqno: 0x00, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0005, DataType: CharString, ModelIdentifier: β€œlumi.sensor_magnet.aq2” >, < AttributeRecord || AttributeId: 0xFF01, DataType: CharString, CharString: β€œ\x01\x21\xC7\x0B\x03\x28\x1B\x04\x21\xA8\x01\x05\x21\x45\x06\x06\x24\x00\x00\x00\x00\x00\x0A\x21\xC4\x4A\x64\x10\x01” > > > >
2021-11-17T15:22:55.764173087+00:00 DEBUG Zigbee Contact Aqara Open/Closed Sensor device thread event handled
2021-11-17T15:23:11.545043011+00:00 TRACE Zigbee Contact Received event with handler zigbee
2021-11-17T15:23:11.550871053+00:00 INFO Zigbee Contact <ZigbeeDevice: 2a4d8042-7e0f-4147-acf0-676010229d90 [0xC103] (Aqara Open/Closed Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC103, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -60, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x01, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2021-11-17T15:23:11.560157053+00:00 DEBUG Zigbee Contact Aqara Open/Closed Sensor device thread event handled
2021-11-17T15:23:11.949565761+00:00 TRACE Zigbee Contact Received event with handler zigbee
2021-11-17T15:23:11.953740303+00:00 WARN Zigbee Contact Zigbee string reported length 9 but was actually only 8 bytes long
2021-11-17T15:23:11.957924386+00:00 INFO Zigbee Contact <ZigbeeDevice: 2a4d8042-7e0f-4147-acf0-676010229d90 [0xC103] (Aqara Open/Closed Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC103, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xFF, rssi: -60, body_length: 0x0011, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x1C, mfg_code: 0x115F, seqno: 0x02, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xFF01, DataType: CharString, CharString: β€œ\x04\x21\xA8\x01\x0A\x21\xC4\x4A” > > > >
2021-11-17T15:23:11.966831220+00:00 DEBUG Zigbee Contact Aqara Open/Closed Sensor device thread event handled
2021-11-17T15:23:14.699095221+00:00 TRACE Zigbee Contact Received event with handler zigbee
2021-11-17T15:23:14.703823471+00:00 INFO Zigbee Contact <ZigbeeDevice: 2a4d8042-7e0f-4147-acf0-676010229d90 [0xC103] (Aqara Open/Closed Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xC103, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -60, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x03, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2021-11-17T15:23:14.713954721+00:00 DEBUG Zigbee Contact Aqara Open/Closed Sensor device thread event handled
2021-11-17T15:23:15.328575554+00:00 TRACE Zigbee Contact Received event with handler zigbee health poll
listening for logs… done

Yes that’s the one. I believe I may see the issue…
If that example is straight from your code "SmartThings’ is misspelled. The β€œh” is missing from the name.

1 Like