Say what ??
Didnt think the Sonos integration was ready yet !
Well they did say the near future. It hasn’t been pushed to beta yet so that might be a week off.
Above you mentioned your sonos was merged ?? Probably where my confusion lies, so it has not been auto converted to edge
Sorry, I meant the code is now in the main repository having been rapidly processed this evening. There is normally a weekly update from main to beta but I don’t know if it will have made the cut for this week.
Yes. Same thing. Very odd.
I still see from the IDE my Bose Soundtouch connected via LAN with the old architecture. It’s a wifi product connected via LAN but I didn’t understand if this too will be migrated or not. I’ve seen a virtual edge drive so I tried it months ago but it didn’t work well so I’m wondering the future of this integration…
They have an Edge driver published for Bose. So it should be migrated.
I assume groovy vs edge doesn’t matter here - but are routines with thermostats on edge drivers still run in the cloud? Mine are on DTH still and all run in cloud even though DTH is local.
(sorry wrong link) in this list? because here i still see the drives named with beta (bose included) so i was wondering if there is a different channel for edge drives not beta.
THis is the lsit of all the SmartThings provided Edge drivers in production
Testing on a local Edge based thermostat, common routines are being marked as local. Testing stuff like IF TEMP > VAL THEN TURN OTHER DEVICE ON, etc. Any routine logic that has to run in the cloud (like some conditionals still) or if any device used in the routine is cloud based would of course push the routine to no longer running locally, but most logic should be fine.
Edit: @Paul_Oliver beat me to it.
Interesting. Yeah I should’ve checked virtual thermostat first. Doing that I see the things my local z-wave DTH are doing in cloud move local.
It also may be that your routines pre-dated some of the logic that checked for local-ness. If you open one of your routines and change the name slightly and re-save it, if it involves all local devices it may mark itself local. Or it may be that the local DTH thermostat drivers still can’t run local routines of course…
Ok thanks, I’m not very familiar with github, I had a direct link to the samsung channel, but I was rightly told that the posted link is not good because it is associated with my hub, sorry, I don’t have the “clean” link without the references to my hub. From github I have no idea how to get and install the drives in my hub. I just wanted to figure out if this edge drive is still beta or not. From my app I still see the beta that I installed
You don’t need to manually install the public/production drivers provided by Samsung. They are automatically installed during migration or when you add a supported device.
I’m well aware that the IDE is no longer a trustworthy source but until today it was accurately showing me which devices had converted to Edge by listing the device type as placeholder.
Overnight last night, I see there were three “HubUpdated” events in the hub log.
Now I have several devices which were previously listed as placeholder but now have some other device type.
Sigh.
ok then it hasn’t been migrated yet, as are the hues. none of my devices migrated by themselves, and all those deleted and put back into Edge keep the beta suffix on the drive. 
@HalD As you are aware the IDE is no longer trustworthy. You have to use the API to determine what has migrated and what is still using DTH. Set up the API, it’s very easy to do. Pick devices and then filter it by type and then Dth. That will show you the devices that have not been migrated.
Thanks! I’ve been aware of the API Browser but hadn’t bothered to set up a token and try it. The pittance of info I was getting from the IDE was adequate, until it wasn’t. Now all set up on the Browser.