Vaillant VR_71: add keepValveOperable (4) to Mc{1,2,3}Operation status enum - #621
Open
buliwyf42 wants to merge 2 commits into
Open
Vaillant VR_71: add keepValveOperable (4) to Mc{1,2,3}Operation status enum#621buliwyf42 wants to merge 2 commits into
buliwyf42 wants to merge 2 commits into
Conversation
The room controller writes status=4 in a short daily burst (~5 min) on otherwise-off mixer circuits — a valve anti-seize / keep-valve-operable maintenance run. The shared onoff type (0=off;1=on) doesn't cover it, so HA's enum sensor rejected the value. Add a dedicated Values_McStatus enum (off=0, on=1, keepValveOperable=4) for the three Mc status fields; pump stays onoff. Verified: tsp compile --warn-as-error passes, emitted CSV = 0=off;1=on;4=keepValveOperable, tsp format clean. Refs john30#620
buliwyf42
force-pushed
the
vaillant-vr71-mc-status-keepvalveoperable
branch
from
June 24, 2026 06:07
0936764 to
4afa0fe
Compare
Reported in john30#620 for a cooling-capable VR 71 (VRC 700, aroVAIR convectors): status 2 is sent while the circuit is cooling (flow target 10 C), versus 1 while heating (flow target 42.5-44 C). Without it, cooling installations keep hitting the original problem of this issue - a value outside the enum. Value 1 keeps the label 'on' on purpose: the field used the shared 'onoff' type before this branch, so renaming it to 'heating' would change the reported state on every existing installation.
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
1 participant
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.
What
Mc{1,2,3}Operation.status(b523 0200/0201/0202) is currently typedonoff(0=off;1=on). On real installs the controller also writesstatus = 4, which the sharedonofftype doesn't cover, so ebusd passes the raw value through and Home Assistant's enum sensor rejects every such update:This adds a dedicated
Values_McStatusenum (off=0, on=1, keepValveOperable=4) for the threestatusfields and leavespumpononoff.Why
4 = keepValveOperablePer the discussion in #620 across three independent VR_71 installs:
status=4appears in a short daily burst (~5 min) on otherwise-off circuits — a valve anti-seize / "keep valve operable" maintenance run. Observedstatusvalues are only0and4;1(on) was not seen. Name suggested by @Hoppur.Verification
tsp compile --warn-as-errorpasses.status,,UCH,0=off;1=on;4=keepValveOperable.tsp formatclean;pumpunchanged (onoff).Closes #620