Opower - ConEd - Unable to pull data from account - 403 Forbidden

[Henchman-21]

The problem

Trying to pull my Coned utility data through the Opower integration. I'm able to add my username/password/TOPT and the account adds successfully, however on initializing it says no entities and Failed Setup, will retry. Hovering over the error I see

403, message='Forbidden',url=URL('http://cned.power.com/ei/edge/apis/multi-account-v1/cws/cnd/customers?offset=0%batchSize=100&addressFilter=')

Definitely putting in correct account info, if I change the user/pass/TOTP it errors out adding and will not even try to initialize.

What version of Home Assistant Core has the issue?

core-2024.2.5

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

Have added , reloaded, deleted account, reset TOTP, no change.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Used to use the Orange and Rockland Utility to MQTT Bridge addin but that doesn't seem to be reliable anymore.  Have reset the TOTP a few times, and again it will fail to add successfully if the info is entered incorrectly.

I see this in debugging:
2024-02-28 22:33:14.134 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Consolidated Edison (ConEd) (XXXXXXXXXX@gmail.com)' for opower integration could not authenticate: 403, message='Forbidden', url=URL('https://www.coned.com/sitecore/api/ssc/ConEd-Cms-Services-Controllers-Opower/OpowerService/0/GetOPowerToken')

2024-02-29 15:32:12.418 DEBUG (MainThread) [homeassistant.components.opower.coordinator] Finished fetching Opower data in 5.016 seconds (success: False)

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)}}

[Shocktrooper]

I have this same exact issue for ComEd

[issue-triage-workflows[bot]]

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.

[Henchman-21]

The bot kinda poked me but oddly enough this just started working 3-4 days ago.

[Ixitxachitl]

is that the same as this? I've been getting this error for a couple weeks. Failed setup, will retry: 403, message='Forbidden', url=URL('https://pge.opower.com/ei/edge/apis/DataBrowser-v1/cws/cost/utilityAccount/_[...]_?aggregateType=hour&startDate=2024-05-22T00:00:00-07:00&endDate=2024-06-17T00:00:00-07:00')

[Ixitxachitl]

Yes? No? Maybe something is wrong with my utility account? I'm not sure if this is a bug.

[Henchman-21]

Yes, it wasn't exactly that but was a 403 forbidden error each time. I will note I had 2 accounts in ConEd (one from previous residence). I still have 2 when I login to ConEd but the current one is what opens by default now, so maybe the API calls were trying to hit the previously defaulted inactive account. I don't know how to change that though, I did nothing on either end, so maybe it was something ConEd did as housekeeping with their own systems.

[Ixitxachitl]

I have 2 properties on my account as well, maybe that's the issue, If it doesn't resolve itself maybe I can open a new bug report but it's hard to say if this is repeatable for other users.

[alexkermani]

I have two service addresses on my PG&E account and I suddenly got this 403 error when trying to authenticate opower. No change to the creds, it just stopped working one day several weeks ago. The two accounts were previously feeding into HA without issue.

[stgarrity]

I have the same issue with two service addresses on a PG&E account ... happy to share logs etc if @tronikos or someone else is looking at it?