Integration not signing in with Australian OVO Energy account credentials

[diliff79]

The problem

Sorry if not the right place to highlight this issue, it's not a code issue per-se, but it seems that OVO Energy is a UK Company but has an Australian subsidiary operating separately (from an account integration point of view).

I was struggling to sign into the ovo_energy integration with my Australian account username and password before EVENTUALLY discovering that the integration was probably only ever intended for UK accounts, not Australian accounts. There's no documentation that explains that the integration is UK only and is likely confusing a few Aussies out there. Or maybe I'm the first. :) Either way, I thought the documentation should be a bit more specific.

What version of Home Assistant Core has the issue?

n/a

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ovo_energy

Link to integration documentation on our website

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

[thecode]

Thanks for reporting, I have transferred it to the docs site, as this should be documented that it only supports UK accounts.

[home-assistant]

Hey there @timmo001, mind taking a look at this feedback 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 Change the title of 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.

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved.
If this issue is still relevant, please let us know by leaving a comment 👍
This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.