home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.9k stars 30.12k forks source link

ElkM1 timeout starting with 2022.3 release #67599

Closed deanryan closed 2 years ago

deanryan commented 2 years ago

The problem

I upgraded core from 2022.2.9 to 2022.3 yesterday (2Mar2022) on HAS OS (Rpi 4 w/ 8GB RAM). After the upgrade the ELKM1 integration started reporting:

Logger: homeassistant.config_entries Source: config_entries.py:366 First occurred: 8:26:18 PM (1 occurrences) Last logged: 8:26:18 PM

Config entry 'ElkM1' for elkm1 integration not ready yet: Timed out connecting to elk://192.168.0.251; Retrying in background

The detailed log shows repeated instances of the message:

2022-03-03 20:26:18 WARNING (MainThread) [elkm1_lib.elk] ElkM1 at elk://192.168.0.251 disconnected

I have a custom web site (local to LAN) that also interfaces to the same control using the non-secure interface, and it is still working fine, so it doesn't appear to be an issue with the control or network.

Detailed log attached: HA ELK M1 Log.txt

What version of Home Assistant Core has the issue?

2022.3

What was the last working version of Home Assistant Core?

2022.2.9

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Elk M1

Link to integration documentation on our website

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

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

probot-home-assistant[bot] commented 2 years ago

elkm1 documentation elkm1 source (message by IssueLinks)

probot-home-assistant[bot] commented 2 years ago

Hey there @gwww, @bdraco, mind taking a look at this issue as it has been labeled with an integration (elkm1) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

bdraco commented 2 years ago

It’s timing out waiting for login. Do you have a username set in your configuration?

Sent from my iPhone

On Mar 3, 2022, at 8:03 PM, probot-home-assistant[bot] @.***> wrote:

 Hey there @gwww, @bdraco, mind taking a look at this issue as it has been labeled with an integration (elkm1) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

bdraco commented 2 years ago

I uploaded the changes in the linked PR here

mkdir -p /config/custom_components
cd config/custom_components
git clone https://github.com/bdraco/elkm1_custom elkm1

Then restart

starman2k01 commented 2 years ago

Same problem here. Also in 2022.3.1

starman2k01 commented 2 years ago

FYI changes fixed it 2022.3.1! Thank you!

iannecj commented 2 years ago

@bdraco I am running Home Assistant 2022.3.1 but after removing user name and password which have always been in my YAML config and restarting it does not correct the problem?

deanryan commented 2 years ago

This didn't fix it for me either. I had to delete the integration and re-install. Not ideal, but it's working again.

bdraco commented 2 years ago

If you set it up and has originally added a username when it's not needed you can

  1. Wait for 2022.3.2 which will ignore the unneeded username
  2. Delete Setup again without the username
  3. Do a backup and manually remove the username from .storage/core.config_entries