Parent-Child App and Device Logging Changes

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

@bflorian

I would expect all the parent messages to be logged in the parent’s context

Just to clarify, the messages are being logged from the parents context, just that not 100% of the messages are showing up on live logging. What I had mentioned earlier was in reference to this piece of code I had written as a workaround before this fix was put into production.

Bug in Parent Child Devices

Yes I did but these are 2 different things. This is taking about sharing the State/AtomicState variables - which isn’t what I’m trying to do. I expect the State variable to be valid in the context of the Smartapp. I.e. I can access that variable anywhere in the SmartApp. In this case when the SmartApp is called the State variable always starts with null If you have a child parent just try this, in your SmartApp method called by the child try this: Device Handler (inside your refresh() command) callAppMethod(this) Also define this in your Device Handler to help see what’s going on def log(message) { log.trace message } SmartApp def callAppMethod(child) { child.log "BEFORE State: $state.testVar" if (state.testVar == null) { child.log "EMTPTY!!" state.te…

Essentially the parent would call the child device to log messages. So what my parent test app now does is:

log.trace "From childFunc"

child.log "From childFunc"

When this code is run 10 times, this should ideally print 10 messages from the child context and 10 messages from the parents context. My point was that I’m seeing 8 messages being dropped when the parent prints the log v/s all 10 showing up when the child prints the logs. The live logging is dropping messages.

Hope this clarifies it.