The only thing keeping me on the Classic app is the Apple Watch support to trigger routines (which I primarily use to unlock doors).
Is this coming to the new app?
The only thing keeping me on the Classic app is the Apple Watch support to trigger routines (which I primarily use to unlock doors).
Is this coming to the new app?
are widgets for scenes available in the apple watch? I know they are in other iOS devices --> menu > settings > widget
Iâm sure Iâm not a typical user and while Iâve been trying to transition from custom device handlers unfortunately I have a few devices in the house that Iâm not sure apply the standard SmartThings Device Handlers.
A few device that I can think of that Iâm still using custom controllers are:
Loweâs Iris Keypad - Which is just a Centralight Zigbee keypad - I havenât scanned the built in device handlers but Iâm currently using custom code.
Enerwave ZWN-SC7: I have 3 of these installed in my house and I really like them but unfortunately Iâm not sure I know what device handler might work as it doesnât seem to work with the device handlers I tried this evening. I know from reading elsewhere that as a scene controller it is an older tech but unless I can find something else that could be used to do similar behaviors then Iâd like to figure out how to continue to use them after the sunset of the custom code requirement. (Iâm willing to change the SC7s to something else that doesnât require custom code but I canât think of any devices that fit the bill (wired to Main that has multiple buttons)
Iâve also run into the problems of not being able to change modes using automations and scenes. I understand the limitation of wanting to prevent infinite loops but unless something has changed I was unable to replicate a quieting down routine that only occurred in certain modes that then changed the house into a sleeping mode.
I can share my steps if necessary to demonstrate what seems like it should work.
What about voice notifications in the new app. I have amazon echos and am not.looking to.buy sonos speakers.
You might want to check out Echo Speaks. I am using it with WebCore to alert me to different things but I donât think it requires WebCore.
I also have no idea how presence works in the new app. I wrote a custom DTH for the Whistle Pet Tracker (link below) that I use for automations that would only run when the house is fully empty, e.g. arming motion sensors. My custom device doesnât even show in the new app, and as far as I know there are no developer docs that indicate what needs to be done.
This definitely isnât working right.
If I select any location modes in the if block then Iâm not able to select a scene with another location mode.
For example If - No Motion on various sensors, during a certain window of time, in say Home - Night Mode or Home - Evening
Then: Select Scene - Set location mode to Home - Sleeping, turn off various Lights
Unfortunately, all scenes that include a location mode change are greyed out and canât be selected.
I understand wanting to prevent infinite loops but that wouldnât happen in my example.
I just went in an turned off the home monitor and lock manager in Classic and set them up in the new app. Awaiting further instructions !
Checkout the default minimote device handler. Itâs been updated recently to work in the new app. You may be able to make the same changes to your DTH.
I played around with the newly added capabilities you guys added since the last time I checked. Good for my AirQuality DTH you added dustLevel, dustFineLevel, tvocLevel. Now my worry is that you guys wonât allow to have all these on a same Device.
Do you plan to have a UI that adapts to the capabilities we claim in the DTH rather than having tens of UI metadata?
That would be really great that if a device has:
capability âcapability.temperatureMeasurementâ
capability âcapability.airQualitySensorâ
capability âcapability.carbonDioxideMeasurementâ
capability âcapability.relativeHumidityMeasurementâ
capability âcapability.dustSensorâ
capability âcapability.tvocMeasurementâ
then 7 gauges show up (dustSensor would have 2âŚ) and rely on the related attributes.
If someone only declares 3 of them, the only 3 gauges show up.
How about FULL support for cameras that are officially supported (Arlo)?
I have been using new app couple of months. Itâs working and I like it more than Classic.
Iâm still missing couple of things that are working in Classic at the time but not in new app.
âThings I like in new appâ -list is much longer so I save my letters. Good job ST. Sometimes you fu** things up (for example removing sms from europe users just like that) but mostly things are good and you have done great job with a new app!)
Iâm using the new app more and more recently. Itâs a little slow to start for me, but the one thing that bugs me is the constant query box asking me to turn on Bluetooth every time it starts. I have no Bluetooth devices (and canât honestly see the point in an HA environment) so this constant reminder is an annoyance!
Other than this, yes, the new app works well for me. Looking forward to using it as my only interaction with SmartThings.
Thank you.
Have all the routines that I have set up in the classic app, been transferred to my new app? I canât see any. Iâve clicked on Automations and there didnât seem to be anything there.
And what about the smart apps tab, which shows all the other routines that are directly linked to a device?
John
WellâŚhave you transferred them?
âWe will be releasing our transition tool to small groups over the next few weeks. Keep an eye out for the banner in the SmartThings Classic app to get started.â
Just to clarify;
WebCoRE retains full functionality? (Apart from STHM equivalent control)
We can still add custom DTHs via the IDE, even if they donât work currently as expected, and will always be able to do so?
ActionTiles continues to be permanently supported?
Iâm not putting effort in to a platform that wonât ultimately satisfy my needs. As an average home automation enthusiast I donât have programming knowledge or massive technical understanding but want my things to serve the purpose they were bought for.
Much of my automation I have migrated to WebCoRE over the last 3 months or so, and I understand a new version of that is in the works. How does that effect the current version? When will that reach sunset? Will the new version contain equal functionality?
As a layman, this process has dragged on far too long and I still donât see my key concerns answered. My recommendation to others right now is to find another platform that has a more certain future, because Samsung doesnât communicate with its customers.
That said, the new app has moved forward considerably, and it is refreshing to see an increase in staff conversation within the forums. Letâs hope it stays this way.
Classic app
Device>smart app>automation attached to device
New app
Device> not a clue what automation is attached
Yes there are ways to see the automations but for ease of use automations attached to devices MUST be included on the device page somewhere
No! How do you do that? This doesnât seem like a straightforward process. Iâm old, not some sort of IT wizard. Most of the acronyms and terms on his forum mean nothing to me. What I do know is that the classic app was easy to understand and use. Okay there
were some âhiddenâ features that my daughter helped me out with when she visited, but she lives 300 miles away, so canât help transitioning.
You mention that the top devices are supported by ST Approved DTHâs
Do you have a list of Non approved devices and the handlers you are recommending to provide like for like functionality?
Also is proper EvoHome support coming? the old SmartApp works well in Classic. in New it shows so many more unrelated items in the DTH. I am sure someone could rewrite it but as this is one of the leading heating systems.
I found this topic yesterday. I did not read all posts from this topic but I remember that I red post which said that there should be some sort of banner in your classic app to do the migration. If you canât see banner then it is not available to you yetâŚ
I understand that you want to protect users from creating endless loops, but that is easily soluble by powering off the devices in question while you fix your logic or delete the automation. Therefore I would have thought that frustration of not being able to test the state of a device before instructing that device outweighs the harm done by an accidental loop. Your example workaround is something I have tried but doesnât really help in real life as setting a mode does not prevent devices being told to do something different while the mode is in effect - so the mode does not indicate current state of devices.
Could you perhaps consider an âAdvancedâ option for this that sends a pop-up warning of extreme danger to the uninitiated but allows confident programmers who know how to avoid loops to do what they want with the logic?