SHEL Sensor H&T WIFI TF wh

Product Information

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 ¶ A perfect design combined with a battery lasting up to 16 months that keeps your home always comfortable.

Configuring a device as cover allows you to control things like blinds, curtains, shades, shutters, garage doors, …Shelly H&T is a smart temperature and humidity sensor, which can be remotely controlled and monitored through a mobile phone, tablet, PC, or home automation system. It can work standalone in a local Wi-Fi network or it can also be operated through cloud home automation services.

Water heating - Using Shelly Plus Add-on and two DS18B20 sensors, you can easily measure the precise temperature inside your aquarium, as well as the room temperature. Based on this data, you can maintain a comfortable and healthy environment for your pets. Additionally, you can connect a liquid level sensor to the Add-on, and always be sure that the water level is at its optimal level. Some devices, like the Shelly2.5 have multiple switch inputs and outputs. These need to be added individually. Light vs Switch setup ¶ For generation 2 hardware it’s possible to select if a device’s input is connected to a button or a switch. Binary sensors are created only if the input mode is set to switch. When the input is of type button you need to use events for your automations. Event entities (generation 1) 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. Shelly H&T can be accessed, controlled, and monitored remotely from any place where the User has internet connectivity, as long as the device is connected to a Wi-Fi router and the Internet.When you’re working with MQTT in Home Assistant, you’ll know that it does require some manual configuration. If the BUTTON TYPE of the switch connected to the device is set to momentary or detached switch, the integration creates an event entity for this switch. You can use this entity in your automations. Event entities (generation 2) 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 ¶ So you no longer need to add a new config for each device you added and all entities are nicely grouped per device from the start. If the Input Mode of the switch connected to the device is set to Button, the integration creates an event entity for this switch. You can use this entity in your automations. Events

Shelly H&T is the worst H&T out there. I’ve got 4 of them in my house and they are just atrocious. I was looking up for a way to flash them with ESPHome but apparently Alterco refuses to share the GPIO pinouts. If Home Assistant is running as a virtual machine or service on an operating system other than Home Assistant OS, you should open UDP port 5683 on the device’s firewall and/or ensure that communication from this port is redirected to the Home Assistant service.sensors/room_x/lamp.yaml # Input type - platform: mqtt name: Room X - lamp - input expire_after: 86400 qos: 1 state_topic: shellies/shelly1pm-[SHELLY ID]/input_event/0 # Device temperature °C - platform: mqtt name: Room X - lamp - temperature expire_after: 86400 qos: 1 device_class: temperature unit_of_measurement: '°C' icon: mdi:temperature-celcius state_topic: shellies/shelly1pm-[SHELLY ID]/temperature # Device temperature °F - platform: mqtt name: Room X - lamp - temperature F expire_after: 86400 qos: 1 device_class: temperature unit_of_measurement: '°F' icon: mdi:temperature-fahrenheit state_topic: shellies/shelly1pm-[SHELLY ID]/temperature_f # Power consumption (live) - platform: mqtt name: Room X - lamp - power expire_after: 86400 qos: 1 device_class: power unit_of_measurement: 'W' icon: mdi:lightning-bolt-outline state_topic: shellies/shelly1pm-[SHELLY ID]/relay/0/power # Power consumption (since reboot) - platform: mqtt name: Room X - lamp - energy expire_after: 86400 qos: 1 device_class: energy state_class: total_increasing unit_of_measurement: 'Wh' value_template: "{{ value | float / 60 }}" icon: mdi:lightning-bolt state_topic: shellies/shelly1pm-[SHELLY ID]/relay/0/energy # Overpower - platform: mqtt name: Room X - lamp - overpower expire_after: 86400 qos: 1 device_class: power unit_of_measurement: 'W' icon: mdi:flash-alert state_topic: shellies/shelly1pm-[SHELLY ID]/overpower_value External sensors ¶ Espcially if you’re wanting to do ’non-default’ integrations (e.g. use some templating to modify values). switches/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 ¶

platform: mqtt name: Rolling Shutters - switch open payload_on: 1 payload_off: 0 state_topic: shellies/shellyswitch25-/input/0 - platform: mqtt name: Rolling Shutters - switch close payload_on: 1 payload_off: 0 state_topic: shellies/shellyswitch25-/input/1 - platform: mqtt name: Rolling Shutters - overtemperature payload_on: 1 payload_off: 0 state_topic: shellies/shellyswitch25-/overtemperature - platform: mqtt name: Rolling Shutters - firmware available payload_on: true payload_off: false value_template: "{{ value_json.new_fw }}" state_topic: shellies/shellyswitch25-/announce sensor: The integration uses the following strategy to name its entities if the device has more than one relay: Control your lights based on luminousity - Together with an LDR (photoresistor), Shelly Plus Add-on can trigger Shelly Plus 2PM to open the blinds when the room is too dark and it's still daytime. Additionally, when luminosity is low, Shelly Plus Add-on can trigger Shelly Plus 1 to turn on the lights at just the right time. Generation 1 “Shelly 4Pro” and “Shelly Sense” are not supported (devices based on old CoAP v1 protocol) I won’t write a tutorial on doing this, as all required information can be found in the ha-shellies-discovery documentation.Garage door position - You can connect a reed-switch sensor to Shelly Plus Add-on's digital sensor and follow the state of your garage door. This way, you will always know whether it is open or closed when you're away and take appropriate action. sensors/room_x/floorlamp.yaml # Power consumption - platform: mqtt name: Room X - floorlamp - power qos: 1 expire_after: 86400 device_class: power unit_of_measurement: 'W' icon: mdi:lightning-bolt-outline state_topic: shellies/shellyplug-s-[SHELLY ID]/relay/0/power # Energy consumption - platform: mqtt name: Room X - floorlamp - energy qos: 1 expire_after: 86400 device_class: energy state_class: total_increasing unit_of_measurement: 'Wh' value_template: "{{ value | float / 60 }}" icon: mdi:lightning-bolt-outline state_topic: shellies/shellyplug-s-[SHELLY ID]/relay/0/energy # Overpower value - platform: mqtt name: Room X - floorlamp - overpower qos: 1 expire_after: 86400 device_class: power unit_of_measurement: 'W' icon: mdi:flash-alert-outline state_topic: shellies/shellyplug-s-[SHELLY ID]/overpower_value # Temperature °C (Shelly Plug S only) - platform: mqtt name: Room X - floorlamp - temperature qos: 1 expire_after: 86400 device_class: temperature unit_of_measurement: '°C' icon: mdi:temperature-celsius state_topic: shellies/shellyplug-s-[SHELLY ID]/temperature # Temperature °F (Shelly Plug S only) - platform: mqtt name: Room X - floorlamp - temperature qos: 1 expire_after: 86400 device_class: temperature unit_of_measurement: '°F' icon: mdi:temperature-fahrenheit state_topic: shellies/shellyplug-s-[SHELLY ID]/temperature_f Shelly DW2 ¶ If only the device name is set, and the device has multiple channels, the channel number will be appended to the entity name (e.g., Channel 2). Just note that the 2.5 has 2 switch inputs and 2 relay outputs, so you’d need to duplicate configs specific to those, one linked to input/relay 0 and to other to input/relay 1. customize_domain: ! include customisations/customize_domain.yaml customize_glob: ! include customisations/customize_glob.yaml customize: ! include customisations/customize.yaml automation: ! include automations.yaml group: ! include group.yaml script: ! include scripts.yaml binary_sensor: ! include_dir_merge_list binsensors/ light: include_dir_merge_list lights/ sensor: include_dir_merge_list sensors/ switch: include_dir_merge_list switchess/ MQTT Templates ¶