Your automation’s State Trigger is configured to trigger only when any of the listed binary_sensors change state from off to on which means when the door opens. When a door closes (state-change from on to off) the State Trigger ignores it.
I believe that will trigger for state-changes to/from unavailable. Given the automation’s current design, it’ll erroneously report “Closed” when there’s a state-change from on to unavailable.
If imv8n wants the automation to announce all of the door’s possible states, including if it becomes unavailable, that’s the recommended way to do it.
There may also be a seemingly odd announcement if the state-change is from unavailable to on or off. The announcement will report the door’s new state even if the door never physically moved to get to that state.
This is how I had it originally however the zigbee door sensors, I assume would briefly lose connectivtiy at some point and in the middle of the night I would get announcements that a door was closed. My assumpition is that the sensor went from unavailabale to closed.