Skip to content
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

Open
lars-viklund opened this issue Aug 21, 2022 · 4 comments
Open

Problems with circuit current sensors #203

lars-viklund opened this issue Aug 21, 2022 · 4 comments
Labels
support Support and questions

Comments

@lars-viklund
Copy link

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

@lars-viklund lars-viklund added the support Support and questions label Aug 21, 2022
@olalid
Copy link
Collaborator

olalid commented Aug 21, 2022

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.
The current sensor for the charger seems to still work normally (although a bit slow sometimes recently).
I.e. sensor.xxxx_current -> state inCurrentT3, T4, T5.

In any case this would be an issue with the cloud rather than the Easee component, but I will forward the info to Easee.

@joelsvensson
Copy link

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.
Maybe I should use the T3,4,5 instead. Can anyone point me to a good reference describing/mapping those to L1/L2/L3 as I could not find any?

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

{
    "outputPhase": 30,
    "dynamicCircuitCurrentP1": 12.0,
    "dynamicCircuitCurrentP2": 15.0,
    "dynamicCircuitCurrentP3": 15.0,
    "latestPulse": "2022-08-29T19:19:56Z",
    "chargerFirmware": 300,
    "voltage": 236.475997924805,
    "inCurrentT2": 0.9850000143051147,
    "inCurrentT3": 12.079999923706055,
    "inCurrentT4": 12.067999839782715,
    "inCurrentT5": 12.04699993133545,
    "outputCurrent": 12.0,
    "inVoltageT2T3": 236.475997924805,
    "inVoltageT2T4": 233.593994140625,
    "inVoltageT2T5": 229.436004638672,
    "circuitTotalPhaseConductorCurrentL1": 0.00700000021606684,
    "circuitTotalPhaseConductorCurrentL2": 0.00899999961256981,
    "circuitTotalPhaseConductorCurrentL3": 0.00899999961256981,
}

@olalid
Copy link
Collaborator

olalid commented Aug 29, 2022

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.
Look at page 12 in https://easee.com/wp-content/uploads/2021/02/EN_Easee_HomeCharge_Guide.pdf
If you live in Sweden you will most likely have it connected according to "TN/TT 3-phase" picture.
Note that this is is the actual current used, not the setting for the dynamic circuit current limit.

That setting can instead be read from the dynamic circuit limit sensor and its attributes:
Screenshot 2022-08-29 at 22 36 09

@joelsvensson
Copy link

Thanks for a proper explanation 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Support and questions
Projects
None yet
Development

No branches or pull requests

3 participants