[shelly] Plus 1/1PM Add-On support; fix roller pos on open/close state (#13520)

* Added #13493 Plus 1/1PM addon support; Fixed #13515 pos for roller in
open/close state; various null warnings removed; README updated

Signed-off-by: Markus Michels <markus7017@gmail.com>

* digitalInput, analogInput and voltage added for Add-On; README updated

Signed-off-by: Markus Michels <markus7017@gmail.com>

* shelly2-roller re-added (wrong assumption that Shelly 2 doesn't support
roller mode, because it has no power meter)

Signed-off-by: markus7017 <markus7017@gmail.com>
Signed-off-by: Markus Michels <markus7017@gmail.com>

* Initialization for Californium 2.7.3 fixed (no multicast packets where
received)

Signed-off-by: Markus Michels <markus7017@gmail.com>

* Analogous input support for Plus Addon changed; Allterco made a format
change in the beta firmware

Signed-off-by: Markus Michels <markus7017@gmail.com>

* changes applied

Signed-off-by: Markus Michels <markus7017@gmail.com>

* README updated; Shelly Plus addon handling adjusted to latest firmware
(before was beta)

Signed-off-by: Markus Michels <markus7017@gmail.com>

* Update bundles/org.openhab.binding.shelly/README.md

Signed-off-by: Fabian Wolter <github@fabian-wolter.de>

* fix JSON for Shelly1 - ext_switch_enable is a boolean, not an int

Signed-off-by: Markus Michels <markus7017@gmail.com>

Signed-off-by: Markus Michels <markus7017@gmail.com>
Signed-off-by: markus7017 <markus7017@gmail.com>
Signed-off-by: Fabian Wolter <github@fabian-wolter.de>
Co-authored-by: Fabian Wolter <github@fabian-wolter.de>
This commit is contained in:
Markus Michels
2022-12-05 08:51:31 +01:00
committed by GitHub
parent 2382fadaaa
commit 8f972362c3
18 changed files with 622 additions and 183 deletions

View File

@@ -27,6 +27,13 @@ Also check out the [Shelly Manager](doc/ShellyManager.md), which
## Supported Devices
The binding supports both hardware generations
- Generation 1: The original Shelly devices like the Shelly 1, Shelly 2.5, Shelly Flood etc.
- Generation 2: The new Plus / Pro series of devices
The binding provides the same feature set across all devices as good as possible and depending on device specific features.
### Generation 1
| thing-type | Model | Vendor ID |
@@ -35,6 +42,7 @@ Also check out the [Shelly Manager](doc/ShellyManager.md), which
| shelly1l | Shelly 1L Single Relay Switch | SHSW-L |
| shelly1pm | Shelly Single Relay Switch with integrated Power Meter | SHSW-PM |
| shelly2-relay | Shelly Double Relay Switch in relay mode | SHSW-21 |
| shelly2-roller | Shelly2 in Roller Mode | SHSW-21 |
| shelly25-relay | Shelly 2.5 in Relay Switch | SHSW-25 |
| shelly25-roller | Shelly 2.5 in Roller Mode | SHSW-25 |
| shelly4pro | Shelly 4x Relay Switch | SHSW-44 |
@@ -68,7 +76,7 @@ Also check out the [Shelly Manager](doc/ShellyManager.md), which
| shellytrv | Shelly TRV | SHTRV-01 |
| shellydevice | A password protected Shelly device or an unknown type | |
### Generation 2 Plus series:
### Generation 2 Plus series
| thing-type | Model | Vendor ID |
|---------------------|----------------------------------------------------------|----------------|
@@ -80,7 +88,7 @@ Also check out the [Shelly Manager](doc/ShellyManager.md), which
| shellyplusi4dc | Shelly Plus i4 with 4x DC input | SNSN-0D24X |
| shellyplusht | Shelly Plus HT with temperature + humidity sensor | SNSN-0013A |
### Generation 2 Pro series:
### Generation 2 Pro series
| thing-type | Model | Vendor ID |
|---------------------|----------------------------------------------------------|----------------|
@@ -97,21 +105,32 @@ Also check out the [Shelly Manager](doc/ShellyManager.md), which
The binding has the following configuration options:
| Parameter |Description |Mandatory|Default |
|----------------|------------------------------------------------------------------|---------|------------------------------------------------|
| defaultUserId |Default user id for HTTP authentication when not set in the Thing | no |admin |
| defaultPassword|Default password for HTTP authentication when not set in the Thing| no |admin |
| autoCoIoT |Auto-enable CoIoT events when firmware 1.6+ is enabled. | no |true |
### Generation 1
The binding defaults to CoIoT events when firmware 1.6 or newer is detected. CoIoT provides near-realtime updates on device status changes.
This mode also overrules event settings in the Thing configuration.
| Parameter |Description |Mandatory|Default |
|----------------|--------------------------------------------------------------------|---------|------------------------------------------------|
| defaultUserId |Default user id for HTTP authentication when not set in the Thing | no |admin |
| defaultPassword|Default password for HTTP authentication when not set in the Thing | no |admin |
| autoCoIoT |Auto-enable CoIoT events when firmware 1.6+ is enabled (Gen1 only). | no |true |
Disabling this feature allows granular control, which event types will be used. This is also required when the Shelly devices are not located on the same IP subnet (e.g. using a VPN).
`defaultUserId` and `defaultPassword:` will be used by the binding if device protection is enabled.
However, the Plus/Pro devices have a fixed user id admin`. Nevertheless the binding provide that option to allow a mixed operation of Gen 1 and 2 devices in the same installation having same defaults.
`Generation 1`: The binding defaults to CoIoT events when firmware 1.6 or newer is detected.
CoIoT provides near-realtime updates on device status changes.
This mode also overrules event settings in the Thing configuration.
Disabling this feature allows granular control, which event types will be used.
This is also required when the Shelly devices are not located on the same IP subnet (e.g. using a VPN).
In this case autoCoIoT should be disabled, CoIoT events will not work, because the underlying CoAP protocol is based on Multicast IP, which usually doesn't passes a VPN or routed network.
'Generation 2:'
### Generation 2 (Plus
## Firmware
The binding requires firmware version 1.7.0 or newer to enable all features, version 1.9.2 is recommended.
The binding requires firmware version 1.8.2 or newer for generation 1 to enable all features, version 1.9.2+ is recommended. Generation 2 devices require 0.10.2 or newer, the Plus HT at least 0.11.0.
Some of the features are enabled dynamically or are not available depending on device type and firmware release.
The Web UI of the Shelly device displays the current firmware version under Settings:Firmware and shows an update option when a newer version is available.
@@ -134,10 +153,10 @@ The binding uses mDNS to discover the Shelly devices.
They periodically announce their presence, which is used by the binding to find them on the local network.
Sometimes you need to run the manual discovery multiple times until you see all your devices.
`Important`:
`Important for Generation 1 Devices`:
It's recommended to enable CoIoT in the device settings for faster response times (event driven rather than polling).
Open the device's Web UI, section "COIOT settings" and select "Enable COCIOT".
It's recommended to switch the Shelly devices to CoAP Unicast mode if you have only your openHAB system controlling the device.
It's recommended to switch the Shelly devices to CoAP peer mode if you have only your openHAB system controlling the device.
This allows routing the CoIoT/CoAP messages across multiple IP subnets without special network setup required.
You could use Shelly Manager (doc/ShellyManager.md) to easily do the setup (configuring the openHAB host as CoAP peer address).
Keep Multicast mode if you have multiple hosts, which should receive the CoAP updates.
@@ -170,7 +189,7 @@ Sometimes you need to run the discovery multiple times.
### Roller Favorites
Firmware 1.9.2 for Shelly 2.5 in roller mode supports so called favorites for positions.
Firmware 1.9.2+ for Shelly 2.5 and 0.11+ for Plus 2PM in roller mode supports so called roller favorites for positions.
You could use the Shelly App to setup 4 different positions (percentage) and assign id 1-4.
The channel `roller#rollerFav` allows to select those from openHAB and the roller moves to the desired position.
In the Thing configuration you could also configure an id when the `roller#control` channel receives UP or DOWN.
@@ -186,14 +205,14 @@ The binding sets the following Thing status depending on the device status:
| UNKNOWN | Indicates that the status is currently unknown, which must not show a problem. Usually the Thing stays in this status when the device is in sleep mode. Once the device is reachable and was initialized the Thing switches to status ONLINE.|
| ONLINE | ONLINE indicates that the device can be accessed and is responding properly. Battery powered devices also stay ONLINE when in sleep mode. The binding has an integrated watchdog timer supervising the device, see below. The Thing switches to status OFFLINE when some type of communication error occurs. |
| OFFLINE | Communication with the device failed. Check the Thing status in the UI and openHAB's log for an indication of the error. Try restarting OH or deleting and re-discovering the Thing. You could also post to the community thread if the problem persists. |
| CONFIG PENDING | CONFIG PENDING description |
| ERROR: COMM | ERROR: COMM description |
| CONFIG PENDING | The thing has been initialized, but device initialization is in progress or pending (e.g. waiting for device wake-up) |
| ERROR: COMM | Communication with the device has reported an error, check detailed status. |
`Battery powered devices:`
If the device is in sleep mode and can't be reached by the binding, the Thing will change into CONFIG_PENDING.
Once the device wakes up, the Thing will perform initialization and the state will change to ONLINE.
The first time a device is discovered and initialized successfully, the binding will be able to perform auto-initialization when OH is restarted. Waking up the device triggers the event URL and/or CoIoT packet, which is processed by the binding and triggers initialization. Once a device is initialized, it is no longer necessary to manually wake it up after an openHAB restart unless you change the battery. In this case press the button and run the discovery again.
The first time a device is discovered and initialized successfully, the binding will be able to perform auto-initialization when OH is restarted. Waking up the device triggers the a status report (CoIoT packet for event url for Gen1 and WebSocket call for Gen2), which is processed by the binding and triggers initialization. Once a device is initialized, it is no longer necessary to manually wake it up after an openHAB restart unless you change the battery. In this case press the button and run the discovery again.
### Device Watchdog
@@ -208,7 +227,7 @@ The binding also monitors that the device is responding at least once within a g
The period is computed depending on the device type and configuration:
- battery powered devices: &lt;sleepPeriod from device config&gt; + 10min, usually 12h+10min=730min
- else, if CoIoT is enabled: 3*&lt;update Period from device settings&gt;+10sec, usually3*15+10=45sec
- else, if CoIoT or WebSocket is enabled: 3*&lt;update Period from device settings&gt;+10sec, usually3*15+10=45sec
- else 2*60+10sec = 130sec
Once the timer expires the device switches to OFFFLINE and the bindings starts to re-initialize the device periodically.
@@ -266,7 +285,7 @@ The LED channels are available for the Plug-S with firmware 1.6x and for various
## Events
### Action URLs vs. CoIoT
### Generation 1: Action URLs vs. CoIoT
Depending on the firmware release the Shelly devices supports 2 different mechanims to report sensor updates or events.
@@ -299,6 +318,16 @@ If there is no specific reason you should enable CoIoT. Check section Network Se
Enable the autoCoIoT option in the binding configuration or eventsCoIoT in the Thing configuration to activate CoIoT.
### Generation 2: WebSockets
The Plus and Pro series of devices use WebSockets for device communication.
Usually the binding establishes a WebSocket connection to the device (http port 80).
However, battery powered devices like the Plus HT are not reachable while the device is in sleep mode.
For those the binding sets up a so called "Outbound WebSocket" during device initialization.
Afterwards the device wakes up and calls the configured URL, which is the processed by the binding.
The device UI shows the URL when active.
Battery powered devices could only report events to a single host, take care if you have multiple openHAB instances on the same network.
### Button events
Various devices signal an event when the physical button is pressed.
@@ -378,6 +407,7 @@ Depending on the device type and firmware release channels might be not availabl
| |temperature2 |Number |yes |Temperature value of external sensor #2 (if connected to temp/hum addon) |
| |temperature3 |Number |yes |Temperature value of external sensor #3 (if connected to temp/hum addon) |
| |humidity |Number |yes |Humidity in percent (if connected to temp/hum addon) |
| |input1 |Contact |yes |Status of the reed contact (OPEN/CLOSE), only with external switch add-on |
### Shelly 1L (thing-type: shelly1l)
@@ -402,6 +432,7 @@ Depending on the device type and firmware release channels might be not availabl
| |temperature2 |Number |yes |Temperature value of external sensor #2 (if connected to temp/hum addon) |
| |temperature3 |Number |yes |Temperature value of external sensor #3 (if connected to temp/hum addon) |
| |humidity |Number |yes |Humidity in percent (if connected to temp/hum addon) |
| |input1 |Contact |yes |Status of the reed contact (OPEN/CLOSE), only with external switch add-on |
Note: The `meter`for the Shelly 1L is kind of fake.
It doesn't have a real power meter, but you could setup an estimated consumption in the Shelly App, e.g. 60W if you have attached a good old light bulb to the output channel.
@@ -416,13 +447,15 @@ In this case the is no real measurement based on power consumption, but the Shel
| |input |Switch |yes |ON: Input/Button is powered, see General Notes on Channels |
| |button |Trigger |yes |Event trigger, see section Button Events |
|meter |currentWatts |Number |yes |Current power consumption in Watts |
| |lastPower1 |Number |yes |Energy consumption for a round minute, 1 minute ago |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |lastPower1 |Number |yes |Energy consumption for a round minute, 1 minute ago |
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart)
|
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
|sensors |temperature1 |Number |yes |Temperature value of external sensor #1 (if connected to temp/hum addon) |
| |temperature2 |Number |yes |Temperature value of external sensor #2 (if connected to temp/hum addon) |
| |temperature3 |Number |yes |Temperature value of external sensor #3 (if connected to temp/hum addon) |
| |humidity |Number |yes |Humidity in percent (if connected to temp/hum addon) |
| |input1 |Contact |yes |Status of the reed contact (OPEN/CLOSE), only with external switch add-on |
### Shelly EM (thing-type: shellyem)
@@ -438,14 +471,14 @@ In this case the is no real measurement based on power consumption, but the Shel
| |autoOff |Number |r/w |Relay #1: Sets a timer to turn the device OFF after every ON command; in seconds|
| |timerActive |Switch |yes |Relay #1: ON: An auto-on/off timer is active |
|meter1 |currentWatts |Number |yes |Current power consumption in Watts |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |returnedKWH |Number |yes |Total returned energy, kwh |
| |reactiveWatts|Number |yes |Instantaneous reactive power, Watts |
| |voltage |Number |yes |RMS voltage, Volts |
| |powerFactor |Number |yes |Power Factor in percent |
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
|meter2 |currentWatts |Number |yes |Current power consumption in Watts |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |returnedKWH |Number |yes |Total returned energy, kwh |
| |reactiveWatts|Number |yes |Instantaneous reactive power, Watts |
| |voltage |Number |yes |RMS voltage, Volts |
@@ -469,7 +502,7 @@ The Thing id is derived from the service name, so that's the reason why the Thin
| |autoOff |Number |r/w |Relay #1: Sets a timer to turn the device OFF after every ON command; in seconds|
| |timerActive |Switch |yes |Relay #1: ON: An auto-on/off timer is active |
|meter1 |currentWatts |Number |yes |Current power consumption in Watts |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |returnedKWH |Number |yes |Total returned energy, kwh |
| |reactiveWatts|Number |yes |Instantaneous reactive power, Watts |
| |voltage |Number |yes |RMS voltage, Volts |
@@ -477,7 +510,7 @@ The Thing id is derived from the service name, so that's the reason why the Thin
| |powerFactor |Number |yes |Power Factor in percent |
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
|meter2 |currentWatts |Number |yes |Current power consumption in Watts |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |returnedKWH |Number |yes |Total returned energy, kwh |
| |reactiveWatts|Number |yes |Instantaneous reactive power, Watts |
| |voltage |Number |yes |RMS voltage, Volts |
@@ -485,7 +518,7 @@ The Thing id is derived from the service name, so that's the reason why the Thin
| |powerFactor |Number |yes |Power Factor in percent |
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
|meter3 |currentWatts |Number |yes |Current power consumption in Watts |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |returnedKWH |Number |yes |Total returned energy, kwh |
| |reactiveWatts|Number |yes |Instantaneous reactive power, Watts |
| |voltage |Number |yes |RMS voltage, Volts |
@@ -514,9 +547,31 @@ The Thing id is derived from the service name, so that's the reason why the Thin
| |button |Trigger |yes |Event trigger, see section Button Events |
|meter |currentWatts |Number |yes |Current power consumption in Watts |
| |lastPower1 |Number |yes |Energy consumption for a round minute, 1 minute ago |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
### Shelly 2 - roller mode thing-type: shelly2-roller)
|Group |Channel |Type |read-only|Description |
|----------|-------------|---------|---------|--------------------------------------------------------------------------------------|
|roller |control |Rollershutter|r/w |can be open (0%), stop, or close (100%); could also handle ON (open) and OFF (close) |
| |input |Switch |yes |ON: Input/Button is powered, see General Notes on Channels |
| |event |Trigger |yes |Roller event/trigger with payload ROLLER_OPEN / ROLLER_CLOSE / ROLLER_STOP |
| |rollerpos |Number |r/w |Roller position: 100%=open...0%=closed; gets updated when the roller stops, see Notes |
| |rollerFav |Number |r/w |Select roller position favorite (1-4, 0=no), see Notes |
| |state |String |yes |Roller state: open/close/stop |
| |stopReason |String |yes |Last stop reasons: normal, safety_switch or obstacle |
| |safety |Switch |yes |Indicates status of the Safety Switch, ON=problem detected, powered off |
|meter |currentWatts |Number |yes |Current power consumption in Watts |
| |lastPower1 |Number |yes |Accumulated energy consumption in Watts for the full last minute |
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (reset on restart) |
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
*Note: The Roller should be calibrated using the device Web UI or Shelly App, otherwise the position can't be set.*
The roller positioning calibration has to be performed using the Shelly Web UI or App before the position can be set in percent.
Refer to [Smartify Roller Shutters with openHAB and Shelly](doc/UseCaseSmartRoller.md) for more information on roller integration.
### Shelly 2.5 - relay mode (thing-type:shelly25-relay)
The Shelly 2.5 includes 2 meters, one for each channel.
@@ -592,7 +647,7 @@ The Shelly 4Pro provides 4 relays and 4 power meters.
| |timerActive |Switch |yes |Relay #1: ON: An auto-on/off timer is active |
|meter |currentWatts |Number |yes |Current power consumption in Watts |
| |lastPower1 |Number |yes |Energy consumption for a round minute, 1 minute ago |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
@@ -676,10 +731,10 @@ This information applies to the Shelly Duo-1 as well as the Duo White for the G1
| |brightness |Dimmer | |Brightness: 0..100% or 0..100 |
|meter |currentWatts |Number |yes |Current power consumption in Watts |
| |lastPower1 |Number |yes |Energy consumption in Watts for a round minute, 1 minute ago |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart)|
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
#### Shelly Vintage (thing-type: shellyvintage)
### Shelly Vintage (thing-type: shellyvintage)
|Group |Channel |Type |read-only|Description |
|----------|-------------|---------|---------|-----------------------------------------------------------------------|
@@ -981,6 +1036,20 @@ You should calibrate the valve using the device Web UI or Shelly App before star
| |timerActive |Switch |yes |Relay #1: ON: An auto-on/off timer is active |
| |button |Trigger |yes |Event trigger, see section Button Events |
If the Shelly Add-On is installed:
|Group |Channel |Type |read-only|Description |
|----------|-------------|---------|---------|---------------------------------------------------------------------------------|
|sensors |temperature1 |Number |yes |Temperature value of external sensor #1 |
| |temperature2 |Number |yes |Temperature value of external sensor #2 |
| |temperature3 |Number |yes |Temperature value of external sensor #3 |
| |temperature4 |Number |yes |Temperature value of external sensor #4 |
| |temperature5 |Number |yes |Temperature value of external sensor #5 |
| |humidity |Number |yes |Relative Humidity in percent |
| |voltage |Number |yes |Measured voltage |
| |analogInput |Number |yes |Percentage of reference voltage (VREF) at analogous input |
| |digitalInput |Switch |yes |State of digital input (ON/OFF) |
### Shelly Plus 1PM (thing-type: shellyplus1pm)
|Group |Channel |Type |read-only|Description |
@@ -994,9 +1063,23 @@ You should calibrate the valve using the device Web UI or Shelly App before star
| |button |Trigger |yes |Event trigger, see section Button Events |
|meter |currentWatts |Number |yes |Current power consumption in Watts |
| |lastPower1 |Number |yes |Energy consumption for a round minute, 1 minute ago |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
If the Shelly Add-On is installed:
|Group |Channel |Type |read-only|Description |
|----------|-------------|---------|---------|---------------------------------------------------------------------------------|
|sensors |temperature1 |Number |yes |Temperature value of external sensor #1 |
| |temperature2 |Number |yes |Temperature value of external sensor #2 |
| |temperature3 |Number |yes |Temperature value of external sensor #3 |
| |temperature4 |Number |yes |Temperature value of external sensor #4 |
| |temperature5 |Number |yes |Temperature value of external sensor #5 |
| |humidity |Number |yes |Relative Humidity in percent |
| |voltage |Number |yes |Measured voltage |
| |analogInput |Number |yes |Percentage of reference voltage (VREF) at analogous input |
| |digitalInput |Switch |yes |State of digital input (ON/OFF) |
### Shelly Plus 2PM - relay mode (thing-type: shellyplus2pm-relay)
|Group |Channel |Type |read-only|Description |
@@ -1010,7 +1093,7 @@ You should calibrate the valve using the device Web UI or Shelly App before star
| |button |Trigger |yes |Event trigger, see section Button Events |
|meter1 |currentWatts |Number |yes |Current power consumption in Watts |
| |lastPower1 |Number |yes |Energy consumption for a round minute, 1 minute ago |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
|relay2 |output |Switch |r/w |Relay #2: Controls the relay's output channel (on/off) |
| |outputName |String |yes |Logical name of this relay output as configured in the Shelly App |
@@ -1021,7 +1104,7 @@ You should calibrate the valve using the device Web UI or Shelly App before star
| |button |Trigger |yes |Event trigger, see section Button Events |
|meter2 |currentWatts |Number |yes |Current power consumption in Watts |
| |lastPower1 |Number |yes |Energy consumption for a round minute, 1 minute ago |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
### Shelly Plus 2PM - roller mode (thing-type: shellyplus2pm-roller)
@@ -1104,7 +1187,7 @@ Channels lastEvent and eventCount are only available if input type is set to mom
| |timerActive |Switch |yes |Relay #1: ON: An auto-on/off timer is active |
|meter |currentWatts |Number |yes |Current power consumption in Watts |
| |lastPower1 |Number |yes |Energy consumption for a round minute, 1 minute ago |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
@@ -1148,7 +1231,7 @@ Channels lastEvent and eventCount are only available if input type is set to mom
| |button |Trigger |yes |Event trigger, see section Button Events |
|meter |currentWatts |Number |yes |Current power consumption in Watts |
| |lastPower1 |Number |yes |Energy consumption for a round minute, 1 minute ago |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
### Shelly Pro 2 PM - roller mode (thing-type: shellypro2pm-roller)
@@ -1162,10 +1245,10 @@ Channels lastEvent and eventCount are only available if input type is set to mom
| |stopReason |String |yes |Last stop reasons: normal, safety_switch or obstacle |
| |safety |Switch |yes |Indicates status of the Safety Switch, ON=problem detected, powered off |
| |event |Trigger |yes |Roller event/trigger with payload ROLLER_OPEN / ROLLER_CLOSE / ROLLER_STOP |
|meter |currentWatts |Number |yes |Current power consumption in Watts |
| |lastPower1 |Number |yes |Energy consumption for a round minute, 1 minute ago |
| |totalKWH |Number |yes |Total energy consumption in Watts since the device powered up (resets on restart)|
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
|meter |currentWatts |Number |yes |Current power consumption in Watts |
| |lastPower1 |Number |yes |Energy consumption for a round minute, 1 minute ago |
| |totalKWH |Number |yes |Total energy consumption in kwh since the device powered up (resets on restart) |
| |lastUpdate |DateTime |yes |Timestamp of the last measurement |
### Shelly Pro 3 (thing-type: shellypro3)