Is there an XML <> UI crosswalk and dictionary?

[Tarun Nagpal]

The loxone config files use different terminology for almost every setting than what is presented in the UI, which of course makes file level investigation a pain in the ass.

Combined with the very esoteric HVAC settings, hidden connections, and the rest, make it even more opaque

A simple example - TDiff - it maps to acceptable deviation when you have a single temp setting; but in practice what I have seen is it seems to actually be the threshold value to switch modes and the system actually tolerates very little actual deviation from the set temp. Either some other parameter is confounding the picture, or the description is poorly written...

I am slowly putting together my own, but honestly if someone has already done the work somewhere, I would obviously rather skip that tedium and just get my house working properly. 

[Rob_in]

https://github.com/sarnau/Inside-The-Loxone-Miniserver

Anything there?

What are you trying to achieve?

Source code of the various smart home integrations (Home Assistant, ioBroker,etc) might also be useful.

Robin

[Tarun Nagpal]

I am using it for AI review of everything and monitoring.  It is life changing to be able to just say “hey why is the AC running?” and have it chase down the reason. 

Well I’ve started to assemble my own crosswalk. I’ll post it somewhere when it feels more complete…

[Simon Still]

Loxone's documentation and  'help'/info within config has always lagged behind features.  It's much better than it was but still confusing and difficult to track down info on lots of stuff.