IRCv2 Setpoint Lockout after 17.x Update when using 3rd-party integration (KNX / Modbus)

30 views
Skip to first unread message

Waclaw Smirnov

unread,
May 30, 2026, 5:18:15 AM (6 days ago) May 30
to Loxone English

Hello everyone,

I would like to discuss a very frustrating behavior with the Intelligent Room Controller (IRCv2) block that appeared after the recent major update (version 17.0.3.31).

In my previous projects, I successfully built hybrid systems integrating Loxone with KNX room thermostats. Everything worked flawlessly. However, after the latest update, the logic of the IRCv2 block has completely changed regarding external setpoint inputs.

The Problem:

If you connect anything to the ϑt (Target temperature) input — whether it is a physical link from a KNX group address, a Modbus register, or even a basic Virtual Input — the IRCv2 block immediately locks out (greys out) the manual setpoint adjustment inside the official Loxone App. Local users lose the ability to tweak the temperature from their smartphones entirely.

It seems the block now treats any active connection to ϑt as a hard override from a "master system", completely overriding the local user interface.

What I have tried so far:

  1. I attempted to bypass this by clearing the ϑt input on the page and sending the setpoint via internal API commands using a Virtual HTTP Output (simulating how Home Assistant or the web interface changes values using the block's UUID), but the Miniserver seems to reject or ignore these commands now.

  2. I tried pulsing the values and resetting to defaults, but as long as the block detects an external data source aiming for the setpoint, it locks the app UI.

This is a critical issue for me because I have a large residential project fully equipped with KNX thermostats where everything was running perfectly until this firmware update. Now, I am stuck looking for a workaround, and as you can imagine, fixing this architectural change for the clients will likely be at my own expense.

Has anyone encountered this specific lockout behavior in version 17.x? Are there any clever workarounds or hidden logic tricks to update the IRCv2 setpoint from KNX/Modbus without losing smartphone app control?

Any ideas or insights would be highly appreciated!

Thanks in advance,

Jonathan Dixon

unread,
May 30, 2026, 7:08:15 AM (6 days ago) May 30
to Waclaw Smirnov, Loxone English
I've struggled with this kind of integration before, although I hadn't spotted the v17 change you mentioned.
What I have noticed in v17 is now any UI adjustment to the target temperature is now "permanent". Previously anyone tweaking the main thermostat control up or down would invoke a temporary override (for 8 hours or something?). Now it's permanently changing the setpoint, and presumably you need to use the awkward "Block Preset" feature to restore it to default at a prescribed time. (e.g., when vacating the house, a guest leaves, etc)
It seems like the change you mention is semi related.
(Completely OT but another UI change it is the very prominent "Enable Presence Detection" on Lighting controllers, which seem to keep getting turned off accidentally. or intentionally by guests, and I haven't yet figured out a way to automatically re-enable them when I reset the house to defaults)

Anyway, to your question, what I ended up doing was feeding the setpoint temperature selection from the KNX keypad through to a HTTP Virtual output, which loops back to hit the origin miniserver (127.0.0.1) on the API end point for adjusting the setpoint. So adjusting temperature up/down on the wall pad sets an override in a completely interchangeable with adjusting it on the app. [Or at least it was until the v17 change mentioned above]

For a temporary override the command is something like:
http://user:pass@miniserver/dev/sps/io/<IRC>/override/3/<duration>/<temp> 

Happy to share a worked example if this is of interest.

I haven't looked but there must be someway the API allows adjusting the permanent setpoint too.



--
You received this message because you are subscribed to the Google Groups "Loxone English" group.
To unsubscribe from this group and stop receiving emails from it, send an email to loxone-englis...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/loxone-english/66b8e28d-9a87-4377-a05a-8b9c8b5655b4n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages