1026 dust sensor is impossible to distinguish when customer calculate averaging?

Q:
question regarding 1026 dust sensor because ” it is impossible to distinguish when customer calculate averaging
In order to reduce measurement variance”.

The 1026 dust sensor MCU does its own averaging internally. Can confirm the below and if it is correct, then it seems the 1026 model may not be able to distinguish between smoke and large dust ?

1) From Sharp ED presentation it says 1026 model has “No need” for “averaging”. This suggests the built-in MCU does averaging internally.

2) The GP2Y1026AU0F specification (Jan, 2018) shows below. It says Vout (output voltage) is updated once per second. This suggests it does averaging.

A:
1026 performs averaging processing internal.
It measures every 10ms and output the average value of 100 measurements every second(1 second =10ms ×100 times)
Therefore, when compared with analog output product( 1010 or 1014), it may be difficult to find big change of output due to house dust.

For dust sensor with microcomputer(1026), there are cases that moving average processing is performed on the user side to further reduce variations.
But in that case, it becomes more difficult to distinguish between big dust and smoke.