Upload a .Loxone file from Loxone Config and get a report with logic diagrams.
The file is never uploaded. The project contains an address, serial numbers and network addresses, so your browser processes it entirely. Nothing remains after you close the page. We only measure anonymous traffic (no cookies, no persistent ID and no project content — only counts, e.g. how many pages the report had).
Outputs nothing switches, logic without result, energy meters missing from Energy, missing notifications, valves without control.
Every program page as an inputs → blocks → outputs diagram, and a Loxone app preview (rooms, categories, favourites), also two versions side by side.
Two .Loxone files side by side: what was added, removed and changed — in page diagrams, objects and the XML. Change list to Markdown.
Input and output usage of every module, registers with addresses, virtual inputs and buses.
LoxAudit is a free online tool by IT2core that reads a Loxone Config project (file .Loxone) and shows what is wired wrong or not at all. It draws the signal routes of every program page, lists block parameters, the usage of Tree, Air, Relay and Extension modules and Modbus registers, and compares two project versions (for example before and after a change). It works offline in the browser, sends nothing and never changes the project.
No. The file is read directly in your browser and is never uploaded. Nothing remains after you close the page.
In Loxone Config via File → Save as, or in the Loxone Config projects folder in Documents. It is an XML file with the extension .Loxone.
The Energy Flow Monitor only shows consumers that have a meter block (Meter or Wallbox) included in the energy flow. An energy meter without a meter block is counted in the rest of the house consumption. LoxAudit lists such meters in its findings.
Outputs without input, blocks whose result leads nowhere, blocks without inputs, unused Modbus devices, energy meters missing from Energy, a storage meter measured in one direction only, missing notifications, valve actuators without room control, dew point without cooling lockout, I/O with default names, empty pages and a single user.
Yes. The App preview section draws favourites, rooms and categories as the user will see them. After loading a second file it compares two project versions side by side and highlights renamed or moved items. Values are illustrative only, the file contains no live state.
Yes. In the Compare two versions section, load a second file, or choose two files at once at the start (the older one is A). You will see added, removed and changed objects, new and removed connections, diagrams of changed pages with highlighted blocks (merged or A and B side by side) and the old and new value of every parameter — all in two columns A | B. The advanced XML mode shows both complete .Loxone files side by side with aligned lines: red = removed, green = added, yellow = changed attribute value, blue = a block Loxone Config only moved within the file. Objects are matched by UUID, so renaming or moving is not a deletion. The change list can be downloaded as Markdown.
No, it only reads. Findings are a list of questions to check in Loxone Config — without a live Miniserver it cannot confirm whether each behaviour is intended. If you want the project fixed or extended, IT2core can help.
Automatic wiring checks. Without a live Miniserver it cannot be confirmed whether each behaviour is intended — treat them as a list of questions.
How the user will see the project in the Loxone app: favourites, rooms and categories with the items that have “Use in visualisation” turned on. Names, rooms, categories and favourites come from the project; values and states are illustrative only.
What changed between this project (A) and another version (B): everything in two columns side by side — page diagrams, objects with the old and new value, and connections. In the advanced XML mode both complete files side by side: red = removed, green = added, yellow = changed value. Objects are matched by UUID, so renaming or moving to another page does not count as a deletion.
Program page from left to right: inputs → function blocks → outputs. Dashed line = inverted input, red border = dead end.
Green = used in the program, yellow = used with a default name, outline = free. Modules driven by a function block (Air blinds, wallbox, energy meters) have free I/O on purpose.
Address, function (3 = holding, 4 = input), polling period in seconds and scaling.