The End of Groovy Has Arrived



1 Like

Hard to tell without more info… you may want to start a new thread and post an image of the piston.

1 Like

It’s been working perfectly for months, and now no longer works. Guessing this is just a symptom of the ongoing degradation of SmartThings infrastructure. If I wasn’t still waiting on a Home Assistant Yellow I would have already jumped ship.


I’ve switched one of the sonoff zbminis to the MC driver.

Manual test shows it is working.
Will need to wait for the routines to see if I suffer “oscillation”.
However when I open up the devices properties in st app (android) it says “could not get the device’s status”
Do you get that ?

No, I am not seeing that problem.

1 Like

1 hour later and I’m no longer seeing that message either. :man_shrugging:
Hopefully it was a transient thing and won’t return.

Hi @Declankh

And if it ever comes out, nothing happens either, it’s not important if you don’t see some capability without information.
This indicates that at that moment it has not been able to update any of the capabilities in the waiting time that it has established.
The same thing happened before, but no message was displayed and this version of the App does.


Thanks for the explanation Mariano. @Mariano_Colmenarejo
There are more settings for the device in the device properties in android compared to iOS. Is that expected ?

Hi @Declankh

There should be the same settings on Android and IOs, but I don’t use IOs and I can’t how to steal it

here is the Android properties/settings

and here is the same screen on IOS

Android is main device so not a big deal for me.

In Android this is fixed with clearing app cache.
In IOs i do not known how solve this presentation for new custom capabilities.

Maybe IOs users can help

My apologies for asking a few questions but I am not a programmer by any stretch, we’re lucky I can even update my computer :sweat_smile:

I have migrated most of my devices to edge drivers now but I’m unclear on a few devices and whether they will work in the edge environment:
(1) Genie Aladdin Connect garage door openers
(2) Ecobee thermostats
(3) Nest thermostat
(4) Ring doorbell

Sorry if this has all been asked and answered!

Edge Drivers are mostly for devices which connect to your SmartThings/Aeotec hub, so primarily zwave and zigbee. There are only a few WiFi devices that will use them unless they are coming in through Matter. :thinking:

Your Ring and Nest devices take a different path, cloud to cloud, and will not use Edge Drivers. They are already on the new architecture. :sunglasses:


Thank you @JDRoberts!

1 Like

I’d like to see a proper websocket driver for Sonos.

1 Like

I’m seeing a few new “behaviors” in the last 2-3 days when “searching for nearby devices” and not sure if these are transition-related or not:
(1) it keeps adding several “eero” devices with a device type of Samsung audio. I do have an eero mesh wifi system but only 2 access points up and running.
(2) it keeps adding duplicates of my LifX LED strips - one is connected LAN and the other Viper.

Any advice on keeping/deleting or preventing “eero” from joining in the future is welcome!

Did I miss comments on whether the new platform allows access to local/non ST resources?

Specifically, I use @zcapr17 logging SmartApp (I dont think he’s been on for 4 years now, but that SmartApp has been going strong for 6 years now…)

This writes to an InfluxDB on the local network. Im guessing if the platform is fully cloud, things like this wont work?

Anyone got any suggestions for storing sensor data in the future?

Check in on Codersaur’s thread for his logger first?

Skip to the bottom:

Codersaur = zcapr17…its his logger Ive been running.
I also saw @eargollo offering, but I cant get it to work, and left comments on his Github page.

I’m pleased to report that after moving to @Mariano_Colmenarejo edge driver I’m not getting the oscillation off,on,off that I got with the stock zigbee switch driver

The only other oddness (and probably totally unrelated to the driver) is that I’m noticing a lag of two or more minutes before a switch change shows in the history log.
When it does appear it has the expected time stamp, not delayed.

1 Like