They also said that only those users whose devices and custom apps all worked on the new app had gotten the migration notice. I’m an example that disproves that.
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.
There are lots of existing threads on Hubitat (some people are running both hubitat and smartthings), so just search the forum for it or start in the following section:
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.
That thread was moved to its very own section.
The thread is a pretty good read.
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.
I am able to do both of these in automations in the new app see screenshots below:
Leave Home (when both members are out)
When either member arrives home:
Hey thanks! I figured out that I hadn’t enabled location services on the second device.
Easily done, glad to hear you got it sorted
In my experience, presence sensor its a little messy and tricky in the Classic App, but when I tried it in the New App it was straight forward, just let app set it as a location member device and its ready roght away…in may case is working perfectly …
If you’re not shortsighted when you set it up!
In my experience, presence sensor in the new app has just stopped working after a time. In the classic app, it occasionally hiccups in that it is delayed (maybe once a month). However, in the new app, I had to turn off location services and turn them back on when it just flat stopped working. (This was on three different phones)
Eventually, I just gave up on the new app for presence and went back to the old. Also, NOT doing the creepy stalker Life 360.
Not sure if this is related or not, when I go into IDE and change a DTH for a devices, it does not change in the new app. I’ve migrated and no longer have the classic app to verify. This is happening on two devices only and has me pulling my hair out trying to figure out what’s going on. Any thoughts/recommendations is appreciated.
It gets a little tricky witb DTHs in NewApp. If a developer gas not created a custom presentation / VID in thier DTH, then the system is making a guess about what controls need to be present in the device’s display based on the capabilities defined in the DTH. So if you switched between devices that have no VID and the same capabilities, it displays the same stuff.
One trick is to set it to use a wildly different dth to one of the generic ones like ‘ZWave Device’ which we know doesn’t really show anything and back…
What device was it and what dth were you trying to switch to?
Thanks for the response. These are Netatmo devices, specifically the Wind Gauge and Outdoor module. Using the updated DTH from @cscheiene. The other devices seem to have updated (indoor/rain) but it’s just these two that are causing the trouble. I just changed it to a motion sensor and it changed, however switching back to the Wind module it doesn’t change in the app, still displays the motion sensor elements…
Update: I believe this is a “New App” issue as is displays appropriately in the “Classic App”
Then the device handler will need to be updated by the developer to display properly.
I guess you’ve not been using it for the last week with their transition to the “new” presence sensor in the new app. It left my automations pointing at a disconnected presence sensor.
If we are stuck with a device that is using a custom DTH, and the old API goes away, How will we be able to able to change it back to a stock DTH?
I’m trying but continue to get frustrated every step of the way. So much has changed and not for the better. I have been using this solution since the inception and over the years little discomforts do occur but nothing like the impact of the migration. Having to create many virtual switch’s to handle functions whether in SharpTools or other apps should not be. Need to to make all areas accessible via an API even your new SHM. Next time you get bright ideas of making major changes, which you call enhancements, discuss with the long time supporters and have community feedback like other companies do. I know it works as I sit on 3 panels and they listen and the products usually are better in the end. We shouldn’t loose functionality like EchoSpeaks or SharpTools unless you have a native replacement which I am in favor of. Work with those outside Dev teams as they have truly made this product a success.