Ah thanks. I did not know you could not do that. Strange that. Probably because I always add them to a room and never try to remove completely.
There appears to be a bug with date/time on z-wave repair on iOS
Network Repair date?
It looks like that was a design choice in the new app. You even canāt add a device without it being a room. The only way is to use the old app.
When I add devices in the old app, they show up as in the āNo Room Assignedā section (at the bottom of the rooms) in the new app. However, I note that if I remove a device from a room using the old app, that section does not re-appear.
Rainy day here in Minneapolis, so I made the jumpā¦ My transition (initiated by me, not a banner message or anything like that) seems to have gone well - I donāt think I have any missing capabilities, but I guess weāll see over the next week or so!
Until these were fixed recently, the new appās lagginess and the inability to use modes and locations more broadly in Automations were the 2 big things holding me back.
I didnāt use WebCore a ton before, but my few pistons were critical for meā¦ Between Scenes and Automations in the new app, I was able to set up everything I used to use WebCore for, so thatās nice.
I wish Automations were just a tad more robust, like āIf (X) and if (Y or Z), then (Q)ā, but itās at least a good startā¦ For instance, one of my old WebCore lighting pistons could only be replicated by creating 6 new Automations, but hopefully future enhancements to Automations will enable me to consolidate those back down again.
Smart Lighting now seems rather out of place in the new app - itās kind of a weird little step-sibling to Automations ā¦ I like its simplicity & features, so I kept most of my pre-existing setups in there (6 total now), but Iām leery that SmartThings is going to deprecate it as the new app matures - itās sort of hard to justify its existence in the new app, but perhaps Iām missing somethingā¦ I know Smart Lighting runs locally for sure, but do Automations too? I dunnoā¦
The ability to set my lighting color temps below 2700K in Automations is a huge win - that alone was a big reason I was previously using WebCore.
Fingers crossed my efforts today all end up working as planned - we shall see!! 
6 Likes
As of this writing, only some parts of smart lighting and some parts of smartthings home monitor can run locally. (Those are both also considered automations, though.)
Automations that you create anywhere else in the smartthings app and custom smartapps do not run locally.
https://support.smartthings.com/hc/en-us/articles/209979766-Local-processing#What
2 Likes
Thank you, sir! that was the very article I was trying to find, and I somehow didnātā¦ My search-fu is weak today. Appreciate the clarification!
2 Likes
I havenāt tested real recently, but last time I thought about moving from Smart Lighting to Automations, the timers werenāt acceptable. I believe the problem I had is for real basic motion lighting. Turn a light on with motion, turn it off 2 minutes after motion stops. The problem was the light was turned on by motion, the light would turn off after 2 minutes - but that wasnāt re-evaluated by the automation, so it didnāt care if motion had happened again, or was still happeningā¦ 2 minutes later that light was turning off.
Not sure if thatās still how it goes as I havenāt tested lately
3 Likes
When I migrated (manually) my sole motion controlled light to the new automations, I ended up with 2 separate rules - one that turned the light on if motion is detected, and another that turned the light off if no motion is detected for 5 minutes. Iād rather it all be in one but at least it does work.
1 Like
Correct, this was an intentional choice. During device join in the new app, you are required to choose a room. The only way you end up with a roomless device is by joining it or removing it from a room through Classic (one of many reasons why weāre trying to get away from a dual-app architecture). āNo Room Assignedā is actually considered a room, but was intended as a container for anything thatās been kicked out of a user-created room.
2 Likes
Support for more complicated and local automations are in the worksā¦see below article from SDC last year:
Documentation on Rule API is here: https://smartthings.developer.samsung.com/docs/rules/rules-breakdown.html
Thanks for migrating and sharing your experience. If you run into anything funky please let us know hereā¦weāre opening up to more users every day and monitoring the experience carefully - we continue to appreciate the communityās feedback; itās really helpful.
3 Likes
Thanks Blake! The recent updates to the new app were most definitely a huge step toward easier conversion, and I look forward to future enhancements.
I had a relatively basic setup (not much WebCore, not a ton of devices/integrations overall), so I figured this would be a good time to take a stab at migrating.
This has given me a good foundation for working with automations (little āaā intentional) in the new app, so I feel better positioned now to keep up with future enhancements.
Thank you for the good work on the new app - itās cominā along well!
1 Like
@blake.arnold
First experiences trying to add devices in new app. (Context, until this weekend I EXCLUSIVELY used Classic to add devices.)
Discoverability in the add devices section is a mess. Youāre forcing a brand - first experience. PLEASE PLEASE give me a way to skip this and jump right into add generic Zwave or Zigbee device. (Needs to be a first class citizen at the top of the UI) Donāt make me scroll pages of brands to find the one I want or switch tabs to get to device types.
It made the process take at least 2x the amount of time it did in Classic (due to discoverability) and anecdotally, the progress meter in the new zwave add UI is frustrating. (Skipping 15-20% at a time with no progress in between. Leaves the user wondering if anything is happening.)
End result. 2 switches added. 45 min. Frustrated user.
4 Likes
The āscan nearbyā and āScan QR codeā options can be used for general inclusion. They used to be at the top of the screen on iOS, but got moved to the bottom corners recently. Looks like Android may still be at the top.
2 Likes
I hear ya Jimmy - unfortunately itās not entirely obvious thatās what itās for. 
3 Likes
Search function (upper righthand corner on Android) is helpful as well. Eliminates the need to search by brand, then device cat, then device. Thatās what I usually use. Tested this just now and was able to join an ST and non-ST device within a minute. Good suggestions on the UX thoughā¦we are continuing to try and refine this to make it as simple as possible while still as flexible as possible.
6 Likes
@blake.arnold any update on adding a ācontact sensor open for X timeā option to the Automation creator? A lot of WInk refugees looking for that.
1 Like
My roomless devices get created in the IDE as I stopped using Classic months ago. You canāt add the Group/Room on the first pass when creating a device, and even if you edit the device to add the Room, it doesnāt tend to get picked up by the new app (at least not reliably). Room syncing remains a bit one-way.
I donāt have a huge issue with having to have my devices in a room, though Iād prefer it to be an option, but the situation @GSzabados described with āBring device from other roomsā not picking up the unassigned devices does sound like a bug rather than a feature.
3 Likes
I know this is probably hopeless, because Iāve been bringing it up for four years, but please remind your UI developers that when you put something important at the bottom of the screen, those of us using voice readers have to then listen to every single item on the screen above it read aloud before we get to the important stuff.
(Yes, thereās an option to skip down to the bottom, but you donāt know that you should be using that if you canāt see the screen.)
7 Likes
I thought that too when I first started using the Android version of the new app, but then I realized that āScan Nearbyā was the general inclusion function. The way it was presented in the UI (especially with the words āNearbyā, which for some reason made me think it was looking for Bluetooth devices or something), really confused me.
3 Likes
you are right actually. It does also look for bluetooth devices.
1 Like