[linky] Bad values from yesterday once the refresh is working again

[lolodomo]

Once #9358 is used, data refresh is hopefully back.
The new problem is that values are not the ones expected, at least for the yesterday and the current week values.
We are Tuesday, we should have these values considering Monday but yesterday value is UNDEF and current week value is 0.

Either the binding is shifting the values for one day or the request is run too early while the value for yesterday are not yet provided.
Edit: Or the API is never providing last day ?

[lolodomo]

If I go to the WEB site, the value from yesterday is available.
If I use the report console command to list the last values, yestterday is not listed. Other day values look correct.

[lolodomo]

I will investigate a little more but it looks like the API is not returning the yesterday value.
If true; the channel name should be renamed as "day before yesterday".

[lolodomo]

@clinique : WDYT ?

[lolodomo]

If I restart the binding now, value from yesterday is now ok.
My current hypothesis is that the value from Monday was not returned by the API called Wednesday at 05am.
I will have to log the JSON content to confirm that tomorrow morning.

[lolodomo]

If this is confirmed, the solution would be to ignore the result of the request when the value from yesterday is not provided and then let the binding try again later in the day. The check frequency should then be increased a little like a try every 2 hours.

[lolodomo]

At 5 in the morning, the value returned by the API for yesterday is NaN (and the current week value of course does not include yesterday).
The solution I plan to implement is to detect the NaN for the last day value in the API response and in this case to ignore this API response and trigger a new refresh later in the day.