Skip to content
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 - Unknown error occurred from SMUD #114870

Closed
luckygenes-dw opened this issue Apr 4, 2024 · 3 comments · Fixed by #114826
Closed

Opower - Unknown error occurred from SMUD #114870

luckygenes-dw opened this issue Apr 4, 2024 · 3 comments · Fixed by #114826

Comments

@luckygenes-dw
Copy link

The problem

Selected Add Entry then selected Sacramento Municipal Utility District (SMUD) from dropdown list, entered credentials for SMUD account then clicked submit. Integration appeared to be processing request then after a few seconds, integration displayed "Unknown error occurred".

What version of Home Assistant Core has the issue?

core-2024.4.0

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?

File "/usr/src/homeassistant/homeassistant/components/opower/config_flow.py", line 84, in async_step_user
    errors = await _validate_login(self.hass, user_input)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/opower/config_flow.py", line 50, in _validate_login
    await api.async_login()
  File "/usr/local/lib/python3.12/site-packages/opower/opower.py", line 193, in async_login
    self.access_token = await self.utility.async_login(
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/opower/utilities/smud.py", line 164, in async_login
    okta_login_2_url = SMUD.get_okta_url_from_response_redirect(
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/opower/utilities/smud.py", line 234, in get_okta_url_from_response_redirect
    return query_parts["redirectUrl"][0]

Additional information

Opower integration installed prior to latest 2024.4.0 install.

@home-assistant
Copy link

home-assistant bot commented Apr 4, 2024

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)

@darth-monkey
Copy link

Similar issue for me on 2024.4.0 but getting Failed to connect.

Nothing generated in logs regardless of log level - if someone can help direct how to collect that, I'd attach here as well.

@tronikos tronikos mentioned this issue Apr 4, 2024
20 tasks
@tronikos
Copy link
Member

tronikos commented Apr 4, 2024

This should be fixed in tronikos/opower#77 by @BrianHenryIE
You can verify by running the demo.py at https://github.com/tronikos/opower or verify once #114826 is merged and released

@github-actions github-actions bot locked and limited conversation to collaborators May 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants