SHEL Sensor H&T WIFI TF wh

Product Information

platform: mqtt name: Rolling Shutters command_topic: shellies/shellyswitch25-/roller/0/command # rc, open, close and stop state_topic: shellies/shellyswitch25-/roller/0 # open, close, stop position_topic: shellies/shellyswitch25-/roller/0/pos set_position_topic: shellies/shellyswitch25-/roller/0/command/pos availability_topic: shellies/shellyswitch25-/online json_attributes_topic: shellies/shellyswitch25-/info payload_open: open payload_close: close payload_stop: stop state_opening: open state_closing: close position_open: 100 position_closed: 0 payload_available: true payload_not_available: false qos: 1 switch: Configuring a device as cover allows you to control things like blinds, curtains, shades, shutters, garage doors, … If you’ve been getting seriously into HomeKit, and have found yourself exploring all the possibilities, you’ll quite probably be aware of HomeBridge or HomeAssistant, which for want of a better word, are platforms that allow many non-HomeKit devices to be exposed to HomeKit, albeit unofficially. Now, despite the fact that many of these devices are not officially meant to work with HomeKit, a lot of people love the challenge of ‘shoehorning’ something into Apple’s smart home platform for a variety of reasons, not least for being able to control these devices from the Home app, but also to add functionality to a device that Apple doesn’t currently support, like robot vacuums. Others simply love the hardware they have that doesn’t happen to work with HomeKit, like Nest thermostats or Ring video doorbells. Going one step further, there are some companies, like Sonoff for example, that produce a series of devices that can have firmware added to them to make them HomeKit compatible without even the need for HomeBridge. They’re still not certified of course. One other such company is Shelly, Based in Sofia, Bulgaria, who produce a massive variety of devices, all of which can work with HomeKit via HomeBridge, and even carry ‘official’ support via the HOOBS application, which is in essence, an interface that makes using HomeBridge easier to navigate. If Shelly devices are in a different subnet than the Home Assistant server, you should ensure communication on UDP port 5683 between these subnets.

If you have external temperature or humidity sensors connected to the Shelly 1PM, you can also read their values over MQTT. Temperature ¶ I could see this sensor being useful for those working from home. You could plug it in overnight and monitor the air quality, temperature, and humidity while you sleep, and in the morning, place it on your desk. The CO2, PM2.5, and PM10 readings will give you an extra insight as to when your window should be opened. Shelly Plus Add-on is a galvanically isolated sensor interface for all Shelly Plus relays. Use it to measure temperature and humidity using its 1-Wire terminals, or connect various analog and digital sensors for complex automation and higher efficiency. Highly compatibleswitches/energy/shelly_em.yaml - platform: mqtt name: "EM - Relay" expire_after: 604800 qos: 1 command_topic: "shellies/shellyem-/relay/0/command" state_topic: "shellies/shellyem-/relay/0" value_template: {{ 'on' if value == 'on' else 'off' }} # Test for capturing 'overpower' state - platform: mqtt name: "EM - Phase A - Reset Totals" expire_after: 604800 qos: 1 optimistic: true payload_on: "reset_totals" payload_off: "" command_topic: "shellies/shellyem-/emeter/0/command" - platform: mqtt name: "EM - Reset Device Data" expire_after: 604800 qos: 1 optimistic: true payload_on: "reset_data" payload_off: "" command_topic: "shellies/shellyem-/command" Shelly 3EM ¶ The integration uses the following strategy to name its entities if the device has more than one relay: These relays can be used to control 2 different loads (e.g. 2 lamps in a room) or to control the up/down motion of rolling shutters. We’re all using Home Assistant to automate our lives, why not use it to automate device integration? Shelly Gen 1 and Shelly Gen 2 ¶

Motion-controlled lights - Shelly Plus Add-on can also be connected to a PIR sensor to light up rooms that you occasionally use around the house. This way, when you enter the room, the light will come on for as long as you need it to. For battery-powered devices, the update platform entities only inform about the availability of firmware updates but are not able to trigger the update process. Using the homeassistant.update_entity service for an entity belonging to a battery-powered device is not possible because most of the time these devices are sleeping (are offline). sensors/energy/shelly_em.yaml - platform: mqtt name: "EM - Phase A - Energy" value_template: "{{ value|float / 60000 }}" # Wm to kWh unit_of_measurement: 'kWh' expire_after: 86400 device_class: energy state_class: total_increasing qos: 1 state_topic: "shellies/shellyem-/emeter/0/energy" - platform: mqtt name: "EM - Phase A - Returned Energy" value_template: "{{ value|float / 60000 }}" unit_of_measurement: 'kWh' expire_after: 86400 device_class: energy state_class: total_increasing qos: 1 state_topic: "shellies/shellyem-/emeter/0/returned_energy" - platform: mqtt name: "EM - Phase A - Total Energy" value_template: "{{ value|float / 60000 }}" unit_of_measurement: 'kWh' expire_after: 86400 device_class: energy state_class: total_increasing qos: 1 state_topic: "shellies/shellyem-/emeter/0/total_energy" - platform: mqtt name: "EM - Phase A - Total Returned Energy" value_template: "{{ value|float / 60000 }}" unit_of_measurement: 'kWh' expire_after: 86400 device_class: energy state_class: total_increasing qos: 1 state_topic: "shellies/shellyem-/emeter/0/total_returned" - platform: mqtt name: "EM - Phase A - Power" unit_of_measurement: 'W' expire_after: 86400 device_class: power qos: 1 state_topic: "shellies/shellyem-/emeter/0/power" - platform: mqtt name: "EM - Phase A - Reactive Power" unit_of_measurement: 'W' expire_after: 86400 device_class: power qos: 1 state_topic: "shellies/shellyem-/emeter/0/reactive_power" - platform: mqtt name: "EM - Phase A - Voltage" unit_of_measurement: 'V' expire_after: 86400 device_class: voltage qos: 1 state_topic: "shellies/shellyem-/emeter/0/voltage" Binary Sensors ¶ Shelly H&T has an embedded Web Interface, which can be used to monitor and control the device, as well as adjust its settings.

