-
-
Notifications
You must be signed in to change notification settings - Fork 32.6k
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
opower core integration - list index out of range error #138955
Comments
Hey there @tronikos, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) opower documentation |
Hi @tronikos, Looks like this is the same possibly as #113916 docker exec -it $(docker ps -f name=homeassistant -q) bash nano /usr/src/homeassistant/homeassistant/components/opower/coordinator.py
Thank you, |
apparently in docker image that's used there is no nano, when I use the command exactly as posted I get the addon terminal prompt to go down to bquote> |
Is there any other way to get to the file to edit it I'm on the arm version of HAOS so not so easy to get an editor working. |
The problem
List Index out of range error on opower integration for past 5 or so core updates for PG&E account. Had opower working about 3 months ago solid, then got the error in the title and thought it would resolve after a few major revisions of the integration...no luck, is there a method to reset the index back into the expected range?
HAOS
Core 2025.2.4
Supervisor 2025.02.1
Operating System 14.2
Frontend 20250214.0
Thank you,
Daniel
What version of Home Assistant Core has the issue?
2025.2.4
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
opower
Link to integration documentation on our website
https://www.home-assistant.io/integrations/opower/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: