![]() ![]() Move what you can to Routines in the SmartThings app. ![]() If you’re using webCoRE, we recommend the following before September 30: ![]() It hasn’t been updated to work with the new SmartThings architecture. But other popular community SmartApps, like the webCoRE automation creator, will stop functioning come December 31. Some third-party applications, such as SharpTools, plan to automatically migrate to the new platform before Groovy goes away. Community developers must adapt their SmartApps to SmartThings’ Cloud API model. While developers have had almost two years to update their SmartApps, Samsung will no longer host the code to run them. Several popular cloud-based products and services like Life 360 and Logitech Harmony may stop working come December 31.Community-written SmartApps are in a bit more precarious situation. So plan ahead before December 31 if you’re using any of these in SmartThings. Some popular community-created cloud integrations might stop working, too, including for devices like MyQ. This includes things like Life 360 and Logitech Harmony since their respective companies haven’t moved to the new API. But several popular cloud-based products and services may stop working come December 31. ![]() Several cloud-connected devices like Ring, Rachio, and Arlo were automatically migrated to new API-based integrations. It’s up to the manufacturer to develop new interfaces using SmartThings’ new cloud-connected API. Possible complicationsĬloud-connected devices are a little…cloudy. Many of these will run locally now that all hub-connected devices will use SmartThings’ Edge Drivers. Routines in the mobile app also use the Rules API in the background. The new Smart Lighting app will utilize the Rules API so its automations run locally. They will also migrate the popular Smart Lighting and Severe-Weather Alert SmartApps starting September 30th. Samsung migrated some of the default SmartApps-like lock management and Smart Home Monitor-when they retired the classic SmartThings app. Going forward, SmartApps will use the SmartThings API. In both cases, these were historically built in Groovy, and Samsung hosted the code in their AWS cloud. SmartThings provided some default SmartApps and community developers also created their own. SmartThings uses SmartApps to automate or connect to outside services. This includes 2015-16 Samsung TVs and older Samsung and D-link cameras. There’s also a small set of devices that will have less functionality or not work at all. Any device that fails migration to an Edge Driver will show up as a “thing” and require a manual fix. If a device gets migrated to a driver with less functionality, it might be removed from Routines and Scenes. You can manually re-add the device to use a custom Edge driver, or the migration will try to move the device to the custom driver before a standard driver. Otherwise, you may lose some advanced functionality with a standard Edge Driver. If you use a community handler today for advanced functionality, try to find an equivalent community Edge Driver. For Z-wave and Zigbee devices, the migration to a default Edge Driver will be based on the fingerprint those devices expose to the SmartThings hub. Samsung will kick off an automatic migration process around the end of August to move devices from legacy handlers to Edge Drivers. So far we’re impressed by what we see of SmartThings Edge. Community developers have also been creating custom Edge Drivers that add advanced functionality power users are looking for. Consequently, the SmartThings team has been developing a set of Edge Drivers to replace these legacy handlers. Samsung announced almost a year ago that they would replace these with Lua-based Edge Drivers for the LAN, Zigbee, and Z-wave devices that connect to SmartThings hubs. SmartThings’ legacy platform uses Groovy Device Type Handlers (DTHs) to translate data to and from devices connected to its platform. The Routine creator Drivers replace Device Type Handlers ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |