I’d like to get rid of a notification being send for the first event after startup. This is because I reboot my server once a day (late at night) and I always get a “closed” event sent when the state is detected.
I don’t set the initial state on the accessory when it is created because I don’t want to freeze the home bridge startup process, and want to asynchronously set the state via polling to be a nice homebridge citizen.
I was think to initialize to “closed” and then have polling code reset. I kind don’t like that because if poll g code was failing for some reason then HomeKit would think the door is not n the wrong state for an extended period of time and I don’t like to give false state reports. Just seems wrong. I’d rather have HomeKit keep the device in an “updating...” state.
I’d like to get rid of a notification being send for the first event after startup. This is because I reboot my server once a day (late at night) and I always get a “closed” event sent when the state is detected.
I don’t set the initial state on the accessory when it is created because I don’t want to freeze the home bridge startup process, and want to asynchronously set the state via polling to be a nice homebridge citizen.
I was think to initialize to “closed” and then have polling code reset. I kind don’t like that because if poll g code was failing for some reason then HomeKit would think the door is not n the wrong state for an extended period of time and I don’t like to give false state reports. Just seems wrong. I’d rather have HomeKit keep the device in an “updating...” state.
If someone has advice that would be great.