Environment - SHTC3

SHTC3 Temperature and Humidity sensor

Plugin details

Type: Environment

Name: SHTC3

Status ESP32: COLLECTION H CLIMATE B

Status ESP8266: CLIMATE B

GitHub: P173_SHTC3.ino

Maintainer: tonhuisman

Used libraries: .

Description

The Sensirion SHTC3 Temperature and Humidity sensor offers good accuracy in a small package, and has a very low power requirement. The sensor is kept in Sleep-mode until a measurement is requested, and even that measurement can use a low-power variant to keep power consumption as low as possible, f.e. when used in a battery-operated setup.

Configuration

../_images/P173_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.

I2C options

The available I2C settings here depend on the build used. At least the Force Slow I2C speed option is available. This sensor can also be used with an I2C Multiplexer, but as the (fixed) device address is 0x70 the I2C multiplexer has to be configured to use a different from the default I2C address. For details see the I2C Bus page.

Device Settings

  • Temperature offset: An offset from the current temperature can be applied in 0.01°C steps. The offset can be set here.

  • Read in Low-power mode: When enabled will use the Low-power version of the command to read the data, for improved battery-life when used in a bettery-powerd setup.

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.

Values

The plugin provides the Temperature and Humidity values. A formula can be set to recalculate, f.e. when temperature has to be presented in ° Fahrenheit instead of ° Celcius: %c_c2f%(%value%). The number of decimals can be set as desired, and defaults to 2.

In selected builds, per Value Stats options are available, that when enabled, will gather the measured data and present most recent data in a graph, as described here: Task Value Statistics:

Change log

Changed in version 2.0: …

added 2024-08-30 Initial release version.