Help! Problem with aggregation?

I received your DB @Psoy, I confirm that the bug is the same as the one encountered by @lmilcent, namely that there are sensor values that are recorded as « NaN » in the DB by the Zigbee2mqtt integration (and recently)

@AlexTrovato The fix we made apparently wasn’t enough, the issue still persists!

I will make a correction and it will be included in the next version of Gladys :slight_smile:

Thank you once again for your help
Have a good evening

I found a way to further solidify this part!

I made a PR here:

It’s crazy!
I hope the « isFloat » validation doesn’t reject integers :smiley:

Are we sure that @Psoy is on a « recent » version?

Good evening,
Yes, 4.8.1, since the day before yesterday evening.
This sensor was well historized under the Mqtt integration and now I have moved it to zigbee2Mqtt for 4 days and no more history.

No! I checked the validation library code they use, and in the tests, integers are accepted :slight_smile:

The bug is indeed present, currently if you sent text it would pass!

For information @Psoy, I merged my fix (Make device state validation more robust (#1480) · GladysAssistant/Gladys@dc5a183 · GitHub) which will be included in the next release of Gladys.

I think I will make a release early next week with this bug fix (not today, it’s forbidden to deploy on Friday :D)

Thanks Pierre-Gilles, I’m not in a hurry, no problem

I know that on Friday, we tidy up the tools :laughing:

@Psoy As expected, new version of Gladys is out today with the fix!

I hope this will solve the issue for you :slight_smile:

I just checked, but 4.8.2 hasn’t reached me yet :wink:. I’ll confirm that for you as soon as possible
Thanks again

It’s done, 4.8.2 has been released and the problem is resolved
Thanks again