I am using lum from @rboy and in new app it works great except if I set a code for a particular day only it never works.
Is anyone else using @RBoy lum on new st app and seeing this issue?
The wifi outlet one just needs the VID in the meta data.
I received the email notification to migrate, but the current version of the app is not voice navigable. (It is a major step back from two versions ago.)
Can I ignore the email? Or will I be forcibly migrated to an unusable system?
Will send you a DM to discuss. Wouldnât have expected you to get that emailâŚit only went out to users with fairly basic setups.
As mentioned before, thereâs no hard deadline that is set at this point, so you arenât being forced to move to the new app if thereâs something specifically preventing you from it at this time.
Thanks @DavinD. Can you elaborate a bit more. What is VID? Should I add this as capability to metadata in DTH? Thanks again.
In new app i can´t see galaxy watch (no location âmyStatusâ and no device âgalaxy watchâ). In âSamsung IDEâ, there is both âmyStatusâ and âGalaxy Watchâ
Do you plan to incorporate the galaxy watch in the new application?
It is very interesting to use the galaxy watch for automations
Greetings
In this post Original & Aqara Xiaomi Zigbee Sensors (contact, temp, motion, button, outlet, leak, etc) that âSmartThings has not yet published developer documentation on how to do this (use the Handler Device), so the best solution is to use the SmartThings âClassicâ mobile app for nowâ.
Seriously?
If that problem exists, I find it complicated to move on to the new application of smartthings, although it is true that I have three Xiaomi devices and they work correctly in the new application.
Greetings.
I recently started seeing server errors in the shm running on the new st app.
It shows up when the app first launches.
Is anyone else seeing this?
yes I had same issue. it forced me to log off. when I logged back in, my location was gone and I had to add location again by accepting an invitation. when I added the location, the smart thingsHomemonitor was deleted. Also, none of the scenes are working.
Yes, Iâve see that quite a lot over the few days. The ârefreshâ button usually fixes things. Iâve seen quite a few other reports of it.
Whatâs the trick for Rachio? I am still seeing âCanât connect to deviceâ in the Connect app.
may have to add Rachio again from the new app to get the ST Schema version.
All the time⌠refresh helps, but Iâm not happy wit this kind of âsecurityâ
Ugh, thanks. So annoying when you have to remove and re-add devices.
So deleting the prior devices and integration then re-adding in the Connect app simply sets each Rachio Zone up as a simple on/off switch rather than valves with the functionality and reporting of the prior Classic official integration.
Am I missing something?
Nope, for better or worse, thatâs what mine is to.
Sigh. Another step backwards.
Thanks
Iâve been nearly exclusively on the new STSC app since sometime in December.
After living with the latest update for a couple of weeks I have to say itâs got some new annoyances.
- When you tap on a device the controls such as on/off and dim level take a couple of seconds to load. Iâve got a 100Mbps fiber connection to the internet with low latency.
- There seems to be no caching of the controls. Accessing the same device repeatedly still requires a couple of seconds before the controls are usable.
- The order of items on the deviceâs page, for dimmers at least, is annoying. There are controls for timer and timed power on and off which are seldom used. On my phone, these push the dim level control partially off the screen. So the process of changing from level requires first waiting for controls to load, then scrolling down to make the slider accessible.
Iâve been trying to play with the new app but a major pet peeve is how heavily it relies on âroomsâ for organization. I spend an hour yesterday putting all my devices in rooms via the IDE. The classic app reflects that. The new app, theyâre all all showing âNo room assignedâ.
Even removing and reinstalling the new app doesnât fix it.