Known Issues
Issues have been reported with data; these vary by firmware version. Newer firmware may resolve these or introduce new issues.
Production & Consumption data
data |
envoy |
issue |
in firmware |
|---|---|---|---|
whToday |
Mtr |
late reset some time after midnight |
|
reset to non-zero value |
|||
sudden value step changes |
|||
whLastSevenDays |
Mtr |
sudden value step changes |
|
watt_hours_lifetime |
NoCT |
reset to zero when reaching 1.19 MWh |
<8.x |
Std |
1.19 MWh value stepdown |
||
all |
NoCT |
stalled values in V1 Production Endpoint |
>= 8.2.4264 |
Inverter device data
The inverter device data includes a deviceDataLimit that appears to be fixed at 50. If more inverters are installed, only data for the first deviceDataLimit inverters is included, resulting in missing inverter data. When the reported deviceCount is greater than or equal to deviceDataLimit, data falls back to /api/v1/production/inverters to avoid data loss; device detail data will then be unavailable for all inverters.
Daily Outage at 11 PM
Each day, shortly after 11 PM local Envoy time, the Envoy performs some internal resets and cleanups. These cause the Envoy to become unresponsive. How long this outage lasts, varies by hardware type and/or firmware version.
Pyenphase uses retries when a request fails. Default retry setup is no more than 240 seconds elapsed, or 6 attempts. Each try uses the timeout specified in pyenphase.Envoy or a 45 seconds default. With the default timeout of 45 seconds, this results in maximum 6 attempts, 5 retries. Or up to 6 attempts if the failure occurs quicker.
If this 11 PM outage still results in errors, use the pyenphase.Envoy.set_retry_policy() method to set a more relaxed retry scheme.