Skip to content

Mqtt HA improvements - #76

Merged
BorisBrock merged 4 commits into
mainfrom
mqtt-ha-improvements
Aug 4, 2026
Merged

BorisBrock merged 4 commits into
mainfrom
mqtt-ha-improvements

Conversation

@BorisBrock

Copy link
Copy Markdown
Owner

No description provided.

@BorisBrock
BorisBrock merged commit 119ba58 into main Aug 4, 2026
3 checks passed
@BorisBrock
BorisBrock deleted the mqtt-ha-improvements branch August 4, 2026 09:04
sadilek added a commit to sadilek/HeidelBridge that referenced this pull request Aug 4, 2026
…rock#75, BorisBrock#76) into kupa5

Our three fixes are now upstream, so the fork no longer carries them. Boris made
two edits when merging: ClampToWallboxRange and WriteCurrentLimitRegister moved
from a file-local anonymous namespace to private members of HeidelbergWallbox,
and InitialChargingCurrentLimitA is now defined as MaxChargingCurrentA instead
of repeating 16.0f.

Conflicts resolved in favour of upstream throughout, except for two items that
stay fork-specific in MQTTManager.cpp:

- The Enable Charging unique_id keeps its underscore. Upstream still has
  "%control_enable_charging"; reverting ours would orphan the existing entity in
  Home Assistant and break the automation that references it by entity id.
- The diagnostic echo to {DeviceName}/internal/last_command is kept. It is not
  upstream and is deliberately not proposed, since it adds public topic surface.

Also adopted from upstream: the discovery publish retry (publish() can silently
return 0 when the TCP send buffer is full) and the Last Will plus
availability_topic on every entity, which together complement the retained
discovery from BorisBrock#73.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants