Maybe, but right now to me it looks like a public Beta phase. A lot of what should be obvious glitches still in play, including the issues with multicomponent devices, broken labels, inconsistent fingerprint mapping, variable value scales, battery life, etc.
Here are a few from today. This doesn’t look like production to me but maybe I have different standards…
I just noticed that the units are missing as well from the detail view state. Not all, but some.
.
Anyone else getting notifications for devices they don’t have? My dryer just finished according to Smartthings, but I don’t have a connected dryer. When I was adding/replacing some of my devices today, my z-wave motion sensors were registering smoke detected.
.
I have 2 Schlage Connect deadbolt locks that I have converted over to the edge drive. Both added fine, however they do not work correctly in Smart Lock Guest Access. 1 lock shows codes 1 code 2, ect. from a earlier install but now the names are missing and I can’t rename them. The second lock doesn’t even show up or import the default codes. I have tried removing and including it several times. I have rebooted the hub and factory reset the locks At this point I’m stumped, my last lock that’s running a DTH is working flawlessly.
.
I am unable to see “driver” on any Edge device, I am not sure how long this has been an issue because I only just began thinking about the transition again after testing out some drivers a few months ago. I only have two devices with Edge drivers, neither of them shows the “driver” option anymore. Also, I don’t have the driver option when looking at the hub details to see what drivers I have loaded. I’ve tried clearing the app cache, and backing out of the details page a few times to see if that helped, but still nothing. Yes I can add new drivers. Yes devices do pair with the drivers. I am unable to select different drivers though with the “drivers” page missing![]()
.
installed the Edge driver and it works more reliably but still, after a day of no use the ST click would take anywhere from 4 to 8 sec to turn on the light. It’s as if something in the hub goes to a deep sleep and needs to wake up, load, etc. to execute the command and send the HTTP request to the Tasmota web server. Once awoken, it works OK. Does anyone else see the same issue?
![](https://avatars.discourse-cdn.com/v4/letter/h/f1d935/48.png)
Yes. I’m aware of this issue. It has been reported by other developers. [Link] Unfortunately, this comes from the ST Edge platform, hopefully it will be fixed in the next ST hub firmware release soon.