New Stock Edge Drivers Beta list

Devices & Integrations
101

Now I get this when I try

Forbidden
You do not have permission to access the specified invitation

1 Like
102

Try clear the cache. Incognito or other browser.

103

The link posted by @Mircea_Cosmin_Ionica appears to be to the acceptance page for the channel during the authorization flow for their account. Their account doesn’t belong to you, so you’re getting a forbidden error.

Follow the link I posted above to the ST beta driver topic, and find the channel invitation in the first post. Alternatively, if you’ve already enrolled in that channel, you can access the page to install additional drivers by navigating to your ST Hub device in the ST app, and then finding that channel in the list of drivers.

I will not be posting a direct link to a channel invitation that I do not own. Just like with anything else on the interwebs, you should know the source of the program you’re installing.

4 Likes
104

This topic is for discussion of “stock” edge drivers. Those are provided by the SmartThings company.

For discussion of a “custom” edge driver channel, one that you have created, please start a new thread in the following section of the forum:

Community Created Device Types - SmartThings Community

Thank you.

2 Likes
105

I have added a topic where you can post requests for new community-created edge drivers. That should make it easier for the community developers to find the requests and hopefully get you a quicker response.

So I suggest you move your post (which was great, by the way, all the essential details) over there and hopefully you’ll get a response.

Post Requests for Edge Drivers Here (community-created)

3 Likes
106

The following text has been amended as the Z-Wave drivers are not new, they are updates.

Just wanted to mention that some new and updated drivers are available, including a new Zigbee Light/Switch driver that covers a long list of switches and outlets.

The updates are to four Z-Wave drivers including switches.

Sadly the Sonoff S26R2ZB must have missed the cutoff for Zigbee switches, as the Sonoff button did for the Zigbee Button. The Sonoff temperature/humidity sensor also isn’t in a stock handler.

Apart from an IKEA Shortcut button that I can’t use until the battery drain issue is sorted, I think I all my branded devices will be totally covered by stock Edge drivers once those three get sorted. There is a lot of snagging to be done though.

3 Likes
107

Hopefully zwave sensor and zwave smoke detector is readded soon. I cloned the github repo for zwave smoke detector and built my own driver but Co stays in “checking” state and status doesn’t revert to clear after testspo still definitely some issues there.

108

I did the same without even nothing showing up in the ui.
First alert smoke and co .

109

smoke did show up for me…even tested with some smoke and it worked but just as with test it wouldn’t revert to clear

110

They have been updated but it just seems to be the fingerprints and profiles that have changed.

111

Apologies if this has been already asked, but I have not found any information about.

I just paired a Sonoff ZBMINI using the stock edge driver. It’s working as expected. However, when I check the history information, it shows lots of on/off events that I have not generated (no routines created either).

I have reinstalled the driver after several hub reboots and paired again. No luck, same behaviour.

Can this be fixed?

Screenshot_20220116-215956
Screenshot_20220116-2159561080×2340 149 KB

112

The Sonoff ZBMini does not work properly with the Stock Edge Driver or @Mariano_Colmenarejo Edge driver. Mariano put a lot of effort into trying to get it working properly, but he was not successful.

It works just fine on automations. But the strange thing is the the light is usually off even when the app says it is on.

113

That’s a pity. I understand that it’s beta phase, but I would say that stock driver should have some bugs rather than faulty behaviour. Shouldn’t be removed the fingerprint?

I have tried Mariano’s version as well. Fair attempt from his side.

114

Samsung published a nice list of devices added to Edge. It doesn’t include the release from Jan 11th with all the zigbee switch devices, but it seems to include most drivers before that.

1 Like
115

@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           │
└─────────────┴──────────────────────────────────────┘
1 Like
116

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.

117

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

118

@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

2 Likes
119

How do you link this device to STHM? Kidde isn’t listed and IFTTT wouldn’t work with STHM, correct?

120

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. :sunglasses: