-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Handle catch-up data #72
Comments
The GEN3PLUS inverter sends the 'catch-up' data with every connection. It would be very easy to send this data to the MQTT broker with the old timestamp. |
I understand, I already assumed, that this will be not easy possible. I have an older model TSOL-MS600, but with probably exotic firmware RSW_400_V1.00.20 |
Can you send me a trace or a dump of one of this additional packets with catchup data? |
Of course. I assume, there are sensible private data inside these traces, which should not published. How can I remove them? |
Pls send a mail: [email protected] |
Thank you for the trace. |
Great, thank you. |
@s-allius I've been using version 0.8.0 for a few days now, and at the moment I seem to be having a lot of connection problems, so a lot of data is being sent as a catch-up block. |
Please try the release candidate v0.8.1-rc.1. There is a hot fix which should fix the connection problems for the GEN3 inverters with version 0.8.0. The filter for the catch-up data in 0.8.0 is only available for GEN3PLUS inverters. For the GEN3 ones I will bring this with version 0.9 |
Ok, thank you. I'm on v0.8.1-rc.1 now. |
Today my inverter was offline for many hours (9:00-18:00) and I noticed some interesting behavior:
When the connection is re-established, the inverter not only sends its current data every 5 minutes. It has been sending 10 additional packets every 5 minutes for ~1 hour. These additional data packets appear to contain data from the time the inverter was offline.
This 'catch-up' data is then used at talent-monitoring.com to fill the gap in the graph for the time the inverter was offline.
Screenshot of 18:30, where data up to 12:30 was subsequently filled.
Screenshot of 19:50, data was subsequently filled completely.
The proxy doesn't distinguish between normal data packets and these catch-up data packets. So all packages are handled as current data, so the chart in Home Assistant looks like this.
I don't know if it will be possible to process this 'catch-up' data with the correct time stamp and then fill in the data in the Home Assistant. At least it would be good to ignore this data if it cannot be handled appropriately.
The text was updated successfully, but these errors were encountered: