-
Notifications
You must be signed in to change notification settings - Fork 9
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
Remaining charging time doesn't have a unit #150
Comments
There is a unit, it's minutes by default. Have a look at the left, under "Verlauf". The unit is displayed there as |
I see what you mean. |
Nope, that does not make any difference. I'll dig deeper. |
It turns out there are quite some bugs in the frontend when it comes to the |
As a workaround, you can add a template sensor to wrap around the sensor the integration gives you, or use an alternate frontend card. As soon as frontend solves this, we'll update this issue. Make sure to make the template sensor of another sensorclass than The integration will not change the sensorclass itself, because it is in fact a duration, and this is used in the HA backend in multiple ways. |
Thanks for the deep dive into the underlying reason. I think, I will just keep it as it is right now and wait until frontend solves this, since remembering the unit being |
I created a pop-up to quickly see some stats about my car.
You can see the state of charge (SoC), the car's range, and the remaining charging time. While the first two have units, the last one doesn't.
Opening the sensor details also shows that it doesn't have a unit:
I'm running version 1.6.4.
The text was updated successfully, but these errors were encountered: