Closed mbalfour closed 2 years ago
Might also be related to https://github.com/jesserizzo/envoy_reader/issues/78 , in which it mentions that newer Enphase Envoy firmware changed how it authenticates.
enphase_envoy documentation enphase_envoy source (message by IssueLinks)
Hey there @gtdiehl, mind taking a look at this issue as it has been labeled with an integration (enphase_envoy
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
@mbalfour What firmware version is your Enphase Envoy running?
It’s running D7.0.68.
(sent from an iPhone, which encourages brevity)
On Dec 27, 2021, at 8:51 PM, Greg @.***> wrote:
@mbalfour What firmware version is your Enphase Envoy running?
— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.
At this point the envoy_reader
API does not support Envoys running firmware D7.x.x.
I would say this is a duplicate of Issue #61524. Though this is not a Home Assistant issue but the downstream API which is tracked by Issue #78
I'm experiencing the same issue with my IQ Envoy Firmware R5.0.55
`Logger: homeassistant.config_entries Source: config_entries.py:344 First occurred: 10:10:09 AM (1 occurrences) Last logged: 10:10:09 AM
Config entry 'Enphase Envoy' for enphase_envoy integration not ready yet: Error communicating with API: All connection attempts failed; Retrying in background`
I tried removing the integration and re-adding it manually but that failed as well.
@BillyFKidney This appears to be a different issue than the original one @mbalfour posted. I'm not sure how others feel about changing the PR from one issue to another. I personally would want a new PR to track the issue, but that's just me and dealing with defect reports for years on end.
In either case, it appears the code is failing at some point when the integration is working with HA internals? Can you post some details regarding the steps, logs, screenshots, and HA version.
Kinda why I was thinking about a new PR since more details are needed to determine the failure
For the Envoy firmware 7.x.x issue please see this comment for Issue #78 on the envoy_reader
repo. I have some code that supports the new firmware.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
The problem
I just got a new Enphase Envoy installed at my house. I'm trying to set it up in Home Assistant, but get "Unexpected error". Home Assistant: v2021.12.5 Steps:
From looking at the logs, my best guess is that envoy_reader needs to be updated to ignore SSL verification results.
What version of Home Assistant Core has the issue?
core-2021.12.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Enphase Envoy
Link to integration documentation on our website
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
Possibly related to https://github.com/home-assistant/core/issues/60109 . It looks like there was a different problem happening recently that resulted in envoy_reader getting updated to support newer versions of httpx. Maybe the SSL default settings changed in the version bump as well?