Sorry, there have been a lot of random issues with my handlers lately and I spent the entire day yesterday fighting with a driver so I was just a bit frustrated…
I guess it’s possible that my handler is causing the problem if ST recently changed anything related to the way setting defaults are handled which would explain why it wasn’t an issue in the past.
Did you try the steps I included in my last email?
Changing the settings from the IDE will mess things up and when you make a change to a setting in the mobile app there’s a delay before it syncs so after changing that value to something other than disabled you have to wait for it to sync before changing it back.
Param #3 and param #5 won’t show in the IDE because their not settings. The handler changes those behind the scenes depending on whether the auto on/off settings shown in the mobile app are set to disabled or a number. If you have live logging open you’ll be able to see whether or not it changed those parameters.
The problem is that the default on the device should be disabled and the handler won’t touch that param unless it changes so if it’s out of sync and you change it to enabled then it will be able to set it back to 0 when you change the setting back to disabled.
Being able to see the live logging results during inclusion if that doesn’t work would make it much easier for me to troubleshoot the problem…