Loxone ↔ KNX: incorrect initial state after Miniserver reboot

Configuration
, ,
1

After a Loxone Miniserver reboot, the state shown in Loxone may not match the real KNX state.

Reason:

  • The Miniserver does not know the state of the lamp before the reboot
  • By default, the Loxone channel is initialized as OFF
  • Meanwhile, the physical lamp may remain ON, since KNX works autonomously

Behavior:

  • After startup, Loxone shows the light as OFF
  • In reality, the light may be ON
  • After the first ON/OFF action (from Loxone or KNX)
    → a status telegram is sent from KNX
    → states become synchronized
  • The system then works correctly until the next reboot

Facts:

  • This is not a KNX bug
  • This is missing initial state synchronization in Loxone
  • Status telegrams are only sent on state change, not on startup

Conclusion:
Without explicit initialization or status request, Loxone guesses the state after reboot instead of knowing it.

Question:
What are the best practices to properly initialize KNX states in Loxone after Miniserver startup
(e.g. read requests, startup scenes, dedicated status group addresses)?

2

Hi :wave:!
I don’t see any relation to Home Assistant in this question. Maybe a dedicated Loxone Forum would yield better results for you.

3

Thats not true, that 100% depends on how you setup the status object.
Most if not all status object can be configured to resend the status at intervals or when passing thresholds.

That is down to you, like any other visu server you have to specify what KNX group you want to read at startup and that is possible in Loxone. By default its never, but you can specify at boot / cyclical.

As a last resort you can also tick remanence so after a reboot it will assume the state ( that does however makes an ass out of u and me :sweat_smile:)