I also saw the two other numbers in the data frame from the pm1006, but the datasheet does not say what they are, so I did not make a separate sensor output for them. If somebody has good information on what they are, we can add them, of course.
Judging from the code, the Tasmota implementation is RX-only, like the one currently in ESPHome (but see my PR above for adding TX to the one in ESPHome).
I was assuming RX/TX, as I’ve never seen the other two values before, and though the PM2.5 was only due because the TX from the device queries only that. But now I understand the whole thing.
It is interesting that there are PM1006 and PM1006K sensors, with identical look and far too similar specs and behaviour. I have a feeling that the PM1006 is a sensor which fails on the higher specs PM1006K’s QC process or missing some calibration. (The PM1 on the previous picture looks extreme for me, that’s why I think the above.) Someone should ask Cubic what is the difference if any.
I’ve also just reached a similar conclusion as searching for PM1006 on Google. It brings up PM1006K articles where it is just referenced as PM1006. So, it might be some naming thing and they should be the same. Let’s wait for their answer.
By the way, after browsing their website, if you ever come across one of their AM7000 device for a reasonable price, then please let me know. It looks really tempting…
By the way, what is the TX message to the sensor from the IKEA device? Maybe that is the problem. The document says what it should be to query the measurements. Maybe that has some difference.
Read measures result of particles:
Send: 11 01 02 EC
Haha, I had not read your post yet until I came here to comment, but: I just sent it 11 01 02 EC and then I get a frame back that matches the PM1006K datasheet. PM2.5 value matches what I get from the PM1006-style command. PM1.0 and PM10 are zero.