Page 1 of 1

Bug/issue with "delta"

Posted: Sun Jan 14, 2024 1:35 pm
by RoostWeather
Hello,

I have a potential bug with exporting "delta" to SQL. From previous posts I understand that "delta" doesn't come from the database, but rather is calculated based on values in memory which are wiped following a reboot.

However, I have noticed that occasionally after a reboot, delta continues to fail to be calculated even when sufficient time has passed and values should be stored in memory.

So for example, my meteobridge PRO2 has currently been up for 3 days
Screenshot 2024-01-14 113321.png
Screenshot 2024-01-14 113321.png (11.92 KiB) Viewed 21206 times
however the 24h delta has been reporting as NULL since this time.
Screenshot 2024-01-14 113400.png
Screenshot 2024-01-14 113400.png (26.55 KiB) Viewed 21206 times
Any ideas? Thanks very much.

Re: Bug/issue with "delta"

Posted: Tue Jan 23, 2024 10:53 pm
by RoostWeather
Anyone? Thanks

Re: Bug/issue with "delta"

Posted: Wed Jan 24, 2024 1:19 am
by Mattk
What does your 24 hour delta expression look like?

Re: Bug/issue with "delta"

Posted: Wed Jan 24, 2024 11:55 pm
by Mattk
Have run a MBPro2 with Jan 4 firmware for just over 24 hours and noted no issues with delta24h, rebooted with no issues.

Are you using delta24h or delta24H?

Re: Bug/issue with "delta"

Posted: Fri Jan 26, 2024 1:22 am
by RoostWeather
[th0temp-delta1h:NULL], [th0temp-delta24h:NULL]

Those are the expressions I am using. Unfortunately, it's not a consistently repeatable bug, so I think it will be hard to trace. I now circumvent it by recalculating the deltas from the temperatures, so it is not a problem for me anymore. However, I raise it in case anyone wants to look into it.

Thanks.

Re: Bug/issue with "delta"

Posted: Fri Jan 26, 2024 1:37 am
by Mattk
Unable to replicate that either (using the NULL component)?

Re: Bug/issue with "delta"

Posted: Tue Jan 30, 2024 11:00 am
by admin
This effect does show up sometimes, but I still have not fully understood why. My first digging into it for a whole day was not successful. Sorry, no near term fix to be expected.