State variable not storing object

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

@whoismoses

I recently turned on of my apps in the a parent / child app versus installing it multiple times. I use state just a few time to store values, I try to only use it when required. Is “state” sandbox per child app or is it shared?

Super complex topic which no one from ST cared to verify the intended behavior. I’ve posted lots of results on this.

1. For parent child apps, state variable isn’t shared between them.
2. When a child calls a parent function, the parent’s state variable isn’t a global context so it can’t be accessed from the function in the context of a child call. However the atomicState variable is a global context within the parent and be accessed by the parent function in the context of a child calling it.

Bug in Parent Child Devices

I’m developing a Service Manager SmartApp. The Device calls a function in the Service Manager via parent.XXX() call. The Service Manager then executes some functions. However it now needs to defer the final action so it saves the state in state.queuedActions state.queuedActions << [[function: this.&updateCameraImage, parameter: "", child: child]] runIn(10, executeQueuedActions) // If was successful then give it time to complete When executeQueuedActions runs later: log.trace "Called execute queued actions: $state.queuedActions" I see: Called execute queued actions: [] It isnt’ saving the context of the call. I think the original call is in the context of the Device Handler where as the runIn end up running the context of the Service Manager SmartApp and doesn’t save t…