The temperature offset seems consistent for this sensor, as I see a similar delta. The intended use of the sensor is for temperature compensation of the measurements, not to supply the ambient temperature value
![Verward :?](./images/smilies/icon_e_confused.gif)
when configured for Ikea Vindstyrka, an additional compensation is applied in the code, for the extra heat the ESP adds inside the housing...
Ii didn't add a setting for that, as you can use a formula to subtract the offset, but if you think it's really useful, I can add such setting?
-------------------------------------------
You have configured 2 tasks with different output values, that was required by the old plugin implementation, but I changed the original implementation to now be independent tasks, so not sure if that's a good idea, 2 tasks trying to control the same device...
The advantage of allowing multiple, independent tasks, is that you can have multiple independent sensors on a single ESP, when using an I2C multiplexer (because it has a fixed I2C address). That multiplexer is supported in nearly all ESPEasy builds (See the Hardware tab).
My addition of Get Config Values implementation, allows to fetch all values from a
single task instance, and the intended solution to make them visible on the Device page is to use a Dummy Device, that gets it's values set using a rule that responds to an event of this task, like this:
Code: Select all
// Change #Temperature to #All if "Single event with all values" is enabled
On SEN55#Temperature Do // This assumes a Dummy Device named SEN555, with Quad Values: PM1p0, PM2p5, PM4p0 and PM10p0
TaskValueSet,SEN555,PM1p0,[SEN55#PM1p0]
TaskValueSet,SEN555,PM2p5,[SEN55#PM2p5]
TaskValueSet,SEN555,PM4p0,[SEN55#PM4p0]
TaskValueSet,SEN555,PM10p0,[SEN55#PM10p0]
Endon
The results will be exactly the same, as during measurement all values are retrieved from the sensor (Ikea-mode receives them every second, as that's the update frequency of the Vindstyrka), so are always all available at the same time.
NB: After starting the plugin the first couple of measurements may show some unexpected/0 results, as the sensor seems to do some averaging before returning some values, like tVoc and NOx.