-
Notifications
You must be signed in to change notification settings - Fork 100
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
Number of phases in sensor.charger_power is 2 #887
Comments
I use the attribute charger_phases of sensor.charger_power te recalculate the power in W. But with the last update the number of phases is now 2 which is not correct. The app shows 3 in my example case. |
You haven't given much information on the issue, without that it is impossible for us to try and debug or fix. Please add as much details as possible to assist. |
Charger_pahses: 2 is wrong. it should be 3 as before. |
Ok you say "it's wrong" but what are the logs reporting? The extension can only work with the information the API call gets back, if the API value says 2 then unless it's always off by one for all phases there really isn't anything that can be done. I only have a 3 pin charger at home, so I can't even try and replicate your issue |
To enable debug logs in Home Assistant & click Enable debug logging |
Hi, I wanted to send you the log now, but if I look into the log, I mainly see only my yaml code and some statements from other APIs but not from the Tesla API. How do I get the log from the Tesla API only? As I also use the actual charge power with the phases and amps, I need current data and set therefore the polling interval to 10 seconds:
However, the date is very ofte outdated and I get the correct current data only when I press "forca data update". What can I do to get current data every 10 seconds? |
Charger_phase 1 means single phase |
Version of the custom_component
Configuration
Add your logs here.
Describe the bug
A clear and concise description of what the bug is.
Debug log
The text was updated successfully, but these errors were encountered: