@Paul_Oliver, @Bralok
Did you try this latest version?
It has some changes in the on-off handler
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Switch Mc │
│ Version │ 2022-01-16T15:36:20.510651 │
└─────────────┴──────────────────────────────────────┘
No. I did not know there was a new version, so I am still running the old version.
I will give it a try later this evening.
I have tried the 2022-01-16 version of your Zigbee Switch Mc an d I am still having problems:
The relay generally works fine in automations. But many times the device tile in the Android APP (1.7.77.22) and the web application will show that the relay is on when it is actually off.
I will operate the light and the app will reflect the actual state of the relay, but after I turn it off a few minutes later the app will say the light is on when it is actually off.
The following are the logs of a couple operations of the relay. At the very end is when the app says the relay is on when is is actually off. I use that drive for about 8 devices so they could be some other things mixed in. “Workbench Light” is the Sonoff ZBMINI.
2022-01-17T01:45:06.192615648+00:00 TRACE Zigbee Switch Mc Received event with handler capability
2022-01-17T01:45:06.237937856+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> received command: {“args”:,“capability”:“switch”,“positional_args”:,“component”:“main”,“command”:“on”}
2022-01-17T01:45:06.241272481+00:00 TRACE Zigbee Switch Mc Found CapabilityCommandDispatcher handler in Zigbee_Switch
2022-01-17T01:45:06.248567606+00:00 DEBUG Zigbee Switch Mc Workbench Light device thread event handled
2022-01-17T01:45:06.339103106+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-01-17T01:45:06.348333273+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAAED, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -59, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x7A, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-01-17T01:45:06.370453023+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-01-17T01:45:06.373579940+00:00 INFO Zigbee Switch Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-01-17T01:45:06.377749315+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“state”:{“value”:“on”},“component_id”:“main”}
2022-01-17T01:45:06.389770731+00:00 DEBUG Zigbee Switch Mc Workbench Light device thread event handled
2022-01-17T01:45:06.392945940+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-01-17T01:45:06.397817065+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAAED, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -59, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x7D, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-01-17T01:45:06.419232606+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-01-17T01:45:06.422098773+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-17T01:45:06.425979523+00:00 PRINT Zigbee Switch Mc value.value >>>>>>>>>>> true
2022-01-17T01:45:06.429228731+00:00 PRINT Zigbee Switch Mc <<<<<<< Power meter Timer >>>>> ON
2022-01-17T01:45:06.432993398+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“state”:{“value”:“on”},“component_id”:“main”}
2022-01-17T01:45:06.442774190+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> emitting event: {“attribute_id”:“power”,“capability_id”:“powerMeter”,“state”:{“unit”:“W”,“value”:80},“component_id”:“main”}
2022-01-17T01:45:06.462619606+00:00 DEBUG Zigbee Switch Mc Workbench Light device thread event handled
2022-01-17T01:45:06.487436981+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-01-17T01:45:06.492526981+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAAED, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -59, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x7C, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Int8, OnOff: true > > > >
2022-01-17T01:45:06.514423523+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-01-17T01:45:06.518500065+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-17T01:45:06.521819731+00:00 PRINT Zigbee Switch Mc value.value >>>>>>>>>>> 1
2022-01-17T01:45:06.525032815+00:00 PRINT Zigbee Switch Mc <<<<<<< Power meter Timer >>>>> ON
2022-01-17T01:45:06.529248940+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“state”:{“value”:“on”},“component_id”:“main”}
2022-01-17T01:45:06.538466023+00:00 DEBUG Zigbee Switch Mc Workbench Light device thread event handled
2022-01-17T01:45:14.757004774+00:00 TRACE Zigbee Switch Mc Received event with handler capability
2022-01-17T01:45:14.802954232+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> received command: {“args”:,“capability”:“switch”,“positional_args”:,“component”:“main”,“command”:“off”}
2022-01-17T01:45:14.806578732+00:00 TRACE Zigbee Switch Mc Found CapabilityCommandDispatcher handler in Zigbee_Switch
2022-01-17T01:45:14.832063482+00:00 DEBUG Zigbee Switch Mc Workbench Light device thread event handled
2022-01-17T01:45:14.887913191+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-01-17T01:45:14.892823149+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAAED, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -57, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x7E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Int8, OnOff: true > > > >
2022-01-17T01:45:14.925324816+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-01-17T01:45:14.928615191+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-17T01:45:14.938475232+00:00 PRINT Zigbee Switch Mc value.value >>>>>>>>>>> 0
2022-01-17T01:45:14.942083691+00:00 PRINT Zigbee Switch Mc <<<<<<< Power meter Timer >>>>> ON
2022-01-17T01:45:14.946189149+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“state”:{“value”:“on”},“component_id”:“main”}
2022-01-17T01:45:14.957853274+00:00 DEBUG Zigbee Switch Mc Workbench Light device thread event handled
2022-01-17T01:45:14.962388274+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-01-17T01:45:14.966977774+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAAED, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -57, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x7B, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
2022-01-17T01:45:14.989822774+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-01-17T01:45:14.992678316+00:00 INFO Zigbee Switch Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-01-17T01:45:14.997080982+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“state”:{“value”:“off”},“component_id”:“main”}
2022-01-17T01:45:15.007728024+00:00 DEBUG Zigbee Switch Mc Workbench Light device thread event handled
2022-01-17T01:45:15.011589941+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-01-17T01:45:15.016380941+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAAED, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -57, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x7F, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-01-17T01:45:15.041336649+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-01-17T01:45:15.044371357+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-17T01:45:15.047893566+00:00 PRINT Zigbee Switch Mc value.value >>>>>>>>>>> false
2022-01-17T01:45:15.051005566+00:00 PRINT Zigbee Switch Mc <<<<<<< Power meter Timer >>>>> ON
2022-01-17T01:45:15.054781482+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“state”:{“value”:“off”},“component_id”:“main”}
2022-01-17T01:45:15.064812941+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> emitting event: {“attribute_id”:“power”,“capability_id”:“powerMeter”,“state”:{“unit”:“W”,“value”:0},“component_id”:“main”}
2022-01-17T01:45:15.076316774+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> emitting event: {“attribute_id”:“energy”,“capability_id”:“energyMeter”,“state”:{“unit”:“kWh”,“value”:0.023866666666667},“component_id”:“main”}
2022-01-17T01:45:15.089981233+00:00 DEBUG Zigbee Switch Mc Workbench Light device thread event handled
2022-01-17T01:45:23.980345859+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee health poll
2022-01-17T01:45:53.984831654+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee health poll
2022-01-17T01:46:23.895881449+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-01-17T01:46:23.901643949+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAAED, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -56, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x00, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Int8, OnOff: true > > > >
2022-01-17T01:46:23.944565491+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-01-17T01:46:23.949077241+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-17T01:46:23.955521032+00:00 PRINT Zigbee Switch Mc value.value >>>>>>>>>>> 0
2022-01-17T01:46:23.962013866+00:00 PRINT Zigbee Switch Mc <<<<<<< Power meter Timer >>>>> ON
2022-01-17T01:46:23.966310241+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 8f2a9f23-5370-4144-b511-a698cd635321 [0xAAED] (Workbench Light)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“state”:{“value”:“on”},“component_id”:“main”}
2022-01-17T01:46:23.977938032+00:00 DEBUG Zigbee Switch Mc Workbench Light device thread event handled
2022-01-17T01:46:23.982264741+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee health poll
@Paul_Oliver
I’ve moved this answer to the corresponding thread.
https://community.smartthings.com/t/beta-zigbee-edge-driver-compatible-with-lidl-ecosmart-osram-smartthings-others/231689/1422?u=mariano_colmenarejo
How do you link this device to STHM? Kidde isn’t listed and IFTTT wouldn’t work with STHM, correct?
You would create a virtual smoke sensor which is also a switch to act as a proxy in ST. Then use Ifttt to turn that switch on. It’s hacky, but will work for some people.
@TAustin ’s VEdge Edge Driver has a virtual smoke sensor option. 
Clever. Those virtual device are pretty handy. That also actually answers a previous question I had about creating a “heat sensor” that would trigger a fire alarm as well. If any of the house temp sensors exceed their max temps, set off the alarm. Thanks 
I’m wondering if a Zwave lock driver is in the works.
I’m sure it is, though I’m wondering what the delay could be
If I have a virtual device that is a conglomeration of existing physical devices, would the VEdge driver handle it locally? Note that the following example was designed for Echo Speaks, but it could be used elsewhere.
My dining room has five window sensors. I have created a virtual contact called “dining room”, and the system would warn that the dining room had an open window if it perceived we were leaving or after bed time.
It would be great if that many-to-one translation could work locally.
Just for awareness, there was another commit entitled ‘Add more drivers and fingerprints’ a few days ago.
It looks like it may also include tweaks to correct the behaviour of some devices that have been around for a while, though that may just be where new devices are being added and be wishful thinking on my part.
Ecolink FFZWAVE5-ECO
Does anyone know if a driver was completed to include the smokeDetector and carbonMonoxideDetector capabilities before I climb a ladder?
no, they were never added.
There is z-wave driver with those capabilities, however not for that model. You will need to add fingerprint for that one and test how it’s working.
I have added fingerprint for First Alert Z-Combo model and it’s working. They have two older First Alert midels, but not the one currently sold on Amazon.
Tested my alarm and it is working. Only issue is icon. It is the same icon for Connected and when Alarm goes Off. Besides that everything works.
Groovy DTH:
Edge Driver:
You should try to add your device fingerprint
While I think soundSensor is a poor option for this device, I also think smokeDetector and carbonMonoxideDetector would be wrong. The device doesn’t detect smoke or CO, it detects the sound of smoke and CO alarms. Why not report that?
In my opinion the correct capability is soundDetector though that should be enhanced to have explicit sound types for smoke and CO alarms. Apps such as STHM should add soundDetector to the monitored capabilities.
What driver did you use? When I used the stock ST z-wave smoke detector driver for my Z-Combo the CO was offline.
Stock Z-wave. I just added fingerprint for this model.
- id: 0138/0001/0003
deviceLabel: First Alert Smoke Detector
manufacturerId: 0x0138
productType: 0x0001
productId: 0x0003
deviceProfileName: smoke-co-battery
Mine has a productId: 0x0002 so I did not need to add the fingerprint.
Honestly I don’t care what the capability is called as long as it detectes both Smoke and CO and works with STHM. Adding the capabilities to the driver is something I don’t know how to do.
I disagree Graham. It is essentially only a smoke or CO2 signal. It just collected its data for the trigger in a different way.