2024-11-01 13:32:16.536 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_AWAY was used from xiaomi_miot, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_AWAY instead, please report it to the author of the 'xiaomi_miot' custom integration
2024-11-01 13:32:16.545 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_HOME was used from xiaomi_miot, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_HOME instead, please report it to the author of the 'xiaomi_miot' custom integration
2024-11-01 13:32:16.556 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_ARMED_NIGHT was used from xiaomi_miot, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.ARMED_NIGHT instead, please report it to the author of the 'xiaomi_miot' custom integration
2024-11-01 13:32:16.566 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_DISARMED was used from xiaomi_miot, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.DISARMED instead, please report it to the author of the 'xiaomi_miot' custom integration
2024-11-01 13:32:16.577 WARNING (ImportExecutor_0) [homeassistant.const] STATE_ALARM_TRIGGERED was used from xiaomi_miot, this is a deprecated constant which will be removed in HA Core 2025.11. Use AlarmControlPanelState.TRIGGERED instead, please report it to the author of the 'xiaomi_miot' custom integration
There is a one-year deprecation period, and the constants will stop working from 2025.11
For users:
You can ignore this warning, the component works as usual. Any issue you think is related to this isn't: this is only a warning in your logs - nothing is broken.
On HA 2024.11:
Related developer blog: https://developers.home-assistant.io/blog/2024/10/22/new-alarm-state-property/
There is a one-year deprecation period, and the constants will stop working from 2025.11
For users:
You can ignore this warning, the component works as usual. Any issue you think is related to this isn't: this is only a warning in your logs - nothing is broken.