On every Home Assistant restart, Irrigation Unlimited performs synchronization slightly before my Zigbee2MQTT switch entities have obtained their initial state.
Example:
01:50:53 — IU logs expected: off, found: unknown
01:50:56 — switch becomes off
Both configured switch entities behave identically.
It appears that unknown/unavailable during HA startup is being treated as a genuine state mismatch. Would it be appropriate for initial synchronization to defer checking entities in unknown/unavailable state until they have obtained a valid state?
Version of the custom_component
2025.12.0
Configuration
Log
This error originated from a custom integration.
Logger: custom_components.irrigation_unlimited
Source: custom_components/irrigation_unlimited/irrigation_unlimited.py:5843
Integration: Irrigation Unlimited (documentation, issues)
First occurred: 1:50:53 AM (2 occurrences)
Last logged: 1:50:53 AM
SYNCHRONISATION [2026-08-06 01:50:53] Switch does not match current state: expected: off, found: unknown, switch: switch.sonoff_duo_1
SYNCHRONISATION [2026-08-06 01:50:53] Switch does not match current state: expected: off, found: unknown, switch: switch.sonoff_duo_2
State history of switch
On every Home Assistant restart, Irrigation Unlimited performs synchronization slightly before my Zigbee2MQTT switch entities have obtained their initial state.
Example:
01:50:53— IU logs expected:off, found:unknown01:50:56— switch becomesoffBoth configured switch entities behave identically.
It appears that
unknown/unavailableduring HA startup is being treated as a genuine state mismatch. Would it be appropriate for initial synchronization to defer checking entities inunknown/unavailablestate until they have obtained a valid state?Version of the custom_component
2025.12.0
Configuration
Log
State history of switch