core: Can not add two secure instances of Elk M1 when using TLS 1.2
The problem
I have two Elk M1 Golds. I can add one device secured and one non secured into HA with no issue. If two secured devices are to attempted to be added, the first secured device will add and the second will yield the following message “An ElkM1 with this address is already configured”
Home Assistant 2022.11.1 Supervisor 2022.10.2 Operating System 9.3 Frontend 20221102.1 - latest
What version of Home Assistant Core has the issue?
2022.11.1
What was the last working version of Home Assistant Core?
unknown
What type of installation are you running?
Home Assistant Supervised
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?
I have also tried switching the device order on another test environment and it yielded the same result.
Additional information
I will be happy to provide additional information. Just not sure on this one.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 55 (29 by maintainers)
Commits related to this issue
- Fix creating multiple ElkM1 systems with TLS 1.2 fixes #81516 — committed to bdraco/home-assistant by bdraco 2 years ago
- Fix creating multiple ElkM1 systems with TLS 1.2 (#81627) fixes https://github.com/home-assistant/core/issues/81516 — committed to home-assistant/core by bdraco 2 years ago
- Fix creating multiple ElkM1 systems with TLS 1.2 (#81627) fixes https://github.com/home-assistant/core/issues/81516 — committed to home-assistant/core by bdraco 2 years ago
What an unbelievable Community we have here. I absolutely love the devotion and pride I have experienced here since switching to HA. The commitment everyone has here is outstanding. Thank you so much @gww and @bdraco you guys rock.
No it does not matter what order