Opower - returning 403 Forbidden logging into ConEd

[nyr3188]

The problem

When trying to log into ConEd, the Opower integration returns the following error:

What version of Home Assistant Core has the issue?

core-2024.6.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

No response

Anything in the logs that might be useful for us?

2024-06-28 15:33:03.197 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Consolidated Edison (ConEd) (*******@*******.***)' for opower integration could not authenticate: 403, message='Forbidden', url=URL('https://www.coned.com/accounts-billing/my-account/energy-use')

2024-06-28 20:23:20.668 ERROR (MainThread) [frontend.js.latest.202406101] Failed to format translation for key 'component.opower.config.step.reauth_confirm.title' in language 'en'. Error: The intl string context variable "name" was not provided to the string "Authentication expired for {name}"
2024-06-28 20:28:35.881 ERROR (MainThread) [frontend.js.latest.202406101] Failed to format translation for key 'component.opower.config.step.reauth_confirm.title' in language 'en'. Error: The intl string context variable "name" was not provided to the string "Authentication expired for {name}"
2024-06-28 20:28:37.062 ERROR (MainThread) [frontend.js.latest.202406101] Failed to format translation for key 'component.opower.config.step.reauth_confirm.title' in language 'en'. Error: The intl string context variable "name" was not provided to the string "Authentication expired for {name}"
2024-06-28 20:28:48.414 ERROR (MainThread) [frontend.js.latest.202406101] Failed to format translation for key 'component.opower.config.step.reauth_confirm.title' in language 'en'. Error: The intl string context variable "name" was not provided to the string "Authentication expired for {name}"
2024-06-28 20:28:49.993 ERROR (MainThread) [frontend.js.latest.202406101] Failed to format translation for key 'component.opower.config.step.reauth_confirm.title' in language 'en'. Error: The intl string context variable "name" was not provided to the string "Authentication expired for {name}"
2024-06-28 20:29:01.613 ERROR (MainThread) [frontend.js.latest.202406101] Failed to format translation for key 'component.opower.config.step.reauth_confirm.title' in language 'en'. Error: The intl string context variable "name" was not provided to the string "Authentication expired for {name}"

Additional information

No response

[home-assistant[bot]]

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

Code owner commands

Code owners of opower 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 opower 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)}}

---

opower documentation opower source _{^{(message by IssueLinks)}}

[indiealexh]

Same issue but PG&E

[krucka]

Same issue but PG&E

I have the same issue with PG&E and OPower. Tried setting up for the first time, and originally said "Success" but then immediately got the forbidden error.

[mwolczko]

Same issue but PG&E

Ditto. Last data returned June 9.

[esapozhnikov]

Same 403 forbidden for PG&E here

[tronikos]

This was regressed in the 2024.6 release. I have a fix that will hopefully make it in 2024.7.3