Here I also have no big Problems unti now. All my plugs, switches , curtains automations, lights and sensors are working perfect. Everything with Edge. I think I will only loose my Eutronic Air Quality Sensor. Here no Edge Driver exist , and zur normal Z-Wave driver do not work. Maybe in future.
Does anyone who waited to see what would happen have any new placeholders or things yet? No changes on my end yet.
Same. New firmware coming starting tomorrow so Iād not expect anything before that completes rollout.
1 Like
My Arlo cameras have now stopped sending motion detection to Smarthings AND Sharptools.
They were showing as placeholder in the IDE but now show Arlo Pro Camera.
This is fairly serious as without motion detection , no routines can be used that get triggered by camera motion !
They DO still report motion to the arlo app itselfā¦
Anyone else seeing this?
EDITā¦I just deleted the arlo/smarthings link and set it up againā¦
Now all arlo cameras show as PLACEHOLDER again but now there are 2 of each one , and one of them now detects motion in smarthings !
I have now had to also remove the sharptools linkā¦remake it, and then re-add each device to the rules I had already created ā¦BUT its workingā¦(for now)
Hope that helps somebody with the same issuesā¦
1 Like
But they did announce the Routine Creator, which although only a Beta was communicated as a solid plan last year -
2 Likes
He was one of the primary people working on Rules API. He laid the groundwork, the webcore dev community has chosen to not use it and has moved on to other platforms.
Samsung has done a very bad job with explaining how to use the new environment. I thought I was going to need to use Lua to code the new pieces but then found out it was for drivers.
The Rules API does not allow me to go to the web to interact with other sites. It has a goofy verbose coding syntax. If they hid that syntax behind WebCore they would be in a better position I think.
Whether Samsung promised something or not at this point is not important. They dropped the ball and their platform will be seen as very limited. Maybe the numbers are small so they donāt care.
I want my home automation in one environment. If I am going to do some of my automations in HASSIO Node-Red I might as well do them all. For simple stuff the routines are fine.
3 Likes
This is what I was hoping for.
Having used both Hubitat and Home Assistant, both of those systems have front ends that let you build complicated rules while hiding the super technical stuff.
Iāve worked as an Enterprise developer for 30+ years.
I ācouldā dive into the Rules API and come up more complex rules that the Routine editor currently doesnāt provide, but I honestly donāt feel like I should need to do that for what Iām trying to accomplish.
4 Likes
yes! This is the most disappointing part of this transition. It seems they had a working beta of a complex rules builder using the rules API and thenā¦nothing. This would have been a GREAT tool for those moving off of webcore that found the Routine builder in the mobile app too limiting. Unfortunately both of the people in that video that discussed it are no longer with SmartThings 
10 Likes
Now that the official drivers will be getting installedā¦ should I leave the SmartThings Drivers (Beta) channel?
A new phone (listed under Get your Location from this phone) now appears as āplaceholderā on the IDE, but doesnt seem to actually work to change the location mode. The previous phone was always flaky - I miss the presence sensor - so I dont know if its just an Android thing or related to these changes. Some Hue bulbs just re-added havent changed on the IDE.
I find Android updates frequently break presence ability of the apps themselves.
The last few versions of Android now do things like:
- If an app isnāt loaded frequenty, permissions given at install will eventually be removed. You have to manually opt out of this for each application within a permission manager Settings panel.
- Put apps to sleep more often. You have to jump thru hoops to make sure certain apps can stay running in the background. Especially āpower and networkā hungry apps like ones that need to report presence via wifi access point detection and GPS.
Hi, @Geoffs, @pc-bjorn, @eric182 .
Do you know the device fingerprints of the ones with the issue, please?
I searched the model IM6001 and this one matched:
Hi! No, if you already installed drivers in that channel and added devices to them, it means those devices are already migrated. Devices that are still pending will get the closest driver, it means, if you have a compatible driver already installed, they will be migrated to it.
The drivers in this channel are up-to-date 
My minimotes started working again Saturday afternoon. If you still need more information, let me know.
aah ok, it is no longer necessary, it could have been related to the issue over the weekend.
This is to identify if after a deviceās migration thereās an issue that impacts its functionality so the team can correct it ASAP.
So, please, if you see a comment about this, feel free to tag our team @nayelyz or @andresg .
I donāt actually have any of the drivers in this channel installed. I added to start testing and migrating but so far all the devices Iāve migrated are from other channels. For the short term Iām hoping to allow all the others to self migrate in order to preserve automations, but for the long term Iād think I would want to be on a non-beta channel. Will there be an official channel that will be installed as the migration happens or will the beta channel become the official channel?
I dont know the fingerprint, where do I get it.
The button is the current Smartthings Button.
The buttons I didnt try and fix resolved the next day.
One button I re added came back as Edge (had a Driver entry of āZigbee Buttonā.
The other button didnt have the Driver entry but today it has.
Other buttons still do not have a Driver enrtry.
A third button defunt, I could Not rejoin it. However 2 days later it does rejoin, with Driver of Zigbee Button.
The real interesting thing is that I have the WiFi Hubs (Plume) which is not yet supposed to handle Edge. The notice here
says it will be updated today or so to 0.38.11 - however - it is currently on 043.00005 ?
Psstā¦ 2021 messageā¦.
5 Likes
Thatās an announcement from 2021, the one of the update to 43.5 (July 2022) is here (This version supports Edge drivers):
So, overall, we can say the problems you had could be related to the issue in the platform over the weekend because everything works again, even those with the driver.
Yes, this is because currently, the default joining process checks for drivers first (installed and in the default channel), it will only join with a DTH if there isnāt a driver compatible.
Hereās the announcement about that:
1 Like