Thanks!
That is what happened when I tried to subscribe to the newsletter.
Thanks!
That is what happened when I tried to subscribe to the newsletter.
Subscribing throws a 404.
Yep I was thinking the same about DTH migration/ the end of groovy. Do we have any time frames?
No ETA has been defined yet, @Olicoley. However, the team has mentioned that it wonât be an abrupt change so, donât worry about having issues out of the blue.
Could you confirm that SmartLighting automations will be migrated to Rules API without me having to actively do anything. Thanks
@23dash I think you would prefer local automations which are available now. The only hiccup I have had is that there is no way to sync switches and lights to make them mirror eachother. I have a lot of smart switches and smart bulbs. Syncing their state is a pain without creating circular automations.
Check out this link for moving from SmartLighting to using automations.
I know itâs possible for me to reconfigure SmartLighting as Automations. Iâm trying to establish whether the team at ST plan to make this painless by migrating these to Rules API without the need for user intervention. Imagine all those guys who donât follow this forum⊠theyâll be mighty annoyed if their SmartLighting automations suddenly stopped working.
I understand @23dash. Iâm checking this situation with the corresponding team. Once I get more information, Iâll post it here.
But what about functions that is in the smart lighting app and not in the rules api. I have many zigbee light bulbs that mirrors the behavior of a dimmer. Will this function stop working?
One particular item for us thatâs missing from the Edge drivers Iâve used so far (not sure about Rules API) is the ability to have a light/switch turn on more than 60 minutes before sunset.
Because of that limitation, Iâm still using Smart Lighting app to have a light come on 2 hours before sunset.
All specific times in the Rules API are expressed as +/- offsets from reference times (now, midnight, noon, sunrise and sunset). A time operand can be a maximum of 86399 seconds though I donât really know what that means in practice, but 60 minutes is certainly not of any special significance to the Rules API. So there really shouldnât be an issue.
I personally have had issues with sunrise not being updated on a daily timer for the last six months or so, but that doesnât mean anyone else will.
24 hours=86400 seconds.
I was wondering who would bite on that first.
My point was that I wasnât entirely clear what information was being imparted. It might simply mean that a time is saved as an integer from 0 to 86399 so if I specify fifteen hours after noon I actually get a second before midnight.
Any update on whether SmartLighting routines will be migrated without user intervention
Thanks
This came up in another thread.
Even with Edge, the SmartThings app and any notifications are still going to be cloud-based, right?
So some pre-created routines will be able to run if the Internet is out, but you wonât have app control or get notifications or be able to create new routines until the hub can talk to the SmartThings cloud again. Or am I wrong on that?
This is my understanding. Local automations will run, but the app and its notifications require the cloud. The app isnât tied to, nor served by, the hub itself. They would need to make a version of the app that connect directly to the hub like Philips Hue.
Iâm curious to see if this will change once smartthings adds matter support since matter is intended to be âlocal first.â Matter doesnât require that everything except voice run locally, unlike HomeKit, but it strongly encourages local operations.
I have several devices that run locally with HomeKit and via cloud with smartthings, like Meross, Lutron, and Phillips hue. When our Internet goes out, which typically happens three or four times a year, I use the HomeKit app since the ST app stops working until the cloud connection is restored.
It would be great if smartthings switched to the other connection model, but I havenât heard that that was part of the plan.