Hub Connected Devices Now Use Edge Drivers

[JDRoberts]

@Skates

I linked to the wrong thread the first time. My bad. It should be:

Hub Firmware Beta Group, get ready to migrate!

I have corrected my post above.

[nayelyz (SmartThings Developer Support)]

@csstup

I’m going to guess those are stale values from the device when it was under the DTH.

@csstup is right, @Mariano_Colmenarejo. The team has seen the same behavior with other migrated devices, the values in “Route” and “metrics” remain the same before the migration. This means this value won’t be up-to-date.

[csstup (Corey Stup)]

Can’t wait to see these current values for Edge based Zwave/Zigbee devices in the CLI!

[Automated_House (Jimmy)]

There’s now an official virtual switch Edge driver in production

SmartThingsEdgeDrivers/drivers/SmartThings/virtual-switch at production ·...

[BlackRose67 (Brad Clarke)]

Is there something we need to sign up for to acces that, like we did/do for the Edge beta channel?

[orangebucket (Graham)]

@Automated_House

There’s now an official virtual switch Edge driver in production

My speculative guess is that it will be tied in with the virtual devices the CLI can create and this will be the local version.

[Automated_House (Jimmy)]

yeah, it remains to be seen how to actually create a virtual device that uses that driver. At the minimum, I assume it will used to migrate existing devices that use the default virtual switch and simulated switch DTH. There’s already a couple community created virtual device drivers that are more flexible and easy to use, so I don’t know if i’d ever use this default option.

[orangebucket (Graham)]

@Automated_House

Yeah, it remains to be seen how to actually create a virtual device that uses that driver. At the minimum, I assume it will used to migrate existing devices that use the default virtual switch and simulated switch DTH. There’s already a couple community created virtual device drivers that are more flexible and easy to use, so I don’t know if i’d ever use this default option.

I don’t suppose it’ll be that different to how it was for the DTH version. Just an API call from wherever. When I was reading the code last week I noticed it has the state change flag set like the DTH does so it fits the bill for a straight swap. I didn’t think to test how the virtual switch created via the CLI behaves in that regard. I have lots of virtual devices created with community Edge drivers and I am hoping to be able to replace all of them with a stock solution.

[milandjurovic71 (Milan)]

You can swap stock driver now, but you want be happy with it. I doesn’t have all extras that community created have

[orangebucket (Graham)]

@milandjurovic71

You can swap stock driver now, but you want be happy with it. I doesn’t have all extras that community created have

I’m holding off for the moment as they clearly aren’t ready (and, to be fair, they aren’t claimed to be). Some, like the virtual switch, will work but others are pretty much useless as they don’t have commands. Using the API to set attributes is not a practical option. I’ll also need to have local and cloud options. Very few ‘extras’ are of interest to me.

[allmac (Alberto)]

Smartthings Home Connect and Smartthings Wifi are already Edge ready. Latest update this month.

[Shri (Kodali)]

Anyone having issues with connect hub updated to latest firmware and still dont see edge drivers ?
Hub model # ET-WV520

[Paul_Oliver (PCO)]

Could be related to Thursdays ST cloud issues, which have reportedly been fixed.

ST Cloud Offline? (28 July 2022)

Was trying to add a device through IOS and that failed multiple times. I later tried to manually exclude and “network cannot connect” (for more than the usual delays). Then I checked the hub, which was glowing green, so I went to the legacy IDE. I realized no data was coming in and confirmed this with live logging. I then powered the hub off and back on (waited 30 seconds). I’m now getting solid blue. My internet is working fine. Is anyone aware of a ST cloud issue?

[jkp]

Have you attempted to subscribe to any of the Beta Edge Channels from any of the Developers to see if that changes? Would be interested to see if it changes

[Shri (Kodali)]

@jkp When I enroll in beta program, drivers show up as expected .

I have two connect hubs at two different locations and both behave the same way.

[Shri (Kodali)]

Thanks @Paul_Oliver . That explains many failed attemps yesterday adding Ikea button. That page says the issue has been resolved now but, my hubs still dont show edge driver option .

[nayelyz (SmartThings Developer Support)]

@Shri

my hubs still dont show edge driver option .

Where is it not appearing? The picture you shared above belongs to the “Driver” option inside the Hub

@Shri

It says you have enrolled to that channel but, have you installed any driver? For example:

You need to check if your device is supported in that driver, you can check their fingerprints in the official drivers’ repo:

[Cory_Booth]

I ran into a similar issue myself when a Z-Wave switch, overnight, switched to Edge.

The only thing you can do is to shut off the “indicator” LED and hope the Edge Drivers support this later on.
You can manually toggle the LED setting using the “up-up-up / down” technique.
Quickly hit UP three times, then Down once.

I found I could only activate two modes:
On when off
Always off

I actually prefer “on when on” - so mine are “off” for now

[nayelyz (SmartThings Developer Support)]

@Cory_Booth

into a similar issue myself when a Z-Wave switch, overnight, switched to Edge.

Can you provide more details, please?

• Device brand and model, this is to look for the device on this page: Catalog of Certified Z-Wave Products
• Do you know which DTH did the device use before?
• Which stock driver is it using?
  1. In the app, go to the device details
  2. Select menu (three-dot symbol in the upper-right corner)
  3. Tap on “driver”. There it will show the driver’s name (and other details)