The integration uses Device Name to name its entities if the device has only one relay or no relays at all.

sensors/energy/shelly_3em.yaml - platform: mqtt name: "3EM - Phase A - Energy" value_template: "{{ value|float / 60000 }}" # Wm to kWh unit_of_measurement: 'kWh' expire_after: 86400 device_class: energy state_class: total_increasing qos: 1 state_topic: "shellies/shellyem3-/emeter/0/energy" - platform: mqtt name: "3EM - Phase A - Returned Energy" value_template: "{{ value|float / 60000 }}" unit_of_measurement: 'kWh' expire_after: 86400 device_class: energy state_class: total_increasing qos: 1 state_topic: "shellies/shellyem3-/emeter/0/returned_energy" - platform: mqtt name: "3EM - Phase A - Total Energy" value_template: "{{ value|float / 60000 }}" unit_of_measurement: 'kWh' expire_after: 86400 device_class: energy state_class: total_increasing qos: 1 state_topic: "shellies/shellyem3-/emeter/0/total_energy" - platform: mqtt name: "3EM - Phase A - Total Returned Energy" value_template: "{{ value|float / 60000 }}" unit_of_measurement: 'kWh' expire_after: 86400 device_class: energy state_class: total_increasing qos: 1 state_topic: "shellies/shellyem3-/emeter/0/total_returned" - platform: mqtt name: "3EM - Phase A - Power" unit_of_measurement: 'W' expire_after: 86400 device_class: power qos: 1 state_topic: "shellies/shellyem3-/emeter/0/power" - platform: mqtt name: "3EM - Phase A - Voltage" unit_of_measurement: 'V' expire_after: 86400 device_class: voltage qos: 1 state_topic: "shellies/shellyem3-/emeter/0/voltage" - platform: mqtt name: "3EM - Phase A - Current" unit_of_measurement: 'A' expire_after: 86400 device_class: current qos: 1 state_topic: "shellies/shellyem3-/emeter/0/current" - platform: mqtt name: "3EM - Phase A - Power Factor" # If the PF is returned as a value between 0.0 and 1.0 # instead of a % value between 0 and 100 # uncomment the line below #value_template: "{{ value|float * 100 }}" unit_of_measurement: '%' expire_after: 86400 device_class: power_factor qos: 1 state_topic: "shellies/shellyem3-/emeter/0/pf" Binary Sensors ¶

WiFi-operated humidity and temperature sensor

It automatically recognizes new Shelly devices talking to the MQTT broker (after the Shelly’s been configured to use MQTT) and creates devices and entities for each of them. Generation 1 “Shelly 4Pro” and “Shelly Sense” are not supported (devices based on old CoAP v1 protocol) lights/room_x/lamps.yaml # Lamp room X - Shelly 1PM - platform: mqtt name: Room X - lamp payload_on: "on" payload_off: "off" qos: 1 state_topic: shellies/shelly1pm-[SHELLY ID]/relay/0 command_topic: shellies/shelly1pm-[SHELLY ID]/relay/0/command json_attributes_topic: shellies/shelly1pm-[SHELLY ID]/info ## /lights/room_y/lamps.yaml # Lamp room Ya - Shelly 2.5 - platform: mqtt name: Room Y - lamp A payload_on: "on" payload_off: "off" qos: 1 state_topic: shellies/shellyswitch25-[SHELLY ID]/relay/0 command_topic: shellies/shellyswitch25-[SHELLY ID]/relay/0/command json_attributes_topic: shellies/shellyswitch25-[SHELLY ID]/info # Lamp room Yb - Shelly 2.5 - platform: mqtt name: Room Y - lamp B payload_on: "on" payload_off: "off" qos: 1 state_topic: shellies/shellyswitch25-[SHELLY ID]/relay/1 command_topic: shellies/shellyswitch25-[SHELLY ID]/relay/1/command json_attributes_topic: shellies/shellyswitch25-[SHELLY ID]/info Binary sensors ¶ Once the Gen 2 become more readily available, and I get my hands on one or more of them, I may make a new post about the changes. Configuration file structure ¶