Airthings longterm radon does not match app data

Third party integrations
,
1

I have an Airthings Wave Plus gen 1 device that measures radon, and the Airthings app reports 24h and 365d radon readings. The Airthings BLE and esphome airthings integrations include “longterm” radon values, but both of these integrations report different values for the “longterm” radon reading than the 365d value shown in the app. For example, right now, the app reports the 365d reading as 2.8 pCi/L, while the HA BLE longterm value is 1.1 pCi/L. I have not seen any documentation on what “longterm” constitutes, but I was assuming it would be the same 365d interval as in the Airthings app.

Am I missing anything? Is this a limitation of the BLE data? The Airthings web-based integration does not include the “longterm” value, only the BLE-based integrations.

2

Same happened to me after I did “Reset connectivity” via native app.
Before both HA and native app longterm values were really close, but after - native app-reported value stays as it was before, but HA-reported value seems reset as if new measurement segment was started.

Now sure if it is due to the fact it requires to restart device as part of a process (pull out batteries and plug back in).

Now - trying to understand what is the correct way to restart device when needed while not losing longterm data. In my case - to fix luminance sensor stopped working correctly.