home-assistant[bot]
commented
1 year 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!
Code owner commands
Code owners of `elkm1` 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 elkm1` Removes the current integration label and assignees on the issue, add the integration domain after the command.(message by CodeOwnersMention)
elkm1 documentation elkm1 source (message by IssueLinks)
bdraco
The problem
The above error appeared after upgrading to 2023.6.1 from a 2023.5.x version.
What version of Home Assistant Core has the issue?
core-2023.6.1
What was the last working version of Home Assistant Core?
core-2023.5.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Elk-M1 Control
Link to integration documentation on our website
https://www.home-assistant.io/integrations/elkm1/
Diagnostics information
N/A as far as I can tell
Error connecting to ElkM1 ([SSL: NO_PROTOCOLS_AVAILABLE] no protocols available (_ssl.c:1002)). Retrying in 32 seconds 10:27:10 PM – (WARNING) runner.py - message first occurred at 9:59:54 PM and shows up 369 times ElkM1 at elks://xxx.xxx.xxx.xxx disconnecting 10:25:35 PM – (WARNING) components/elkm1/init.py - message first occurred at 10:00:14 PM and shows up 17 times Config entry 'ElkM1' for elkm1 integration not ready yet: Timed out connecting to elks://xxx.xxx.xxx.xxx; Retrying in background 10:00:14 PM – (WARNING) config_entries.py
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
I've tried tls1_2, elks, and elk, methods with no success.
I connected with ELK RP software to ensure the network interface was still reachable and it is.