core
core copied to clipboard
No entities created after successfully adding the Ovo Energy integration
The problem
OVO Energy plugin successfully logs in; however no services, devices nor entities are created.
I suspect this is due to the plugin not supporting the account number identifier, my OVO account has two accounts associated, when I use the ovoenergy CLI tool (from the python package the integration uses) with no account number specified, it returns success with no data (appropriate data is returned when the account number is specified via the CLI tool).
What version of Home Assistant Core has the issue?
2022.6.0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
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?
2022-06-11 22:13:37 DEBUG (MainThread) [homeassistant.components.ovo_energy] Finished fetching sensor data in 0.669 seconds (success: True)
2022-06-11 22:13:38 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.ovo_energy
Additional information
No response
ovo_energy documentation ovo_energy source (message by IssueLinks)
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!
(message by CodeOwnersMention)
Aha! I wondered if this scenario was why I was unable to get any data from the integration!
For some reason they left my previous address on the account when I moved home last year, and I've had two accounts in my profile ever since.
Seems I have the same issue and also my account has 2 addresses listed due to moving home 12 months ago. I have asked OVO when they will remove the old one and they basically answered "at some point" and couldnt give any more info
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 with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.