You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The DPL logs work quite well (that's my opinion), but there is (nearly) a complete lack of info about the DPL's state in the (1) live view and in (2) MQTT.
Describe the solution you'd like
A piece of software is required that keeps track of the current DPL state. Examples:
What thresholds are reached/crossed?
Is (Full) Solar-Passthrough active?
What is the target output for all inverters (and how much for each group (battery- vs. solar-powered))?
What is the current voltage used to decide on the thresholds being reached/crossed and where was the voltage measured?
What is the battery's charge cycle state (charging or discharging)?
All of these and more data points shall be collected in a new C++ class, and that class shall implement the respective websocket endpoint to create a live data card and publish the respective values to the MQTT broker.
Moreover, this shall shim the DPL config to allow overrides such as the mode switch, the upper limit, and everything else we currently allow to be changed through MQTT but causing persistence by writing the config. The live view (and MQTT broker) must then show which overrides are effective at what value.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The DPL logs work quite well (that's my opinion), but there is (nearly) a complete lack of info about the DPL's state in the (1) live view and in (2) MQTT.
Describe the solution you'd like
A piece of software is required that keeps track of the current DPL state. Examples:
All of these and more data points shall be collected in a new C++ class, and that class shall implement the respective websocket endpoint to create a live data card and publish the respective values to the MQTT broker.
Moreover, this shall shim the DPL config to allow overrides such as the mode switch, the upper limit, and everything else we currently allow to be changed through MQTT but causing persistence by writing the config. The live view (and MQTT broker) must then show which overrides are effective at what value.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: