simpleAPI: Consumer-Support und list_components-Übersicht - #3981
Open
seaspotter wants to merge 5 commits into
Open
seaspotter wants to merge 5 commits into
seaspotter wants to merge 5 commits into
Conversation
Consumers were entirely missing from simpleAPI - added get_consumer_all plus 13 individual parameters, mirroring the existing battery/pv/counter pattern. Also added GET ?list_components=all, returning all configured IDs per type in one call, built on the existing MQTT wildcard-scan mechanism (previously only used internally for auto-ID resolution).
Collaborator
Author
|
Ergänzungen fürs Wiki: |
Mirrors the existing instant_charging_limit/amount/soc implementation (HTTP + MQTT) but targets chargemode.pv_charging.limit instead of chargemode.instant_charging.limit, exposing the stop-limit mechanism PvCharging already uses internally but was previously unreachable via simpleAPI.
seaspotter
force-pushed
the
simpleapi-add-consumers-and-discovery
branch
from
September 23, 2026 05:49
d80f741 to
3c8fa82
Compare
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.
get_consumer_all+ 13 einzelne Feld-Getter; MQTT-Daemon:openWB/consumer/#wird jetzt wie bat/pv/chargepoint/counter unteropenWB/simpleAPI/consumer/...republiziert)list_components-Endpunkt (?list_components=all) in der HTTP-Schnittstelle, der alle konfigurierten Komponenten-IDs gruppiert nach Typ zurückgibtpv_charging_limit/pv_charging_amount/pv_charging_soc(HTTP + MQTT), analog zu den bestehendeninstant_charging_limit/instant_charging_amount/instant_charging_soc, aber fürchargemode.pv_charging.limitstattchargemode.instant_charging.limit- schließt die in FeatureRequest pv_charging_limit Parameter in der SimpleAPI verfügbar machen #3995 gemeldete Lücke (Stopp-Limit für PV-Laden war intern inPvChargingbereits vorhanden, aber über simpleAPI nicht erreichbar)state_str,fault_str,rfid,chargemode) kamen sowohl in der HTTP-Schnittstelle als auch im MQTT-Daemon doppelt in Anführungszeichen zurück, da openWB auch reine Strings per JSON kodiert veröffentlicht und beide Stellen den Rohwert ohne Dekodierung übernahmen - an beiden Stellen behobengetChargepointAll()schlug bei fehlendem, nie zuvor gesetztemmanual_lock-Topic still fehl (Rückgabe[]), da dieser eine MQTT-Read nicht wie alle anderen im try/catch abgesichert war