Nope, definitely not in the way we could with Classic.
Iām a little confused.
At the minute, everything works in classic.
If I rely on webcore for everything, surely everything will continue to work in the exact same way ?
And then itāll possibly become a problem in the future if I then do some sort of wipe/reload, at which point Iād need to install the app to re-pair the devices, at which point Iād find some of them wouldāt add this time around because they were only compatible with classic ?
Or have I got this completely wrong?
I havenāt had the chance to play yet, as Iām fairly busy with life in general. = p
While webCoRE can manage the state (armed/stay, armed/away, disarmed) of Smart Home Monitor (SHM) in the Classic app, it can not manage the state of SmartThings Home Monitor ISTHM) in the new app directly.
1 Like
Webcore also canāt control any of the new style of cloud to cloud integrations because they donāt show up as available devices in the groovy IDE. At least until WebCoRE is reworked to use the new Rules API. Which will happen, but itās a while away. Thereās proās and cons to every approach.
Currently I fire up the new app every couple weeks and see what works, what doesnāt and what needs to change to make NewApp workable for me.
Sorry that is not exactly true! I use some of the new integrations (Meross, Kasa and August Locks) and they work in webcore. I have also assisted a few users with other integrations.
Just make sure when adding available devices in webcore to look under select devices by capability and in group 1-3.
2 Likes
Lifx is cloud to cloud and i havenāt had any problems with my lifx bulbs As others have. Maybe because Iām using @whoismoses DtH.
I still activate my scenes created in LIFX app using webCoRE. and control the bulbs individually.
the Lifx integration in the new app also works in webcore
With the new app I cannot use my Goodbye or Iām back routines because there is no way to switch from mode to mode in an automation. Why is this feature disabled? The shotty presence detection makes this a must have feature. I donāt want goodbye to activate and have doors lock and lights turn off when I have people over and ST thinks my phone left. What gives?
1 Like
That was discussed aboveā¦ but this thread is getting rather huge!
The modes just arenāt ready yet. It is coming. Those of us whoāve chosen to jump into the new app early have come up with creative workarounds. The general usage right now is setting up virtual switches related to the modes and turning those on and off to control proper mode logic.
Itās definitely a workaround - again, early adopters. If thatās not what you want to mess with at this time, donāt switch.
4 Likes
@blake.arnold not sure if you are aware, in smart lighting, when setting up lights TOGGLE on/off associating with button push, sometimes need to push the button one more time for it to happen.
This is when the light is turn on or off by means other than the assigned button push (controlled in the app, automation etc.).
So my suggestion would be to check the status of controlled lights before sending commands, this way no need for another smart lighting rule to turn off.
2 Likes
@pauly, SmartLighting does record the toggle for itself. What should it do if you have set for 3 bulb to turn on/off toggle, and you have one on and two off at the time? Should it turn all on/turn all off, or toggle all of them, so you would have two on and one off?
I guess you would like to have what you set up Google all on or all off. It know what was the last command from the SmartApp, so next it toggles that.
This! Thatās what toggle means 
ā¦ that behaviour would make me happy 
But you set in the rule, turn all of them to one state, on or off. It will toggle that state. If you set two off and one on in the rule, then it will toggle those states.
Uhā¦ no. Iād be infuriated. I am quite happy to press it once to get them all the same then press again if the all-the-same wasnāt the correct state. What I find sometimes is slightly different. My button pressed once toggles them on to a subdued lighting, while a double press brings them to full brightness. A single press is also meant to turn them off. Sometimes when I have them on full bright, a single press just dims them to the subdued setting so I have to go via that before a final press turns them off. And sometimes it goes straight to off. Itās not a problem as long as the button is in the same room as the lights since I can see what itās done and act.
To me, on is on, off is off, toggle is toggle - flip state.
But yeah, for most people, I see the problematic outcome there. Single buttons just donāt work for me for this reason. After experimenting with them, I moved to 2 button units. A definite on and a definite off. Single buttons have been relegated to single function tasks.
3 Likes
Exactly what Iām doing right now, single push on, and held to turn off. Itās wasting one more button assignment
Probably thatās where the problem lies, i was setting 2 bulbs to be on, but Iād just need them to be off together, and toggled based on current state.
1 Like
Hopefully, this will be added soon.
Thatās where being allowed the same device in the IF and THEN would help. You could test all the bulbs for state, and if any of them are on turn them all off with that button press. If none are on then turn them on. (or whatever you were trying to do.) Just realised there is no ELSE in the rules!
6 Likes
The rules definitely need to be set up more like logic gates. For example when (the Garage door is open or the door is unlocked) and someone arrives -> ādo thisā
1 Like