You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# NOTE: Expander zone faults are handled differently than
# regular messages. We don't include them in
# self._zones_faulted because they are not reported
# by the panel in it's rolling list of faults.
At least on my panel (Vista 20SE) the expander zones are still reported in the rolling messages. They are also reported as ready or faulted using the !EXP messages. Because they appear in the rolling message list, _clear_zones ends up placing them in the _zones_faulted array anyways.
The only concern this causes, is that any error in _clear_zones such as #50 will affect expander zones when it doesn't need to.
The text was updated successfully, but these errors were encountered:
zonetracking.py contains this note:
At least on my panel (Vista 20SE) the expander zones are still reported in the rolling messages. They are also reported as ready or faulted using the !EXP messages. Because they appear in the rolling message list, _clear_zones ends up placing them in the _zones_faulted array anyways.
The only concern this causes, is that any error in _clear_zones such as #50 will affect expander zones when it doesn't need to.
The text was updated successfully, but these errors were encountered: