Dsc tilt switch occasionally sending incorrect state in state_changed events

i have my DSC power series alarm connected to my home assistant install via envisalink 3, and everything works pretty well…but since starting over with the latest version of hass (i was on 0.70 and based on advice here i have been starting over due to it being pretty much impossible to update that big of a jump), my auto garage closure has been exhibiting some strange symptoms.

i have a tilt sensor on my garage door, and a z-wave outlet with relay connected to the garage door via bell wire to create a “smart” garage door without having to buy an entirely new opener. when the tilt sensor changes from off (closed) to on (open), i start a timer. at the end of the timer, i send a close signal to the garage door so that i can be reasonably sure i never leave my garage door open for longer than a few minutes. if the door is closed manually, any time the tilt sensor changes to off (closed), i send a cancel to the timer so that i’m not opening the garage rather than closing it.

the strange thing i’ve been seeing: occasionally (not all the time, but often enough that i’ve noticed it in my debug messages and verified it in the home assistant db) after i close the door manually (and the state changes to off / closed), home assistant then changes it back to on / open a few seconds later, then back to off / closed about 30 seconds after that. the frustrating part is that it’s not every time that the garage door is opened, it’s only occasionally. if it were happening every time, i’d have an easier time tracking it down myself…but it’s not. disclosure: i’m doing my automations in node red, if that matters, but i did look at the hass db and verify that the states are changing in home assistant itself. node red is just reacting to what hass is sending it.

it ends up not mattering much, because the first closure resets the timer once, the state change back to open just restarts a new timer, and then the last closure resets that new timer…so theoretically i shouldn’t run into any issues unless i set the timer fewer than about 30 seconds (which always seems to be the time period between the re-open / re-closure), which i wouldn’t do anyway because 30 seconds isn’t really long enough to make sure i’m out of the garage anyway. that being said, i’d obviously like to figure out what’s causing this and stop it to keep my system and automations as tightly defined and efficient as possible.

anyone have any ideas what might be causing this / how i can prevent it? is there some sort of polling going on that might be causing some sort of race condition that is resetting the state of the sensor, but not all the time?

anyone have any thoughts on this? is it possible the sensor has just gone bad? i tested the battery in the sensor, it’s still good…i will get a new sensor if i need to, but at the same time i don’t want to waste money on a new sensor if i don’t need one or that won’t fix the problem.

is there anyone out there?