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.
Would be nice if the chargers overview would also indicate if the evcc implementation supports built-in meter reading. I should become a filter like 1p3p or RFID. https://docs.evcc.io/docs/devices/chargers
Some chargers come in different variants (with or without meter), but this is something the user has to take care of when buying. From our side, I think it's sufficient to indicate that we can read it if it exists.
Describe the solution you'd like
Manually go through all the templates and add a meter tag to the devices capabilities.
Additional context
Helpful for making buying decisions based on supported feature set.
The text was updated successfully, but these errors were encountered:
Some chargers come in different variants (with or without meter), but this is something the user has to take care of when buying. From our side, I think it's sufficient to indicate that we can read it if it exists.
Ich glaub weiterhin dass das ne gute Idee ist. Aktuell muss der User in den Code gucken um rauszufinden ob wir das unterstützen. Die Info hilft bei der Kaufentscheidung.
Is your feature request related to a problem? Please describe.
Would be nice if the chargers overview would also indicate if the evcc implementation supports built-in meter reading. I should become a filter like 1p3p or RFID.
https://docs.evcc.io/docs/devices/chargers
Some chargers come in different variants (with or without meter), but this is something the user has to take care of when buying. From our side, I think it's sufficient to indicate that we can read it if it exists.
Describe the solution you'd like
Manually go through all the templates and add a
meter
tag to the devicescapabilities
.Additional context
Helpful for making buying decisions based on supported feature set.
The text was updated successfully, but these errors were encountered: