You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is needed for long periods of internet outage in order for the daily data to be reported correctly to pvoutput.
Things to consider: 1) Status code of newer models with pid offset function changes to 3 after sunset/dusk though all data may be retrieved from the inverter.
2) Old models turn off after sunset/dusk
So I am not sure at which exact moment the day data can be retrieved for old models.
Again during days with heavy clouds the inverter may shutdown before sunset.
As the daily output will be over-writen by the live data, the script could start sending day data at some interval (say 30-60 minutes) before sunset/dusk and keep sending until after 5-10 minutes after sunset/dusk if there is a change. Though to implement this, the estimation of sunset/dusk time is probably needed.
The text was updated successfully, but these errors were encountered:
This is needed for long periods of internet outage in order for the daily data to be reported correctly to pvoutput.
Things to consider: 1) Status code of newer models with pid offset function changes to 3 after sunset/dusk though all data may be retrieved from the inverter.
2) Old models turn off after sunset/dusk
So I am not sure at which exact moment the day data can be retrieved for old models.
Again during days with heavy clouds the inverter may shutdown before sunset.
As the daily output will be over-writen by the live data, the script could start sending day data at some interval (say 30-60 minutes) before sunset/dusk and keep sending until after 5-10 minutes after sunset/dusk if there is a change. Though to implement this, the estimation of sunset/dusk time is probably needed.
The text was updated successfully, but these errors were encountered: