Dust - PM1006(K) (Vindriktning)

Dust level sensors

Plugin details

Type: Dust

Name: PM1006(K) Vindriktning

Status ESP32: COLLECTION E CLIMATE

Status ESP8266: COLLECTION E CLIMATE

GitHub: P144_Vindriktning.ino

Maintainer: flashmark

Used libraries: ESPEasy Serial

Description

This plugin supports the dust sensor used in the Ikea Vindriktning. The PM1006K sensor uses a serial protocol to communicate with the controller. The Vindriktning contains a controller that sets up the sensor and reads the value regularly. This plugin is intended to eavedrop this communication. All sensor reading results are copied to the plugin.

Note: The current plugin does not support direct communication with the PM1006(K) sensor. However, the plugin can be extended later to also support standalone control of this device.

Hardware

The Vindrikting can be bought by Ikea. The device can be opened easily by 4 screws. Inside there is room for a Wemos D1 mini or a similar form factor. The 5 Volt power is available on the Vindrikning solder pads. Also the data received from the sensor is available on a solder pad. Images of a hacked Vindrikning are available on the internet.

Connections

Connecting the Vindrikning 
Vindriktning  ESP    Signal
VCC           VSUP   5V supplied by Vindrikning
GND           GND    Ground
data          RX     Serial data from Vindrikning

See Serial Helper configuration for the options to connect a serial communication to the ESP. The TX signal of the UART is not connected to the Vindrikning. A future version of the plugin might use both TX and RX to directly control the PMS1006(K) sensor without using the Ikea Vindrikning controller.

Power to the ESP is supplied by the Vindrikning processor board and must be connected to the 5V input of the ESP board. This is the same power as supplied to the Vindrikning using the USB connector at the back. In case the ESP board has its own USB connector this connector can be used to supply the power to the system and have a debug connection to your PC. Never connect both USB connectors at the same time, this may cause serious power issues.

Device configuration

Device configuration

task settings

Name : A unique name should be entered here.

Enabled : The device can be disabled or enabled. When not enabled the device should not use any resources.

Sensor

Serial Port : Select the serial port to be used. Choices depend on the type of ESP chip being used.

See Serial Helper configuration for the available options.

Data Acquisition

This group of settings are standard available configuration items.

  • Single event with all values: When this setting is enabled, all available values will be sent in a single event <TaskName>#All, with all values in order as arguments to the event.

  • Show derived values: When checked, the Devices overview page, and the /json endpoint (used for updating the Devices overview page) will include any Derived values as defined. See the TaskValueSetDerived and TaskValueSetPresentation commands.

  • Event & Log derived values: When checked, the Derived values will be generated as Events, to be handled in Rules, and sent to logging devices like the Syslog server and/or SD-card logging.

(The derived values options are only available if String variables feature is included in the build.)


  • Send to Controller: Select the Controller(s) to send the Values to, either on a TaskRun command applied to the task, or on an Interval time action.

Send to Controller is only visible when one or more Controllers are configured.

Depending on the controller capabilities, some configuration settings may be shown:

../_images/Task_config_page_Controllers_section.png

All configured Controllers are shown here, including the enabled or disabled state (multiple Controllers can be enabled, only a single MQTT Controller can be enabled at one time!).

For each controller the user can select wether the data should be sent on each Interval (or explicit TaskRun).

For the Domoticz controllers the value index (IDX) has to be configured.

For some controllers, like Home Assistant/openHAB, there are extra options available.

  • Group: This represents the group id to combine all values from multiple tasks into a single grouped-device during MQTT AutoDiscovery. Groups, by design, can span multiple ESPEasy devices, if desired, as long as the Task/Valuename combinations are unique. If a group should only combine Tasks from a single ESPEasy unit, the group id should be unique across multiple ESPEasy units. The group description, default Group <n>, can be adjusted in Home Assistant. If the Group value matches the current Unit nr, the Unit name, %sysname%, is used instead of Group <nr>.

  • Retained: For MQTT Controllers, this setting can be enabled to send the values for the current task with the Retain flag set. The Publish Retain flag in the Controller settings will override this by sending all task values with Retain flag enabled.

  • Send derived: This checkbox determines if any configured Derived values should also be sent to the controller (and included in the AutoDiscovery if that’s available and enabled).

  • Resend MQTT Discovery: When checked, will start a resend of the MQTT Discovery process for this task after a random delay, when Submit is clicked, so any changed settings will be updated in the MQTT broker. This setting is only available if the controller is enabled, the Auto Discovery feature is available and enabled for the controller. This setting is not stored.

Other controllers, like f.e. FHEM HTTP, do not support additional settings besides the checkbox to enable sending the data.


Commands

This plugin does not support additional commands.

Change log

Added in version 2.0: …

added 2023-04-10 Created.