Preview | SmartThings-managed Edge Device Drivers

There are many many more people who are missing out on custom drivers because it involves copy/pasting custom code today. Being able to subscribe and click to install will make it easier for end users to install custom drivers.

Only install drivers from companies or developers you trust. Even with open source, unless an individual/group is reviewing the code, then you can get malware.

2 Likes

How are users going to change to use Edge drivers when Groovy stops working? Will you swap our devices from using DTH’s to Edge drivers automatically, or will we have to manually uninstall and reinstall each device individually?

Right now the beta is focused on developers and building edge drivers. There will be a separate announcement regarding migration/transition at a later date.

4 Likes

Many of us on here not only read, but modified code to suit our own needs.
I can’t help but feel that ‘closed source by default’ is a step backwards.
It should be open source by default, with the option for commercial operations to distribute closed source code.

2 Likes

We are making our drivers available here:

and here

Given that we are no longer hosting the code for community Edge Drivers it is up to each developer as to how they store their code.

4 Likes

My biggest concern about the new Edge platform is, with everyone rushing to just get their driver out, we’ll get a bunch of plain vanilla drivers that lack thoughtful capabilities that make the platform useful.

See my post today regarding changes made to ecobee which deprecated some very desirable capabilities that created a great automation ecosystem with ST and Classic.

3 Likes

Once you are installing the code by subscribing to someone else’s channel, there’s no way to know for sure what’s in it, just like downloading an app from an App Store. you have to trust the persons reputation.

The only way around this is if the person makes the code available and you put it into your own channel. But that’s a lot more work than most customers want to do.

So I think closed by default is how most people get most software. Like over 90% of phone apps. You may prefer the other way, but I don’t see anything unusual in smartthings having that architecture. FWIW…

Edge is not for C2C integration such as ecobee. Edge is for devices that are paired to SmartThings with protocols such as zwave and zigbee…

2 Likes

Hi Caleb, Can you fix my account too?

I’m still just getting the spinning icon after clearing cache, and trying the incognito window.

Thank you!

@caleb.varberg

If you’re trying right now, AWS is having some issues impacting samsung login to driver channels
Https://status.smartthings.com

I added the driver for the vent (Keen) but when I paired them they did not pair with the driver.

Does your device’s manudacturer and model corresponds to the ones of this fingerprint?

- id: "keen/sv01-610-mp-1.1"
    deviceLabel: Keen Home Vent
    manufacturer: Keen Home Inc
    model: SV01-610-MP-1.1
    deviceProfileName: vent-profile-1

Nope. Didn’t think to check that. Here is what I have.

SV01-410-MP-1.0
SV02-410-MP-1.2
SV02-410-MP-1.3
SV01-410-MP-1.5

Yeah there’s a whole host of IDs the Keen vents show up as - depending on which version the vent is. AFAIK they’re all functionally identical. How do we get multiple fingerprints added?

Wonder what they’re going to do about Peanut plugs. Half the time they don’t properly respond with an ID when queried.

Edit - just checked mine - they’re all ‘SV01-612-MP-1.1’ units. I’ve also seen ‘611’ variants in the wild as well. Also, from what I’ve seen in researching the issue (had to do this research to make mine work with Homeassistant - Zigbee2MQTT didn’t recognize mine either.) when you see 1.x it is a fair assumption that you also need all ids that include integers between .0 and .x

So while they have: SV01-610-MP-1.1
THey also need:
SV01-610-MP-1.0
SV02-610-MP-1.0
SV02-610-MP-1.1
SV01-410-MP-1.0
SV02-410-MP-1.0
SV01-410-MP-1.1
SV02-410-MP-1.1
SV01-410-MP-1.2
SV02-410-MP-1.2
SV01-410-MP-1.3
SV02-410-MP-1.3
SV01-410-MP-1.4
SV02-410-MP-1.4
SV01-410-MP-1.5
SV02-410-MP-1.5
etc.

I have not seen any difference in functionality. The newer versions will indicate when the signal is weak, or if it is disconnected, with a double flashing yellow light.

A post was split to a new topic: [ST Edge] Ïssue with the Zigbee Power Meter driver

@fido Have you tried the ST Z-Wave Bulb Edge driver?

id: Fibaro_RGBW_Controller/EU
deviceLabel: Fibaro Light
manufacturerId: 0x010F
productType: 0x0900
deviceProfileName: fibaro-rgbw-controller

If it is a direct copy of the groovy version it wont work, the colour rendition was way off to start with, the Fibaro hardware driver itself has special options for various scenes, without access to these in built scenes through the app a generic driver wont do

Appreciate the pointer and if someone says it works and presents all available options and settings (which are extensive ) im more than happy to reset the device and try it but as it is installed in a difficult to get at position i need someone to report back first

Hey guys! Long time no speak. I am having a small problem with smartthings and home assistant as i cant get my hands on an aeotec zwave stick 7.
Since the new edge drivers, i have seen that they finally added the fibaro double switch 2 which i had lying around so i bit the bullet and installed one using edge drivers. The only thing is when the device gets added to HA i only see one switch. No secondary switch no nothing. Anyone have any thoughts on this?

1 Like

I suggest you start a new topic on this and then hopefully others who are using home assistant will be able to comment. You can put it in the following section of the forum:

I do know that at the present time many third-party integrations, including the voice assistants, do not see multiple endpoints on a device that is communicating through an edge Driver. So it’s the same symptom, I just don’t know if it’s the same cause. :thinking: