search

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
73.81k stars 30.9k forks source link

Fix elkm1 connection when panel drops VN request (continuation of #69454) #71671

Closed DaveW42 closed 2 years ago

DaveW42 commented 2 years ago

The problem

This issue was addressed in Home Assistant 2022.4, but has emerged again with Home Assistant 2022.5. The prior issue is documented here: https://github.com/home-assistant/core/pull/69454

What version of Home Assistant Core has the issue?

core-2022.5.x (all versions of 2022.5)

What was the last working version of Home Assistant Core?

core-2022.4.7

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Elk

Link to integration documentation on our website

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

Diagnostics information

Elk M1 Gold logs.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Elk M1 Gold Hardware Version .11 Boot version 3.3.2 Firmware version: 5.1.8 Voice List Version: .8

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)

gwww commented 2 years ago

We’re going to need you to try again with the logging. This log does not capture from startup and also does not include the HA parts of the logs.

See https://community.home-assistant.io/t/elk-m1-interface/4461/983 for the log config required. After that is added restart HA.

We need the version of your ElkM1 and M1XEP as well before we can proceed further.

gwww commented 2 years ago

Ignore that last request for ElkM1 version. I see that you included it in the bug report. And it answers the question I had. You are running 5.1.8. The "VN" (get version command) works from 5.1.12 and higher. So that explains why the integration does not work.

We could patch to "make it work" again, but the problem is we say we support 5.2.0 onward for a good reason. There are other things that do not interact well below 5.2.0.

So, I'm going to leave it with you to upgrade your panel and try this out again. I recommend closing this bug.