Description
Manage PM10 sensors in the Matter integration
Description
Manage PM10 sensors in the Matter integration
Hi,
I opened a PR:
I have a question: for now in Gladys we have 3 color levels, namely: good, average, bad.
Would it be good to use the scale posted previously with 6 colors or not?
Hi @Nagromdark and thanks for the PR!
for the PM2.5 that @pierre-gilles had added, the color level (base 3) is not consistent with what I had on the Dyson app.
According to Perplexity, here are the different tiers of the ATMO thresholds (which do not necessarily correspond to the Dyson scale except maybe if divided by 5 or 10) :
After a few questions to Perplexity, itâs better to base ourselves on the ATMO values :
Thanks for the PR @Nagromdark ![]()
Did you test that it works?
I donât really have an opinion, we can
Thanks @mutmut for this data,
OK weâll stick to 3 levels for now, I suggest for PM10 :
For PM2.5 this seems better to me :
Yes I tested locally that it works, I can take screenshots here as soon
Which Matter device did you test with?
That seems pretty good
That seems better, borderline the « Good » could be <= 10 from what I find, but that might be too strict.
Iâm fine with you making the change in another PR though ![]()
OK Iâll make a separate PR for PM2.5
For PM10, I therefore need to
Yes, you can for PM10, I was talking about PM2.5 ![]()
So, was it working at least a little or did you fail to test the value reporting?
At worst, you can use Matterbridge with the example plugin: GitHub - Luligu/matterbridge-example-dynamic-platform: Matterbridge dynamic platform plugin example
which sends random values at regular intervals, it allows you to run tests very easily ![]()
Iâve merged your PR for the PM2.5 change, thanks again for the PR ![]()
Iâve added you to the README as a contributor, congrats on your first contribution @Nagromdark ![]()
Thanks @pierre-gilles ,
yes I was able to test PM10, the values are coming through fine in Gladys. Thanks for the test plugin, nevertheless it seems to have a few small bugs in this plugin :
Anyway, I can see the reading on the right
Ok, in that case that sounds good to me ![]()
Iâll rebase onto master to resolve the conflicts and then Iâll merge!
Thanks for your contribution!
Itâs merged, it will be included in the next Gladys release ![]()
Itâs available in Gladys Assistant 4.62:
Thanks for your contribution ![]()