-
Notifications
You must be signed in to change notification settings - Fork 37
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
No data returned causes the dashes #171
Comments
Will there be a fix? I expierence random no data returns also |
I see a similar issue quite often on all signals. I'm not sure but it seems like this happens when 'raw': {} occurs instead of having content inside. just an idea for a temporary workaround (best solution is of course to get the missing data): fill in the missing data with the last valid value instead of keeping it empty. Example with the issue: Example without issue: |
I found in the code: |
I assume the same. Unfortunally I cannot write phyton :-( could it have an effect on this issue to replace with something like this? (probably, the syntax isn't correct) Better would of course having a solution for the root cause of this missing values. But just to show you how bad the result is at my place: |
The root cause is unsolvable, here is what I got from Foxess:
|
I'm having the same behavior of FoxESS integration. This way it is unsuable because it produces wrong values when calculating kWh from kW variables. |
Describe the bug
Sometimes Foxess decides to return an empty data, so we can see no data at that time (image below). Not sure how to fix that
getRaw
would retry to fetch data again when data is empty.To Reproduce
It is easier to see when the refresh time (timedelta) set to 1min
Expected behavior
To see a continuous line without breaks
Screenshots
Debug logs:
The text was updated successfully, but these errors were encountered: