-
Notifications
You must be signed in to change notification settings - Fork 38
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
Problems with circuit current sensors #203
Comments
Yes, I am seeing the same thing here, but I can not say that I look at those sensors regularly in any case. I think the would make most sense if you have more than one charger on a circuit which I do not have. In any case this would be an issue with the cloud rather than the Easee component, but I will forward the info to Easee. |
I have the same issue I'm using it to set the Dynamic Circuit Current so it caused me some issues when it's not updating. However it's not zero, just very small numbers and by the looks of it, it's not just a decimal change. Output from API request (filtered) - https://developer.easee.cloud/reference/get_api-chargers-id-state
|
T3 for instance means the third screw terminal on your Easee charger, so it depends on what is connected to that terminal, which in turn depends on what type of electric grid you have where you live. That setting can instead be read from the dynamic circuit limit sensor and its attributes: |
Thanks for a proper explanation 👍 |
Question
Since yesterday all my sensors for circuit current (circuitTotalPhaseConductorCurrentL1, etc.) report 0 even while charging. Is anyone else having the same issue? I know that Easee has been having some issues, but their status page claims that everything should be back to normal. Nothing related to the easee integrations in the logs.
What version of the integration are you using?
v0.9.44
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: