-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed data gets - error detection required #6
Comments
(UPDATED)
|
After ~5 days of operation the updated code appears to be working as expected. There has been no spurious data gets and the intraday energy total and channel energy continue to match those provided by the Solar Analytics user portal. Will keep testing for another 5 days before declaring the issue fixed. |
Our HFC based home internet service was offline for 32 hours Wed/Thurs until yesterday evening. While my GW-router wireless back-up did operate the service was very poor (low bandwidth, packet-loss) due to so many others similarly being impacted. I had various cloud based sensors "unavailable" at times and remote access via SSL was next to impossible. Nonetheless the SA code above worked as expected and there were no spurious hourly reports and the end-of-day totals and channel data matched that reported by the Solar Analytics portal. I think that I'm ready to declare a test success and publish the updated code. |
- added some error checking to deal with daily energy total errors when the data get is 'unavailable' or 'unknown' - removed "force_update: true" - where the data get may be 'unavailable' - removed "state_class: measurement" and "device_class: energy" for rest platform sensors (not applicable) #6
Appears to be all fixed. Cleaned-up and tested code now published as Release 3. |
Very rarely, there is spurious data recorded in the HA Energy Manager. It shows up as an extreme 1-hour spike (e.g. 50 to 100kWh which is just not possible) in the usage and generation data and may be a result of a failed get, or errored data from Solar Analytics. Some error detection (and correction) is required to fix these data records for the sake or impacting long-term data collection.
Unfortunately, when checking the history, the source data has been overwritten within 5 minutes. Some clever investigation and debugging is required.
The text was updated successfully, but these errors were encountered: