iOS or Android? On iOS mine hasn’t done that the past 2 versions.
1 Like
And here I was thinking it was me 
1 Like
Android 10
1 Like
Just wondering if this omission is just in the New App or if it was present in classic.
There are no +/- buttons on the keypad when entering a smart lighting offset on Android…
at least you have the “dot” that I am missing in temperature editors.
Hey smartthings folks, looks like you really have problems with editors keypad types in a lot of cases now.
when is this going to be addressed seriously?
1 Like
No I’ll second it - it’s consistently not working, latest version of NewApp on Android. It wont hold the home screen layout through reboot, or update and sometimes even just shutdown and restart of the app.
Particularly egregious when you have 140 devices and the one switch you keep putting on the top defaults to the bottom of the list - so you’re scrolling through 8 screens of stuff you hid an hour ago. 
Oh and that Damned Samsung Smart TV UI ALWAYS comes back to the top when you hid it 1000 times.
Right now I’m classic first so it’s not a horrible problem for me - but If I were in newApp, I’d be griping about it all the time.
5 Likes
It appears that everything is working for me except my Iris keypad; and I have over 200 devices.
The app is still way too slow to load, but some of the new features and potential new features are nice.
2 Likes
Can duplicate that issue on iOS
Tagging @blake.arnold
2 Likes
When entering temperatures I see a different keyboard…
The “.-” key enters a “-” sign if ts the first character you enter, otherwise it enters a “.”
Quite clever actually - if it was consistent.
FYI - Smartthings Buttons don’t run locally if configured in new app versus “Smart Lighting” Smartapp
There was a problem the Smartthings network last night which pointed out a issue with local vs cloud operations.
I have five Smartthings Buttons that I use to turn on/off lights and dim them.
When I primarily used the Classic app, the actions were setup in the “Smart Lighting” Smartapp and worked locally (stored in the Hub) even if my internet connection was down.
When I started using the new ST app, I used it to program the functions (Pushed/ Pushed Twice/ Held)
but they did not work last night when the Smartthings network was having problems SmartThings Status.
So I changed the buttons back to the Smart Lighting Smartapp.
This isn’t really a Classic vs New app situation, but something to keep in mind if you are concerned about local execution.
I hope the Smart Lighting app never gets removed!
1 Like
I hope the automation creator runs locally eventually 
6 Likes
I’m sure memory size becomes an issue and I think the V3 has less than the V2.
Does anyone know how to determine how much memory is in use on your own hub?
but can you validate 18.5 for instance ?
in my case 18.0 keeps the Done button working but 18.5 disables the Done button
Not at all. If it can be done with classic (a vm3 hub is perfectly capable of running local using SmartLighting, proving it is possible) so it can be done, period. Instead I suspect they’re focusing on functions first rather than ‘where the function runs’ its DevOps and iterative development… they’re taking bite sized chunks and that’s a lot of chunks at once (whether or not we think the changes they are accepting are the right ones - like local execution, or variables in Rules API, VS. The icons in the home screen - that’s a completely different story…)
2 Likes
Damn, the status page’s email notification was not working again for me. This is not the first time during the past years. What’s is going on with that email notification service?
@blake.arnold, @jody.albritton, @Brad_ST - Could you please ask the right person to check out what is going with the email notifications there? Thanks!
I disagree. Some people have dozens of devices and if they are heavy users of automation routines (like the Smart lighting app, etc) memory size is bound to come into play. That is only logical.
Also processing power and speed of the hub - if devices are constantly being monitored for state changes (open, close, motion, etc), there has to be an impact on response time.
I was a programmer/analyst for 29 years and still program microcontrollers as a hobby - memory and speed are always limited…
2 Likes
I believe the . appears if the field is a decimal numeric value rather than integer. I noticed it with the ST Anything Child Temperature Device handler…I tweaked the device handler to change the type from Integer to decimal…and then the . showed up on the keypad in the app
I didn’t say memory won’t be a constant ever. Just that’s likely not it now if it already works. Like for like. Very subtle but important difference. Now if we wa t to talk Hubitats definition of local. (cloud disconnected) That’s different entirely. St couldn’t do that on the v3 hardware. Heck, Hubitat is having trouble themselves on thier hardware. 
I am not a programmer but it’s my understanding that ST is going to use something written in RUST running on the V3 & V2 hub to execute automations locally. They have stated that Groovy isn’t really conducive to the smart home environment. The new rules.api is the start of this local execution initiative.
2 Likes