Hubitat from the beginning was very different from smartthings because it was designed to run everything completely locally, except for some third-party integrations like voice assistants. So you were always allowed to run your own custom code on the hub. You also saw a lot more customers with multiple hubs in order to distribute the processing load.
But from a developerās point of view, there were a lot of similarities because it uses the same version of Groovy. It just runs it on the hub.
Each system has its own pluses and minuses, and you will see people moving in both directions, as well as quite a few people who run both smartthings and hubitat.
I remember when hubitat stated & i also remember how member after member in smartthjngs started leaving. I came here in 2016 & this place was kicking. All roads in the internet about smarthomes lead to this address. Then slowly it started emptying out & now it seems like because of hubitat mimicking the old smartyjingsā¦ thats where all the roads are leading to.
Welp RLA stopped working today which was not fun for myself or my guests. Negligence on the part of rboy to not at least send out a heads up. I donāt mind paying for software totally fine, but I like a little bit of professionalism in return.
What does this mean? That SmartLighting no longer works? Because thatās what it means for me. As of two days ago two automations (outside lights on/off with sunset/sunrise) are no longer triggering. The scenes behind work just fine if I run them manually.
The old one was based on Groovy and is most likely now dead.
Smart Lighting was one of a couple of Groovy SmartApps that Samsung recreated, mostly, for the new architecture. Both the old and new versions are region-locked, not available everywhere.
I dont think that is the only indicator, the new version can be installed alongside the groovy version, it is the automations within that indicate if you have been moved, if your groovy automations in SL appear in the tiny text version, then you have been moved
I have the tiny text, but only one instance of the smartapp āSmart Lightingā, and old graphic next to its name (not the light bulb). Iām UK based
Can someone just point me in the direction of knowing how to move my locks and thermostats over to new Edge drivers without having to re-pair them into ST? I have SLGA installed, I can use it to generate codes, but am seeing inconsistent behavior with the existing custom DHs that still show up in the ST app. Iāve read about excluding the ālock/thermostatās fingerprintā in the web, but am just trying to confirm if thatās whatās needed and if by doing that Iām going to have a critical production device drop offline in the process.
The entire point of waiting until the āofficialā transition was promoted as the promise of an automatic transition for lose devices. That seems to have resulted in what feels like a shell of IOT devices whoās status is entirely unclear.
Thanks @jkp so maybe I interpreted the notice above wrong. I read it as a sequential process where migration = complete when SmartApps are shutdown, but now that I re-read it it sounds like devices and SmartApps migrating at different times, which makes this intermediary time when devices kinda-sorta-work pretty challenging.
Groovy devices and SmartApps will sunset soon once we have completed migrations (Note: Groovy SmartApps and Devices may be sunset at different times).
Itās changed from the initial announcement in September 2022.
Originally it was planned to be sequential, with devices completing their migration by December 31, 2022, and smartapps continuing on for a little bit after that.
But then they ran into some issues with the migration and developing some of the stock drivers and they ended up postponing the changeover date for devices to sometime in first quarter 2023. But, as you noticed, appear to have kept the original plan for shutting off groovy hosting for smartapps. So here we are.
Thanks @JDRoberts. Thatās a far more helpful and succinct description of whatās happening than anything Iāve seen officially posted here. I probably just need to get more familiar with SharpTools, since that seems to be the path that many others are using to replicate the kind of conditional workflows, triggers, and calendar integrations that we previously had in the commercial SmartThings apps.
Thanks. Iāll admit I find it Annoying that there hasnāt been an official change log for the migration plan. instead, they go in and quietly edit the original announcement post without doing anything to call attention to the changes. Itās only when sharpeyed community members spot them that the changes become part of the general conversation.
Thanks for the info - I donāt know which version I had (how would you even tell), I simply got rid of it and replaced it with an automation using the existing scenes. Old vs new, should have been migrated if my automations were based on the old one. Oh well.
I know itās been said many times before and Iām just piling on, but this is just a terrible customer experience. No in app notices, vague details published, no clear migration tooling. Itās just frustrating. Not something thatās ready for the average customer who doesnāt want to or canāt deal with the complications of the IOT mess.
This afternoon, all of my automations disappeared. While I presume this is a result of the transition, most were developed in the last 120 days using the mobile interface and no exotic logic. I can understand that some - alarm and the garage interface - would disappear. But loss of 49 out of 49, most using time and local sensors as triggers. No webcore.
What am I missing that all automations go away?
Because thatās what it means for me. As of two days ago two automations (outside lights on/off with sunset/sunrise) are no longer triggering. The scenes behind work just fine if I run them manually.
