Now I may get used to this, but one thing that is slowing me down when I want to quickly check what is on is that I find myself interpreting the power icon on each device tile rather than the icon for the device itself. Although I now know consciously that when a device is on it’s in colour, and off it’s grey, for some reason subconsciously I first look at the power icon which is always full black unless the device is actually disconnected or unavailable. Logically that makes sense but unless I can stop myself checking the power icon primarily it’s kind of hindering me. Also what is confusing is some of them just have a plain round circle while others have the little line going through the circle at the top. I keep finding myself judging the ones with the line to be on and the plain circles to be off. Unless I am the only one with this problem, can the intuitiveness of these indicators be reviewed?
It’s a poor visual of what the status of devices may be. I find myself having to study the icon, or list, room etc far too long to realize what the status is.
The old app actual is better visually. Hopefully this will be improved.
Well perhaps I should come up with a suggestion rather than just a complaint: How about if the power icon was always the same actual shape if it’s on, in black/bold if it’s on and grey (and maybe a different shape too) if it’s not. Then for anything the hub cannot see at the time because for instance it’s disconnected. just put a grey question mark. After all, it’s supposed to be saying “SmartThings does not know the state of this device”, so a question mark would really say that.
For me the power icon is grey for off and black for on.
I do feel that one combined status icon/button would be clearer. Greyed out device icon for the inactive state, coloured device icon for the active state, question mark or other distinct icon if the device is considered unavailable, suitable decoration if pressable.
Bug with Connect App on iOS.
Setting a SmartThings MultiPurpose Sensor to Garage Door operation in the new Connect app works as far as saying the setting is Garage Door, but doesn’t trigger an any events (open or closed).
If I use the Classic app after the Connect app it shows that I have no setting for Garage Door, even though I had set it in the Connect app. If I set it in the Classic App, then I receive that trigger events (open and close) and if I then check the setting in the Connect app if doesn’t show that it is set as a Garage Door.
why the new app vs classic one is so much slower ??
with every update seems to get even more dysfunctional. and recent graphics are seriously depressed .Bose music controller has been stripped from some functionality like volume , ability to see what is currently playing.
On the main page it doesn’t show when ( some ) devices are on , it remains grey , latest update stripped loads of vital functionality and nice graphical design. Is this for real ?
And i would like to ask again , WHY IS IT SO MUCH SLOWER THAN THAN CLASSIC ? is speed of refreshing and loading status going to remain the same , or this is work in progress ?
…No its not my phone making it slow … , I had app installed on several devices at home to test it.
It’s not your phone, trust me. The new app is slower than Classic. This is one of my biggest complaints.
Trying to move over to the new app, but I’m hoping someone can tell me if I am understanding it all correctly. Most everything from my old app has apparently copied itself into the new app except for the old automation routines. Those need to be re-entered into the new app as scenes, and can then be deleted from the old app. My newly created scenes in the new app also seem to have been copied back over to the old app as scenes. Am I correct to assume that I do not want to delete scenes or smartapps from the old app because it will delete from both? If I delete the old app entirely, (which I probably won’t) I’m assuming (hoping) that doesn’t delete any operations from the new app. Just hoping for a confirmation that my thinking is on track. Thanks
that is correct… do not delete them
just remember if you are using SHM in the classic app to remove the rules you set up in SHM first and then remove SHM before removing the classic app…
You may also wish to remove presence sensor in classic once you get it set up in the new app
9 posts were merged into an existing topic: Android app update 8 February 2020 - v1.7.43-22
Wha
t you don’
t like in tha
t
?
Things are not really copied between the apps, they are in the SmartThings cloud and are accessed by both the Classic and the new STSC apps.
Some functions, such as security and presence sensing, are completely separate. For those you should only use the function in one app.
@Brad_ST, @BroderickCarlin, I was just playing with that part of the code today for another DH and it is really not handling things the same way in the new app and the Classic app. This is the code from the DH:
section {
input("garageSensor", "enum", title: "Do you want to use this sensor on a garage door?", description: "Tap to set", options: ["Yes", "No"], defaultValue: "No", required: false, displayDuringSetup: false)
}
I can set it to No and Yes in the new app, it is not a problem, the setting is rendered correctly. But when the code executes, the selected value of Yes sets the garageDoor variable to 1 and No to 0. Meanwhile in the Classic app, it sets to Yes and No. And it should be Yes and No, as the variable defined as enum. The code expects the Yes and No further down.
if (garageSensor == "Yes")
results += garageEvent(xyzResults.z)
Other issue in the new app, that if a device’s setting has to be altered, the actual content is not kept, when clicked on. The entry field opens up completely empty, so if you mistyped something on an entry and you want to change just one character, then you need type from the beginning as it is not editable.
Thanks, I should have realized that, but wasn’t thinkin’.
Insufficient caffeine, I’m sure! 
9 posts were merged into an existing topic: Android app update 8 February 2020 - v1.7.43-22
13 posts were merged into an existing topic: Android app update 8 February 2020 - v1.7.43-22
A post was merged into an existing topic: iOS app update (February 9, 2020) - v1.6.43
From we are being told, yes. That can always change, but since the IDE is so integral right now, getting rid of that would be a significant and impactful change to deal with on top of dealing with the new app.
In the IDE for sure within the Type field when editing a device, or you can browse through what’s available to us via ST’s github site. Note though that not all are/will be available for many reasons, Halo smoke/CO detector DTH for example. It’s available in the drop down list, but not in github.
I would think so up until there’s a suitable replacement, or it gets rewritten to work more effectively with ST’s new developer/ment model.
If you have it installed, definitely (but there’s never a guarantee); for those who don’t you’ll need the Classic app to get it initially installed (for now). After that, the new app can easily use it. To find it, and/or install/setup another instance if your version isn’t a parent/child version, go to the hamburger menu and tap on SmartApps.
