[Bug]: Loxone entities briefly change to `on` after Miniserver restart although real state is `off`

[RealSchlimbo]

Describe the bug

Title

Loxone entities briefly change to on after Miniserver restart although real state is off

Describe the bug

After restarting the Loxone Miniserver, multiple entities in Home Assistant briefly change state like this:

unavailable -> on -> off

within about 1 second.

The real outputs in Loxone remain OFF the whole time.

This short incorrect on state can trigger automations and switch real devices incorrectly.

Affected object example

Loxone object:

• Title: Wasserventil Bewässerung
• Type: EIBPush
• Q UUID: 1f02c585-039f-b9b8-06ff28f54c7ff073

Affected device types

This issue is not limited to a single type. I observed it on multiple Loxone entity types, including:

• Switch
• RoomControllerV2
• LightControllerV2

Expected behavior

After reconnect / Miniserver restart, the entity should return to the correct OFF state directly, for example:

unavailable -> off

or remain unavailable until the correct OFF state is known.

It should not briefly switch to on.

Actual behavior

After a Miniserver restart, Home Assistant shows:

unavailable -> on -> off

even though the real Loxone output remains OFF.

Manual verification of the correct UUID

I manually switched the Loxone object and verified that the affected UUID is definitely:

1f02c585-039f-b9b8-06ff28f54c7ff073

Manual test result:

• 1.0 = ON
• 0.0 = OFF

Example log:

2026-04-15 22:11:03.454 DEBUG ... {'1f02c585-039f-b9b8-06ff28f54c7ff073': 1.0}
2026-04-15 22:11:05.426 DEBUG ... {'1f02c585-039f-b9b8-06ff28f54c7ff073': 0.0}

Reconnect log

During a Miniserver restart I see:

2026-04-15 22:14:31.271 ERROR ... Miniserver out of service
2026-04-15 22:14:32.804 ERROR ... Service Unavailable (503)
2026-04-15 22:14:38.294 INFO  ... Successfully connected to Loxone Miniserver
2026-04-15 22:14:38.948 DEBUG ... '1f02c585-039f-b9b8-06ff28f54c7ff073': 0.0

What is interesting is:

• Home Assistant activity shows unavailable -> on -> off
• but in the reconnect debug log for the confirmed Q UUID I only see 0.0

So the temporary on state is not obvious from the raw reconnect state update of this UUID.

Home Assistant activity

For the affected entity, the Activity log shows:

• became unavailable
• turned on
• turned off

within about 1 second after Miniserver restart.

Impact

This causes automations to trigger incorrectly.
In my case, a real water valve was switched on because Home Assistant briefly reported the Loxone switch as on.

Configuration snippet from Loxone

<C Type="EIBPush" U="1f02c585-039f-b9ba-ffffdda48ec04889" Title="Wasserventil Bewässerung">
  <Co K="Q" U="1f02c585-039f-b9b8-06ff28f54c7ff073"/>
  <Co K="OutputAPI" U="1f02c585-039f-b9b9-07ff28f54c7ff073"/>
</C>

Logging configuration used

logger:
  default: warning
  logs:
    homeassistant: warning
    homeassistant.helpers: warning
    custom_components.loxone: debug
    custom_components.loxone.api: debug
    custom_components.loxone.pyloxone_api: debug

Firmware of your Miniserver

17.0.3.31

HomeAssistant install method

Home Assistant OS with Supervisor

Version of HomeAssistant

2026.4.2

Version of Pyloxone

0.9.12

Update pyloxone

yes

Log

Settings for the log can be found on the main page under the section Log Configuration

[JoDehli]

@RealSchlimbo first of all push buttons should be not used in automatons as the are stateless. This is also discussed in previous closed issues. Please use normal switches for automatons. I think the behavior is not good but it can not be changed for push buttons. I have never had problems with the other entities types.

[JoDehli]

@RealSchlimbo I can not change this behavior on the restart of the miniserver. I think for this you should always to something like this for your automations

trigger:
  - platform: state
    entity_id: switch.your_switch
    from: 'off' # Explicitly state what it changed FROM
    to: 'on'

this should prevent the accidental switching.

[JoDehli]

@RealSchlimbo https://github.com/JoDehli/PyLoxone#known-limitations

[RealSchlimbo]

@JoDehli Thanks for your reply.

I understand the limitation with push buttons, but in my case I am using the Loxone EIB push-button (EpB) block, which converts a physical push button into a defined switch output and is exposed in Home Assistant as a switch.

I also see the same behavior with other entity types, e.g. covers (Jalousie).

After a reconnect of the Miniserver, the cover briefly changes state (open/close) in Home Assistant and triggers automations, even though no real change happened.

I currently work around this using strict triggers with "from" and "to". This helps partly (e.g. filtering "unavailable -> on"), but it does not prevent the following "on -> off" transition from triggering automations.

Also Type RoomControllerV2 have the same behavior:

In general, it would be better if these incorrect intermediate states would not occur at all, since otherwise this needs to be handled in every automation.

[JoDehli]

@RealSchlimbo as I said I can not change this behaviour as I get no signals from homeassistant. You must find a differen workaround.

[JoDehli]

@RealSchlimbo I think I found the problem. And for the Switches I already have a solution. But need more time for the other types.

[JoDehli]

@RealSchlimbo can you try this branch
https://github.com/JoDehli/PyLoxone/tree/475-bug-loxone-entities-briefly-change-to-on-after-miniserver-restart-although-real-state-is-off

I tried to fix the state issue on start up or on reload.