Pulse Counter - DS2423

1-Wire 4kbit RAM with counter (only counter is currently used)

Plugin details

Type: Generic

Name: DS2423

Status ESP32: COLLECTION B

Status ESP8266: COLLECTION B

GitHub: P100_CCS811.ino

Maintainer: TD-er

Used libraries: .

Description

1-Wire pulse counter.

The module supports upto four 32-bit counters, of which 2 are with external trigger (A and B).

Configuration

../_images/P100_DeviceConfiguration.png

  • Name: Required by ESPEasy, must be unique among the list of available devices/tasks.

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

Sensor

  • GPIO <-> 1-Wire: Select the GPIO pin the counter is connected to. Once this is set the next section will be available for configuration.

Device Settings

  • Device Address: When 1 or more counters are connected to the unit, a counter can be selected based on the counter device address. (Multiple devices can be connected to the same GPIO pin.)

  • Counter: Select either counter A or counter B, for each counter a separate task has to be configured, if you have wired both the A and B counter to a counter source.

  • Show CountTotal Value: When checked, and the settings saved, the CountTotal value will also be shown, and sent to Controllers if so configured. The CountTotal value is available, wether this option is enabled or not (see below: Get Config Values).

../_images/P100_CountTotalEnabled.png

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.


  • Interval By default, Interval will be set to 60 sec. The data will be collected and optionally sent to any configured controllers using this interval. When an output value is changed, the data will be sent to any configured controller, and an event will also be generated when the Rules are enabled (Tools/Advanced).

Values

The plugin provides the CountDelta value, that will hold the delta compared to the previous read value, and optionally also the CountTotal value. This delta depends on the Interval value, as waiting longer for a new value will probably increase the counted difference. A formula can be set to recalculate. The number of decimals can be set as desired, though for a count that doesn’t make much sense.

Per Value is a Stats checkbox available, that when checked, gathers the data and presents recent data in a graph, as described here: Task Value Statistics:

Get Config Values

Config value

Information

[<taskname>#CounterTotal]

Returns the current total count accumulated for the selected A or B counter since power-on of the sensor.

Change log

Changed in version 2.0: …

changed 2025-03-15 Add CountTotal value, and enable PluginStats feature.

added 2020-04-25