You have to install New App in 2nd phone, enter to gear icon and activate the phone as a presence location device (Option “Get location from this Phone”, in the screen shot "Obtener su ubicación de este teléfono)), I read some time ago to be sure it works fine its preferred you add a different mail (samsung user) to the members list of your location (one different mail per member and login with different member on each mobile phone) because use same mail (samsung user) in different mobiles could give errors.
Not sure if I would do that now. The new mobile presence in the new app doesn’t make a presence sensor that is available in the classic app. It makes a “place holder” that shows up. However, when you go to settings for the presence sensor, you get a “something went wrong” error. Kind of annoying because you cannot rename or delete it in the classic app.
I’m hoping someone here can help me with this issue. It seems to be directly related to starting after I migrated my home. It’s not just 1 specific device or z-wave only or zigbee only. It’s literally almost everything. My family is not happy at all with the delays and/or non-functionality at this point. When they can’t open the garage door from the app and get stuck outside among other device issues, that gets annoying for them and then they complain that their technology doesn’t work and then they end up not wanting to use it. Thanks in advance.
EDIT: adding also that the Google integration is extremely slow as well. If you tell it to turn a device on or off it take almost 1 minute before the action actually happens.
JD, I like that, your life is your philosophy, very practical and profound at the same time.
Hmmm, not wanting to make you a pariah on the SmartThings forum BUT I’ve got to say/ask: even to a ST rookie, something smells bad with Version 3 rollout. I don’t know enough to say exactly what, though. Are we befuddled users swimming against some nefarious Samsung hidden agenda? Or is this roll-out some profound case of good old-fashioned incompetence? Or is this par for the course in a complex software ecosystems?
Can you comment more on Hubitat? The lack of local processing in ST has always made me uneasy, if my internet goes out because of a power outage (DSL provider seems to have no power backup), so does the automation, even though backed up with UPS.
It required too much technical setup for me, I need a more plug and play system, so I can’t really comment further than that.
As far as the goals of Samsung, I don’t have any inside information, just what I’ve observed as a customer. As I said before, it’s pretty clear that both in terms of numbers of customers and profitability, Samsung’s primary target Has to be the people who buy their $4000 refrigerators and Smart TVs. Those are the ones they need to keep happy.
Once they combined the apps, the number of downloads went up tenfold, literally hundreds of thousands more people. So while I’m sure they would like to keep the hub-based power users happy, at this point we are just a very small percentage of the smartthings customer base. Most people have a hub optional set up.I don’t think there’s anything nefarious about that, I just think it’s market forces.
I started my migration to Hubitat last week after the endless problems and lack of transparency to the development community. It took about a day of learning curves then off to the reset zwave and zigbee devices. Overall I appreciate the set up on a desktop computer, and the IDE is built in so you are not jumping between the iOS UI and the IDE to see what is going on. I am a huge webCoRE fan, but have found most of my logic does work in the native Rules Engine.
To ease the pain, I am using HubConnect v1.64 that syncs the ST and HE hubs, which has provided a seamless experience to the household. In fact, I am using HubConnect to expose the devices to SmartThings, then SmartThings to ActionTiles. It would be great if ActionTiles was native to HE, but HE does have SharpTools integration that I will probably move too over time.
Never thought I would be a big fan of local processing since my job is all about the ‘cloud’, but when running local everything executes remarkably faster AND the last SmartThings outage really had no impact.
Odd on how my attitude changed in only one year when I said this about staying with ST.
The final reason to switch was the pending shutdown of Echo Speaks next month on the ST platform. I had the HE hub in my desk drawer and figured it was time to take back some control of my own household automation. It ST wants to become a closed ecosystem with an external API - great - I will use my HE hub to drive the ST API if still required. BTW, Echo Speaks runs fine on Hubitat.
I didn’t know this background. So Samsung had a different app for the WiFi enabled appliances, to do things like change channels and volume on TV’s? So some exec at Samsung thought it would be a good idea to combine proprietary Samsung appliance WiFi control with a very sophisticated and diverse home automation system (SmartThings)? Not seeing alot obvious synergies there…maybe remove a little redundancy. Is Samsung heading down the rabbit-hole of only controlling their proprietary hardware some time in the future?
Seems the hand is writing on the Wall. Tnx for the link to Hubitat threads.