Not having visited the forums for a while I had no idea this was happening until the email, and even being familiar with software the email and FAQs arent that easy to digest and work out what the impact will be.
I use the Speaker Companion smartapp as it allows a specific Sonos favourite to be started - but routines/scenes only seem to allow a Play operation - i.e. play whatever was last playing.
The ST app seems to allow a favourite to be chosen so why not a routine/scene - how can I choose what starts playing when triggered?
Note to anyone who might still be using a custom smartapp (which I doubt at this point) to connect their Hue devices to ST. That would need to be changed over to one of the official Hue integrations.
Luckily Iād upgraded to a V2 Hue hub earlier when on sale - but its not a trivial task as the upgrade wizard didnt work so all bulbs had to be added by serial number, a older Livingcolours remote re-paired using Hue Essentials app, and all the bulbs re-added to ST as theyre effectively new devices.
This all seems excessive just because thereās no control to select a Sonos favourite in a routine/scene when its available (at least for now) in the Sonos device page in the ST app.
Iām comfortable with software but Id imagine that many users will be unhappy with these extra steps to restore existing basic functionality after these changes are made.
The following thread is specific to discussing the options for power users who will be losing custom groovy smartapps, including Webcore, but find that basic routines arenāt enough for what they want to do. You might find it of interest.
Right now there are two official integration options: cloud to cloud or LAN.
Cloud to cloud should continue to work exactly as is.
The LAN integration will require a new Edge Driver. ST has said they are working on one, but itās not available yet and some of us suspect they may just wait for Matter support to be released by both companies.
There are some community members working on a custom Edge Driver, but itās still in early beta.
And thatās just if youāre currently using an official integration.
If youāre currently using a custom DTH and/or any custom smartapps for your Hue devices, those will all go away. You will probably have to manually transition to the new platform. And you might lose some advanced features.
Damn. I know I complained about the lack of communication just a week ago, but I honestly didnāt expect that the official communication from Samsung would somehow make things MORE confusing.
Looks like I made the right call finally switching away.
As far as I know Iām using the official hue integration. Well I donāt see any hue smart apps on my app so it just be the official one.
My routines that have Philips hue bulbs, innr bulbs etc all run locally so I assume Iām not running the cloud to cloud integration?
So that will have to be transitioned to an Edge Driver.
If things were done sensibly, ST would leave the official local LAN groovy integration running until they have a replacement, then automatically transition you, but no promises as they havenāt said officially that thatās the plan.
Youāre not overreacting, and I totally agree. Iām sure there are many different user types involved here. I for one am in the category who spent the time initially to get an initial Smartthings-based setup in place which I could āset and forgetā with the odd new webcore piston and/or device as the need arose. Itās worked great with the help of many people on here (including you!) but Iām shocked that the ST team are sending out emails about the platform move but have no transition guides in place. If the comms and instructions were clear, Iād be happy to spend the time to properly prepare, migrate and test everything so that I can once again āset and forgetā on the new platform. But instead, it seems Iām either going to have to find the information littered across lots of different community posts or wait for the cutover, see what breaks and then fix it. But I donāt like that idea because Iād rather spend the time when I can, rather than when I have to.
Shame really, Iāve toyed with the idea of moving to Home Assistant but ST was giving me everything I needed so I stuck with things as-is. If this becomes too messy and painful, I might actually quit.
Side note - can someone just confirm the v2 hub which I have, is compatible with this new platform?
How? Is there a guide on how to assign Edge drivers to my devices? I know my way around the IDE, changing DTHs etc. but no clue on how the new stuff works.
Sheez! I wouldnāt classify my pistons as complex but then thatās relative to how simple the Routines functionality is. It may be that even my not-so-complex pistons are a pain the butt to setup. I think I might just start picking a few of the simplest ones and try and create routines.
ST app is showing my hub as being on firmware version 000.044.00009. Iāve never manually updated the firmware as I assumed it will keep itself up to date.
As mentioned in the original announcement, September 30th marks the kickoff of the final stage of the Groovy sunset. Below are some updated milestones to help you plan for the transition. We will also share additional info very soon regarding the continued support for Virtual Devices.
Sept 30th
Ā· Start ST-managed DTH migration
Ā· Start migration of SmartLighting and Weather SmartApps to new plug-in
Oct 15th
Ā· Update IDE to only allow updates or deletion of existing DTHs
Ā· Disable the ability to add new SmartApps
Ā· Remove the IDE debugging tools (Live Logging and IDE simulator)
December 12
Ā· Start migration of 3rd party DTHās to a ST-owned lua driver if they fingerprint match, if not will move to the Thing driver
