Fix Flexpartner.Energy connect and rename from Energy Speedometer#1213
Open
gskjold wants to merge 2 commits into
Open
Fix Flexpartner.Energy connect and rename from Energy Speedometer#1213gskjold wants to merge 2 commits into
gskjold wants to merge 2 commits into
Conversation
The energySpeedometerConfig literal only initialized 9 of MqttConfig's 15 fields, so timeout and keepalive defaulted to 0. setTimeout(0) made the MQTT client abort the CONNECT before the TLS+MQTT handshake could complete, so the connector never connected despite valid host, credentials and TLS. Initialize the remaining fields (timeout 1000ms, keepalive 60s) to match customMqttConfig, with per-field comments so future MqttConfig additions are visible here too. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
d0703e4 to
a8bb08f
Compare
…nslated) Hardcode the "Flexpartner.Energy" brand name in the services tile and the configuration page, bypassing the translation lookup so no language can override it, and remove the conf.cloud.es / status.services.mqtt_es entries from the Localazy source. Rebuilt ui/dist accordingly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
a8bb08f to
12bba95
Compare
🔧 PR Build ArtifactsVersion: All environments built successfully. Download the zip files:
|
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
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
Two related changes to the optional ESP32 cloud connector previously called "Energy Speedometer".
1. Fix the connect failure
energySpeedometerConfigonly initialized 9 ofMqttConfig's 15 fields, leavingtimeoutandkeepaliveat0.mqtt.setTimeout(0)aborted the CONNECT before the TLS+MQTT handshake could finish, so the connector never connected — despite a valid host, credentials, and TLS endpoint. The remaining fields are now initialized (timeout 1000ms, keepalive 60s) to matchcustomMqttConfig, with per-field comments so futureMqttConfigadditions don't silently fall off this literal again.2. Rename to Flexpartner.Energy (fixed brand)
The user-facing label is renamed to Flexpartner.Energy and hardcoded in the services tile and configuration page, bypassing the translation lookup so no language can override the brand name. The
conf.cloud.esandstatus.services.mqtt_esentries are removed from the Localazy source, andui/distis rebuilt.Scope is intentionally limited to display name + connect fix — internal code identifiers, build flags (
ENERGY_SPEEDOMETER_*), and the broker host are unchanged.Verification
ui/distrebuilt; fresh bundle contains only "Flexpartner.Energy".Follow-up (not in this PR)
CLAUDE.md. Already-translatedconf.cloud.es/status.services.mqtt_esvalues become unused; purge separately via a one-timedeprecateMissingtemp config if desired.*.sandtime.energy) expired 2026-03-22; harmless today because the connector setssetCaVerification(false), but worth renewing server-side.🤖 Generated with Claude Code