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

La Crosse View - "Invalid authentication" #91743

Closed
Rumbaar opened this issue Apr 20, 2023 · 16 comments · Fixed by #91979
Closed

La Crosse View - "Invalid authentication" #91743

Rumbaar opened this issue Apr 20, 2023 · 16 comments · Fixed by #91979

Comments

@Rumbaar
Copy link

Rumbaar commented Apr 20, 2023

The problem

Trying to setup the La Crosse View integration, enter valid Username & Password and then receive the following error. No log entry is generated. I'm able to log into the La Crosse Technology website with these valid credentials and the app.

image

What version of Home Assistant Core has the issue?

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

La Crosse View

Link to integration documentation on our website

https://www.home-assistant.io/integrations/lacrosse_view

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

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

Code owner commands

Code owners of lacrosse_view 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 lacrosse_view Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


lacrosse_view documentation
lacrosse_view source
(message by IssueLinks)

@IceBotYT
Copy link
Contributor

Hi, could you please provide a screenshot of the offending log entry? Thank you!
Open your Home Assistant instance and show your Home Assistant logs.

@Rumbaar
Copy link
Author

Rumbaar commented Apr 21, 2023

Hi, could you please provide a screenshot of the offending log entry? Thank you! Open your Home Assistant instance and show your Home Assistant logs.

Unfortunately, as noted in the original comment, there isn't a log entry that is created when I attempt this action. Is there somewhere else or something else I need to do to ensure a log entry is generated when I'm attempting to install/setup this integration?

My action is, go to integration, search for La Crosse View, click on the entry and the login prompt is displayed. I entry my username & password, it returns an error. Then I go to log area for 'home assistant core' and no new entries relating to the LaCrosseView integration are present. I've filtered by 'lacrosse', empty.

@IceBotYT
Copy link
Contributor

I see, sorry for the inconvenience. Thank you for bringing this to my attention.
I do not have any debug logging in place for the integration, but I am working on it. Once that has been implemented, I should be able to fix your problem.

@IceBotYT
Copy link
Contributor

IceBotYT commented May 5, 2023

Hi there! 2 out of the 3 pull requests I opened have been merged, and the one I need the most has yet to be merged. Unfortunately, the changes won't be available until release 2023.6.0. Thank you for your patience, it is greatly appreciated!

@Rumbaar
Copy link
Author

Rumbaar commented May 6, 2023

Hi there! 2 out of the 3 pull requests I opened have been merged, and the one I need the most has yet to be merged. Unfortunately, the changes won't be available until release 2023.6.0. Thank you for your patience, it is greatly appreciated!

Thanks for the update, all good mate. Good luck, and hopefully it'll help with any debugging.

@IceBotYT
Copy link
Contributor

@home-assistant reopen

@home-assistant home-assistant bot reopened this May 25, 2023
@IceBotYT
Copy link
Contributor

Hi @Rumbaar! The pull request has finally been merged :)
Starting Wednesday with the beta, or the next Wednesday if you do not want to switch to the beta, you can enable the debug logging in configuration.yaml like so:

logger:
  default: info
  logs:
    homeassistant.components.lacrosse_view: debug
    lacrosse_view: debug

Once you have your logs, you can let me know by commenting the contents. Thank you!

@maryandmike
Copy link

I have the same issue...

@maryandmike
Copy link

Any solution?

@IceBotYT
Copy link
Contributor

Could you make sure you're on 2023.6 and follow the instructions above? Thank you!

@shomanjk
Copy link

@IceBotYT Here is what I found in the logs. Does this help you resolve this issue? Need any other details from me?

Logger: homeassistant.components.lacrosse_view.config_flow
Source: components/lacrosse_view/config_flow.py:34
Integration: lacrosse_view (documentation, issues)
First occurred: 1:16:03 AM (3 occurrences)
Last logged: 5:36:11 PM

Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/lacrosse_view/config_flow.py", line 72, in async_step_user
    info = await validate_input(self.hass, user_input)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/lacrosse_view/config_flow.py", line 34, in validate_input
    if await api.login(data["username"], data["password"]):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/lacrosse_view/__init__.py", line 29, in login
    response, data = await request(LOGIN_URL, "POST", self.websession, json=payload)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/lacrosse_view/util.py", line 15, in request
    async with websession.request(method, url, **kwargs) as response:
  File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 1141, in __aenter__
    self._resp = await self._coro
                 ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 467, in _request
    with timer:
  File "/usr/local/lib/python3.11/site-packages/aiohttp/helpers.py", line 721, in __exit__
    raise asyncio.TimeoutError from None
TimeoutError

@IceBotYT
Copy link
Contributor

IceBotYT commented Sep 9, 2023

Are you still experiencing this error?

@shomanjk
Copy link

Are you still experiencing this error?

@IceBotYT yeah, I just now tried again. Unexpected error was displayed on the box where I typed in my credentials after a long delay. Then the above error was logged again.

@mbehensky
Copy link

mbehensky commented Oct 24, 2023

I think that, in my case at least, this is happening because I have a lacrossealerts.com account rather than a lacrosseview account. Even though both talk to lacrosse sensors, the alerts version uses a different website and credentials. There seems to be a separate home assistant integration for lacrossealerts. It is on github: https://github.com/Legomaniac/hass_lacrosse_alerts_mobile I haven't tried it yet.

@issue-triage-workflows
Copy link

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.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 29, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Feb 28, 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.

5 participants