Gyro - MPU 6050

.

Plugin details

Type: Gyro

Name: MPU 6050

Status ESP32: COLLECTION

Status ESP8266: COLLECTION

GitHub: P045_MPU6050.ino

Maintainer: .

Used libraries: .

.

Description

The MPU6050 is an I2C gyro sensor with 3 axis measuring capability. This plugin supports to translate that into motion detection, with configurable threshold and time-windows.

Configuration

../_images/P045_DeviceConfiguration.png

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.

I2C Options

The available settings here depend on the build used. At least the Force Slow I2C speed option is available, but selections for the I2C Multiplexer can also be shown. For details see the I2C Bus page

I2C Address: The address the device is using. Depending on the board used, when available an ADDR pin can be used to select the used address. If that address selection is not available, then an I2C multiplexer (in a matching ESPEasy build) can be used to use multiple sensors on a single ESPEasy unit.

Device Settings

  • Function: Select the function this task should perform.

Available options:

Function options

Movement detection

When selecting the Movement detection function, additional configuration is required for setting up the threshold and movement- and ‘silence’- windows.

The Detection threshold can be configured per X, Y and Z axis (range 0..65535) and will be triggered when it exceeds the set threshold, where the axis is ignored if the threshold is set to 0. An actual threshold can be determined by selecting one of the Acceleration X/Y/Z functions, and making note of the value measured while an expected movement is applied to the sensor.

  • Detection on all 3 axes: When this option is enabled, all 3 axes need to exceed the configured threshold for the counter to be increased. When disabled, only one of the axis need to exceed the threshold to cause an increment.

  • Min. detection count: The minimum count of movements during the Detection window before the count is reset.

  • Detection window: The number of interval passes before the counter is actually increased.

Every 30 seconds a counter for the detection window is increased plus all axis are checked and if they all (or any when Detection on all 3 axes is unchecked) that are enabled exceeded the threshold values, a counter is increased.

Each period, defined by the Detection window, the counter is checked against the Min. detection count and if found equal or larger, movement is detected.

If in the next window the Min. detection count value is not met, movement has stopped. The Detection window cannot be smaller than the Min. detection count.

Other measurements

When Function is set to one of the measurement options, Range acceleration, Acceleration or G-force, the settings related to Movement detection will be hidden:

../_images/P045_All3ValuesCheckbox.png

  • Provide all 3 values (X/Y/X): When unchecked (default), the selected raw X/Y/Z value will be available as the single value in the Values section, below. When checked, all 3 X, Y and Z values for the selected function will be available in the Values section, always in X, Y, Z order. Most usable would be to name them accordingly.

../_images/P045_All3Values.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 minimum value allowed is 1 sec.

Values

The measured value or the counter are available here, by default no name is given for the value, as this is usually chosen based on the function. No formula or decimals are available.

In selected builds, per Value a Stats and Hide checkbox and an Axis selection combobox are available, that when Statis is checked, gathers the data and presents recent data, based on the Interval, in a graph, as described here: Task Value Statistics:

Change log

Changed in version 2.0: …

added 2024-11-03 Checkbox for selecting all 3 X/Y/Z values for a measurement.

added 2022-05-05 Checkbox for selecting ALL or ANY axis movement detection.

added Major overhaul for 2.0 release.

Added in version 1.0: …

added Initial release version.