@Jim I’m starting a new thread on this topic, in another thread Bug in Parent Child Devices you had mentioned that it’s discouraged to use
atomicState in the same app. One should use either state or atomicState throughout the app.
I had mentioned that are some inconsistencies that would need to resolved before that would be practical to enforce and you had requested an example. So to follow up on my promise.
I can/have built apps that only atomicState due to nature of the variables involved. However I cannot avoid the use of state, when the smartApp calls
createAccessToken, ST stores the token in the state variable under
This is probably the only and big hurdle that I can think of which would prevent me from not mixing state and atomicState in a single app.