I totally agree JD, how Amazon is handling Organizational Change Management (OCM) is nothing short of Stellar. Everyone in the industry needs to take note.
UNfortunately most people just toss those emails in the junk bin and ignore them. You and I seem to be among the few nerds here who read it. 
I hope they donāt stop doing it.
I suspect itās part of their marketing outreach and they are expecting journalists and industry analysts to read it even if Most regular customers donāt. 
Poor analogy.
True, but I still belive that some people need to lower their expectations of what they can get out of an inexpensive gadget and instead provide meaningful feedback to the team that is on a tight budget and are trying to do their best with what power they have left at a company that is known to do whatever they want without listening to their customers.
You have a point. I dont think most posters here are knocking the developers at smartthings, but letās face it, when it comes to software, its.not Samsungās strong point & they are known for just yanking apps out of their devices when they dont want to support it anymore.
The bottom line is people will leave smartthings, the unknown is how many, but as this user base shrinks, dont be surprised if you see less new exciting features but instead less support.
For sure some people are leaving. But the scale the SmartThings platform operates at in 2020 under Samsung is quite large. Every single person in this forum could leave and they would only lose 0.1% of their active users.
Time will tell. Letās just hope they can get things fixed before dealing with anything else. Would be nice if everything just worked.
And the service is down again. Hub is online but devices arenāt responding. Lovely.
Awesome. I just migrated from Konnected SmartApp in ST Classic to Konnected Cloud in ST New app, and went through all my automations, scenes, and smart apps to re-add my devices accordingly, and it crapped out on me. I thought I screwed something up royally.
I need to remove the old devices and boards in the ST classic app, (per their instructions) or else it will revert everything back to the Konnected SmartApp. I canāt do that when the service is down though. 
Bad time to have your service go down 4 times in a month when your users are trying to migrate. Not a very warm and fuzzy feeling.
Oh I read them for sure since Iām heavily invested in AWS. Thereās so much ānewā content that by the time I catch up, the news cycle starts all over again.
Jeez, you guys have got it cheap. When I bought my V2 hub I paid Ā£130 in the UK approx $175ā¦
Thank you, @JDRoberts !
I apologize if this was discussed already, and I overlooked it. I did see some mention of it, but not this specific question. Regarding using Life360 as presence sensors.
I migrated this morning, and it went about as well as could be expected, given all the complaints on the new app. Life360 seemed to migrate and connect fine, and I see my 3 users as presence sensors, just as in the classic app.
However, it doesnāt seem that I can use them as designed in an automation. Like many people, I have actions perform based on people coming and going, and yeah, the migration broke my old ones. If I try and create a new Automation, the only option it gives me for location is to enable it in the app, not to use the existing Life360 integration. I can see the sensors under devices, but it doesnāt seem to give me the same level of control. So they give you the ability to add a device as a presence sensor, but not to use it in a meaningful way.
So, am I missing something? Is there a simple way to setup an āif everybody leavesā or āif anybody arrivesā condition using Life360? Or am I going to have to create yet another WebCore piston to overcome these shortcomings?
I wonāt go into the horrible integration of my weather station, or the terrible UI, or everything else people are well aware of.
Thanks
If you are building an automation based on a presence sensor that is NOT the builtin NewApp phone presence, look under āDevice Statusā instead of āMember Locationā fornthose devicesā¦
You are correct, not intuitive at allā¦
I concur with this. I have automations that lock the door when either of us leave. The āIfā is Presence sensor:Not Present. I also have a virtual presence sensor that mirrors the Life360 sensor so that you can have Alexa trigger routines based on the stateā¦which is currently broken due to the new Alexa integration.
I also use the Life360 presence in Smartapps like LUM so that certain key codes donāt activate certain actions if either of us is home.
Yes, itās slightly non-intuitive but Life360 is emulating a device not a geolocation for an individual.
Thank you @nathancu & @h0ckeysk8er.
I did see the sensors under the device list. Unfortunately it seems like these automations are really dumbed down. For example I donāt see any way (could be overlooking it) to add a complex If statement. Like,
If Presence sensor1:Not Present or Presence sensor2:Not Present or Presence sensor3:Not Present and Location mode= whatever.
Or what about adding a time buffer. If Presence sensor1:Not Present for > 5 mintues.
Certainly things I can do in WebCore, and I will likely resort to that. But itās stupid to have to reinvent the wheel on what is supposed to be an āupgradeā
Actually, you can do that particular one. Location mode is allowed to be a pre-condition to any others. You can also change the conditions from All (and) to Any (or). So you end up with:
If Location mode=somestate
then if
sensor1=not present
or
sensor2=not present
or
sensor3=not present
do something
One routine I have is āIf either sensor is present, unlock the front door, change location mode, disarm security, send a notification of disarmingā
Also, you have greater flexibility in some of the SmartApps like LUM where you can prevent certain things from happening based on location mode, presence sensor state, etc. In fact, LUM treats the Life360 presence sensor as part of āPeopleā just like a mobile phone presence.
If you click on your Life360 Sensor under devices, but get an error and cannot access it, you may have to uninstall ST NewApp and reinstall it. I found this resolution in an old post. It was the only thing that got Life360 presence sensors working for me again. The āMember Locationā utilizing the āGet your location from this phoneā seemed to be just as unreliable for geolocation in the ST NewApp as ST Classic, (which I why I switched to Life360 in the first place).
Note: Once you sign in to the ST NewApp again, you wonāt lose your settings, devices, automations, SmartApps, etcā¦ however your main screen (rooms, etc.) will need to be re-ordered, as well as the devices in each of your rooms re-ordered. (The devices stay grouped in your rooms, but the order is reset.) Not the worst of problems, but just a heads-up.
Thanks. I didnāt realize there was a pre-condition option for location mode, that helps a little. Still removes the ability to have an x-minute buffer after leaving to run the automation, but itās a start.
Now if anybody has any ideas as to why it thinks my Weather Station is somehow a motion sensor, Iāll all ears, ha ha
