Update envoy_reader.py getData() #63
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update getData() to add optional input parameter to not read inverters. Inverters only update every 5 or 15 mins, depending on Envoy-S configuration, whereas production data updates every minute. Also, requesting inverter data at too short an interval can cause the Envoy to start lagging and eventually timeout. See https://thecomputerperson.wordpress.com/2016/08/03/enphase-envoy-s-data-scraping/#comment-1565 for more details.
Update envoy_reader.py getData()
stuartwishart
added a commit
to stuartwishart/core
that referenced
this pull request
Mar 20, 2021
Update sensor.py to add new Inverters logging options Inverters only update every 5 or 15 mins, depending on Envoy-S configuration, whereas production data updates every minute. Also, requesting inverter data at too short an interval can cause the Envoy to start lagging and eventually timeout. See https://thecomputerperson.wordpress.com/2016/08/03/enphase-envoy-s-data-scraping/#comment-1565 for more details. Note: This change requires an update to jesserizzo/envoy_reader included in PR#63 (jesserizzo/envoy_reader#63) New configuration parameters: inverter_update_period - integer value which defines minutes between Inverters data update requests sent to Envoy-S inverter_logging_full - boolean value that defines whether to send the last Inverters data during a async_update_data() fetch so that the inverter entity information doesn't show Unknown.
Fixed handling of httpx.HTTPError exception
Update envoy_reader.py
|
@stuartwishart We definitely don't want to kill the inverters. I'm wondering how the Home Assistant side would handle this? It would have to switch between the Boolean flag depending on time? Or something like that. The change seems minimal here just adding a flag. Though the code base has changed slightly can you update your code to integrate with the new changes? |
|
@gtdiehl I couldn't work out to how to rebase this PR so I've closed it and created a new PR#68. I've prototype the change on the HomeAssistant side (https://github.com/stuartwishart/core/blob/dev/homeassistant/components/enphase_envoy/sensor.py) to enable a different update rate for the production data and inverter data. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update getData() to add optional input parameter to not read inverters.
Inverters only update every 5 or 15 mins, depending on Envoy-S configuration, whereas production data updates every minute. Also, requesting inverter data at too short an interval can cause the Envoy to start lagging and eventually timeout. See https://thecomputerperson.wordpress.com/2016/08/03/enphase-envoy-s-data-scraping/#comment-1565 for more details.