-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request] DPL set limit should be published (MQTT, Api,...) #1232
Comments
Oh, okay, to the current limit is indeed published already, makes sense. However, the calculated household consumption, the effective (load-corrected) voltage, the expected AC output of each inverter, etc. should be published to MQTT. Essentially, I guess, these are the values that we are also missing in the non-existent DPL live view card. |
Thanks @spcqike indeed I can use it already. Do you know how I can overly directly in HomeAssistant both graphics? |
As I don’t use HA, no. No idea. I know how to do it with grafana and influx (: |
Has your issue been resolved @DanielR92 or do you think that it will be solved when the following issue has been implemented/resolved? #1431 |
@AndreasBoehm Good catch. Yes, this is obsoleted by #1431. And I assume that Daniel did indeed find the info he was interested in. I am going to close this issue. Daniel may re-open it if we missed something. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns. |
Is your feature request related to a problem? Please describe.
There is no problem. But publishing the limit would make a lot of sense here. So that other systems that are also connected via MQTT receive the current values. This also makes it possible to create logs and then understand more precisely how problems arise when they occur.
Describe the solution you'd like
The relevant information for each inverter should be stored via MQTT.
powerlimiter -> status -> ID -> values
Describe alternatives you've considered
Additional context
No response
The text was updated successfully, but these errors were encountered: