core: Elk M1 no longer integrating after upgrade to Core 2023.6

The problem

After upgrading to 6.0 from 5.x was unable to connect to the Elk M1.

What version of Home Assistant Core has the issue?

6.0

What was the last working version of Home Assistant Core?

5.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Elk M1

Link to integration documentation on our website

https://github.com/home-assistant/core/tree/dev/homeassistant/components/elkm1

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: elkm1_lib.connection
Source: components/elkm1/__init__.py:389
First occurred: 9:00:17 PM (12 occurrences)
Last logged: 9:14:35 PM

ElkM1 at elks://192.168.1.190 disconnecting


Logger: elkm1_lib.connection
Source: runner.py:179
First occurred: 8:59:57 PM (185 occurrences)
Last logged: 9:15:39 PM

Error connecting to ElkM1 ([SSL: NO_PROTOCOLS_AVAILABLE] no protocols available (_ssl.c:1002)). Retrying in 60 seconds
Error connecting to ElkM1 ([SSL: NO_PROTOCOLS_AVAILABLE] no protocols available (_ssl.c:1002)). Retrying in 4 seconds
Error connecting to ElkM1 ([SSL: NO_PROTOCOLS_AVAILABLE] no protocols available (_ssl.c:1002)). Retrying in 8 seconds
Error connecting to ElkM1 ([SSL: NO_PROTOCOLS_AVAILABLE] no protocols available (_ssl.c:1002)). Retrying in 16 seconds
Error connecting to ElkM1 ([SSL: NO_PROTOCOLS_AVAILABLE] no protocols available (_ssl.c:1002)). Retrying in 32 seconds

Additional information

No response

About this issue

Original URL
State: closed
Created a year ago
Reactions: 1
Comments: 63 (31 by maintainers)

Commits related to this issue

Fix for https://github.com/home-assistant/core/issues/94198 — committed to gwww/elkm1 by gwww a year ago

Most upvoted comments

Fixed is merged and will be in 2023.6.2

bdraco on Jun 12, 2023

I get enough love by just writing code. Sometimes its painful… especially this SSL stuff which I only know about by writing this integration. Fortunately I have the very talented @bdraco to lean on ❤️

It would be great if someone could test using the same procedure earlier in the thread.

Thank you so much. I can confirm the latest fix works for me on 2023.6.1.

t90rak on Jun 12, 2023

I get enough love by just writing code. Sometimes its painful… especially this SSL stuff which I only know about by writing this integration. Fortunately I have the very talented @bdraco to lean on ❤️

It would be great if someone could test using the same procedure earlier in the thread.

gwww on Jun 11, 2023

I just pushed a fix that works for me. Fingers crossed! @bdraco the magic incantation was SECLEVEL=0. Found it when I found the right release notes.

gwww on Jun 11, 2023

I’m having the same issue, cannot connect via ELK RP either. I tried reloading my 5.4 backup, but it doesn’t seem to work. It says it is restoring the backup and just sits there with the spinning icon. If I look at the console for my VM it shows that HA is rebooted, but still on 6.1 and the web interface will not load. One attempt I got it show 5.4 on console, but no web interface. Force a reboot through the VM Supervisor and it always reboots to 6.1 and acts like I never did a restore. If I can’t restore, I really need to get my ELK working again. I use UPB lighting through my elk so I have lost all my lighting controls and my security controls.

I can’t restore to 5.4 either, same problem. Weird combination of bugs…I run my whole house via ELK so this hurts…

starman2k01 on Jun 11, 2023

I finally have a test rig.

Doing:

/opt/homebrew/opt/openssl@1.1/bin/openssl s_client -cipher ALL@SECLEVEL=1 -tls1 -connect 192.168.2.12:2601

works. As does DEFAULT, DEFAULT@SECLEVEL=1, and a few other combinations I tried.

When I switch to @3.1 version of openssl nothing connects.

I too am trying to see what changed in openssl 3.1.

gwww on Jun 11, 2023

@frr032 You have a typo. You should not have a ~ at the end of the line.

gwww on Jun 11, 2023

I’m not a Python programmer, but I will say I’m a massive fan of whoever wrote the Elk HA integration. Alarm <> Smart Home interconnection is the killer interface in a project. I recall it was the main reason I went with Control4 all those years ago and when I found out Elk could be connected within HA it was also the trigger (literally) for taking the dive in the first place into HA. And installing it as my new home auto project, and ditching Control4. Since doing that I have never looked back! But it’s crucial that things be stable. This is security we are talking about here. As we all know this fabulous driver exposes every alarm sensor as well as arrival/leave action triggers to automation using the alarm. There are a myriad of things that make it totally awesome. This is the second time it has broken recently due to a major upgrade in HA. Things shouldn’t feel beta when it comes to home security. Is there any way the developers at Nabu Casa can test Elk integration first before a HA update release?. I know I am probably asking too much, but I feel it’s important to say it. When a HA update doesn’t go well like this, my whole home automation comes crashing down. Its a bad look. My wife starts to notice and complain. Security is crucial to a smart home ecosystem. Cheers

wappinghigh on Jun 10, 2023

I ran it in 6.0. Didn’t realize 6.1 was out, I’m getting 6.1 now to try it.

On 6/8/2023 8:24 PM, Glenn Waters wrote:

Did you just switch onto 2023.06.1 or were you already running it?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

alindner19 on Jun 9, 2023