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 way it is now, you have to wire a Victron Charger to the DTU in order to get its values for PV power production and to be able to use solar passtrough. So if you need to use two chargers (east/west, for example) you can't fully utilize the potential of openDTU-onbattery.
### Describe the solution you'd like
It would be beneficial if you could calculate the total PV power separately and have the DTU use this external value. This would instantly allow the use of multiple chargers and also chargers other than victron. And all this without more GPIOs, more CPU cycles. It would be scalable basically for free.
### Additional context
The preferred way I'd do this with my 100/20 Victrons would be to attach an ESP with KinDR007/Victron-MPPT-ve.direct-to-MQTT to each of the Victrons and either have Home Assistant calculate the value, or better, have openDTU-onbattery just read and add the values by itself.
The text was updated successfully, but these errors were encountered:
@iamdevnull Ich hab vor ein paar Wochen damit angefangen das feature MPPT Daten via MQTT zu implementieren. Dafür ist eine sehr umfangreiche anpassung des aktuellen MPPT codes nötig, das wird sich noch ein bisschen ziehen. Ein Datum oder eine Prognose kann ich dir nicht geben.
### Is your feature request related to a problem? Please describe.
The way it is now, you have to wire a Victron Charger to the DTU in order to get its values for PV power production and to be able to use solar passtrough. So if you need to use two chargers (east/west, for example) you can't fully utilize the potential of openDTU-onbattery.
### Describe the solution you'd like
It would be beneficial if you could calculate the total PV power separately and have the DTU use this external value. This would instantly allow the use of multiple chargers and also chargers other than victron. And all this without more GPIOs, more CPU cycles. It would be scalable basically for free.
### Additional context
The preferred way I'd do this with my 100/20 Victrons would be to attach an ESP with KinDR007/Victron-MPPT-ve.direct-to-MQTT to each of the Victrons and either have Home Assistant calculate the value, or better, have openDTU-onbattery just read and add the values by itself.
The text was updated successfully, but these errors were encountered: