Add register mapper for Regulus IR14 firmware 1.0.11.0 - #6
Merged
Conversation
This IR14 controller (FW 1.0.11.0; RegulusBOX / TECO Foxtrot, local web login uzivatel/uzivatel) uses a PLC register bank with zero overlap against every shipped mapper (0/54 vs 12_04_10, 14_1_0_5_0, 14_1_0_10_0), so all entities read "unknown" without a dedicated table. Adds ir_version "14_1_0_11_0" with 32 keys, all validated live on a running Home Assistant and cross-checked against the Regulus IR Client app: outdoor / HP inlet-outlet / DHW / zone heating-water / room / desired / AKU-top temperatures, the full heat-pump statistics block (running & idle time, overall + hot-water totals/today/yesterday hours, minutes and starts), and zone 1 state. Remaining keys (AKU & solar — not installed on this unit — plus some dashboard status bits) to follow. Registers were derived from the controller's own XSL (each labelled field binds to a positional INPUT[n] -> n-th register in the page XML) and confirmed by value against the app, including counter drift over time. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Owner
|
thanks for PR - in release 2.0.3 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a register mapper for Regulus IR 14, firmware 1.0.11.0 (
ir_version: 14_1_0_11_0).This controller's PLC register bank does not overlap any existing mapper — 0/54 register addresses in common with
12_04_10,14_1_0_5_0, or14_1_0_10_0— so without a dedicated table every entity readsunknown. (Verified by comparing each shipped mapper's registers against a live register dump from the controller.)Changes
custom_components/regulus/mapper/registry_mapper_ir14_1_0_11_0.py— newREGISTRY_MAPPER(32 keys)custom_components/regulus/const.py— register the mapper inREGISTRY_MAPPERSand add14_1_0_11_0toIR_VERSION_OPTIONSNo changes to integration logic.
Coverage
32 keys, all validated live on a running Home Assistant against the controller and the Regulus IR Client app:
Remaining keys (AKU tank detail and solar — not installed on this unit — plus a few dashboard status bits and zone required-temps) will follow in subsequent commits.
How the registers were derived
The controller's web UI XSL binds each labelled field to a positional
INPUT[n], which corresponds to the n-th register in the page XML. Addresses were extracted from that geometry and cross-checked against the IR Client app's labelled readings — e.g. the statistics counters were matched by value and confirmed by their drift over time (a counter reading 44→53 min between two samples nails the mapping).Tested on the live controller: every mapped key decodes correct, sane, updating values.
🤖 Generated with Claude Code