![]() ![]() ![]() I am pretty sure Konnected may already be using the New ST API, as I do not see where they are asking users to install Groovy SmartApps/DTHs any longer. For all I know, this work may have already been completed and the change is transparent to the end-users. This means their web applications simply need to be changed to use the New ST API as opposed to the current Groovy SmartApps that provide their endpoint connectivity. For SharpTools and ActionTiles, they are already hosting most of their custom apps on existing Cloud Webservers. As such, I believe this group of folks is highly motivated and will be successful in adopting the New ST API. They have financial incentive to figure out how to work with the New ST API. These are folks like SharpTools (, ActionTiles (, Konnected ( RBoyApps ( and Apps and DTHs. ![]() With no officially announced roadmap for the future of hub-connected DTHs, these developers probably aren’t too enthusiastic right now, IMHO.Īnd then there is a group of developers whose business is based upon selling SmartApps and Device Type Handlers to ST Users. As for DTHs, those are still Groovy for now… but eventually that will change as well. Users may need to self-host these new SmartApps on their own local or cloud infrastructure. These developers are unlikely to stand up their own AWS servers to allow ST Community members to continue to run these ‘New ST API’ based applications. Especially SmartApps, which will no longer be hosted on the ST Cloud infrastructure. ![]() I believe there is another group of developers who worked really hard to get their Groovy code working properly, and who are not very enthusiastic about having to rewrite their code, as it may be quite a bit of work. These SmartApps and DTHs are not being actively supported, and thus will die on the vine, once the Groovy IDE is shut down. I believe a lot of developers from the early days of SmartThings are long gone, even though many of their SmartApps and DTHs are still actively used by many in the ST Community. I believe there are a few categories of developers to consider, as follows. Here are my thoughts on the state/fate of existing custom ST code. I just really hope it stays that way and am not sure this will be the case after the full transition, loss of the classic app, and loss of the IDE. But it’s the one that looks more like a scripting language. This is the most Webcore-like option, and is still in development. (Not available in all regions)Ī new SmartThings Home Monitor alert (I think you can, I haven’t checked to see if alert with lights is still available in the new app) And, yes, it’s just as confusing as classic in that sense.įor example, if you want to have a motion sensor event trigger a light, in the new app you could use:Ī custom automation created by tapping the + in the upper right of the home screenĪ new smart lighting automation created by tapping the three horizontal line icon in the upper left of the home screen, then choosing smart apps, then choosing smart lighting. there are still multiple ways in the new app to create what is essentially the same automation, although each way may offer somewhat different features. One thing the new V3 app did NOT do was combine everything into one rules engine UI. I have the impression that the webcore and rule machine replacesments is what their new automations are supposed to be, so if you are planning on sticking with ST start playing with them to get used to it. The rule engine looks sufficient and there is dual zwave zigbee hw available… i dont see much liike various apps etc though i do have servers running in my locations and also some qnap nas that can run it in docker… There aren’t a ton of options for advanced smarthome functions left out there, and a long list of hubs that turned into bricks when the company folded or abandoned them. The average smarthome user wants to plug something in and work, and just thinks its good enough to ask Alexa to turn a light on. I think all of us posting on here are the exception though. I think the only other option was Home Assistant on a raspberry pi, which was truly local and all user supplied hardware, but very complex to setup. Samsung is a huge diversified company that I don’t think will go anywhere anytime soon. Sure Hubitat runs almost entirely locally, but there are a bunch of things it relies on a connection for, like firmware updates, etc. I looked into Hubitat when leaving Wink, and didn’t go for them because what if Hubitat is the next Wink? Hubitat is a small company that could vanish tomorrow. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |