home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.16k stars 30.2k forks source link

OVO energy no longer connecting via integration #115905

Closed jakeherp closed 5 months ago

jakeherp commented 5 months ago

The problem

I have been using the OVO energy integration for close to a year and up until a few days ago it was working fine. However, since the beginning of this week the integration cannot connect to OVO energy anymore. I have removed the integration and tried to set it up again, but I keep getting the Failed to connect error.

I cannot see any logs that would explain this issue further.

What version of Home Assistant Core has the issue?

core-2024.4.3

What was the last working version of Home Assistant Core?

core-2024.4.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ovo_energy

Link to integration documentation on our website

https://www.home-assistant.io/integrations/ovo_energy

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 5 months ago

Hey there @timmo001, mind taking a look at this issue as it has been labeled with an integration (ovo_energy) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `ovo_energy` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign ovo_energy` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


ovo_energy documentation ovo_energy source (message by IssueLinks)

timmo001 commented 5 months ago

Looks like the APIs may have changed image

jakeherp commented 5 months ago

Looks like the APIs may have changed

image

Are the APIs documented anywhere or are they internal and had to be reverse engineered? I was looking for API docs but couldn't find anything.

timmo001 commented 5 months ago

Completly reverse engineered. Looks like the authentication has been changed to use oauth tokens now.

I will update the ovoenergy package to suit

timmo001 commented 5 months ago

Changes made to package. Will release shortly and update the integration

Astro-Pete commented 5 months ago

Is this V2.0.0 released in HA yet? I have the same issue and the OVO integration does not seem to be updated yet.

timmo001 commented 5 months ago

This is in the beta and will be released tomorrow

Astro-Pete commented 5 months ago

This is in the beta and will be released tomorrow

Perfect. Thx for the update.

jakeherp commented 5 months ago

@timmo001 have you been able to get the entities to come through in HA after the auth change? I've not had any luck, keep getting this in HA:

Screenshot 2024-05-02 at 09 47 13

It also keeps asking me to reauthenticate (three times so far since I updated HA last night). Wondering if they have restricted their APIs and expire sign ins much quicker than before.

EDIT:

After re-authenticating again it now appears to be working. Will keep an eye on it and report back, if it stops working again.

JamieMichie commented 5 months ago

@timmo001 have you been able to get the entities to come through in HA after the auth change? I've not had any luck, keep getting this in HA:

Screenshot 2024-05-02 at 09 47 13

It also keeps asking me to reauthenticate (three times so far since I updated HA last night). Wondering if they have restricted their APIs and expire sign ins much quicker than before.

EDIT:

After re-authenticating again it now appears to be working. Will keep an eye on it and report back, if it stops working again.

I had the same problem. re-authenticating fixed it. Now it is working. Thanks!