Make sure to wrote support every time something happens. Send a separate email for different problems… Like zigbee bulbs dropping off, rules corrupted, rules not firing would be three different emails.
Reference the chatter in the forums about the same issues.
It may seen a waste of time, but it really isn’t.
And you think that would help? Let me share this standard response:
“This request was closed and merged into request #…”
Their justification…
“I see you had another ticket that you submitted at the same time, I have merged your tickets for simplicity sake.”
After reasoning that the issues were NOT related…
“We usually like to merge tickets when someone writes in at the same time for different issues - general simplicity sake.”
So …
I’m hoping Tim is seeing when we post since he is part of this thread, and probably the others too. If so, he should know that the issue still exists.
I don’t know why, but everytime I lose a rule head, I visualize a giant worm roaming our data trying to decide whose rules to eat today. I guess I need the humor to keep me sane…
I just had the platform tell me my backdoor was open. Of course it isn’t. The device has lost it’s state.
The door showed open under notifications but no mention in the activity feed. Is this normal? I would think I would see the sensor change state in the feed too.
Pretty sure that’s the state of a different state, and that issue isn’t related to the loss of smart app state variables.
I wouldn’t necessarily jump to that conclusion. Device Handler Instances also have to use “a facility” to store the State of all their Attributes (such as contact: open/closed) and that persistent storage facility is likely the same as for SmartApp “state.*”; albeit with a few different layers in between and different object formats.
After posting I opened and closed the door to reset its state and the device showed the door closing in the activity log. I thought it should.
This seems to indicate that the state of this device spontaneously changed state on smartthings end since the door opening did not show in the activity log. If my sensor malfunctioned, I should have seen the door opening in the log.
Not sure this is the case. If anyone wants to help me try and troubleshoot this I need to collect more data. Please PM me so that we can have a dialogue.
I thought on the developer call engineering said they think they know what is happening… It was a post in another thread.
Just pointing that out so everyone is on the same page.
Thank you! Also this: