SHEL Sensor H&T WIFI TF wh

Product Information

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 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. platform: mqtt name: Rolling Shutters - Calibrate command_topic: shellies/shellyswitch25-/roller/0/command payload_on: rc - platform: mqtt name: Rolling Shutters - FW upgrade command_topic: shellies/shellyswitch25-/command payload_on: update_fw binary_sensor: 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).

However, it’s just a matter of setting the correct platform and/or adding the config in the right file for your Shelly to be configured as switch, cover, … Shelly relays (1, 1PM, 1L, 2.5) ¶ Shelly Plus Add-on (the Device) is a galvanically isolated sensor interface to the Shelly Plus devices. Main applications Espcially if you’re wanting to do ’non-default’ integrations (e.g. use some templating to modify values).The integration offers device services which can be triggered by a configuration button. OTA firmware update In Home Assistant, devices can be configured as a switch, which gives you simple on/off capabilities. 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. Copy the all parts in the config for Phase A and replace emeter/0 with emeter/1 or emeter/2 for Phase B and Phase C respectively. 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:

But you can also configure a device as light, which will also give you control over brightness and colour temp, if the device supports it. After I’ve bought them I started to build my own H&T sensors making use of ESP32 Dev Kit V4.1 and integrating it into ESPHOME with HASS. It works out more than 50% cheaper and stable from the bat off. Reply A perfect design combined with a battery lasting up to 16 months that keeps your home always comfortable. 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 ¶Also note the small difference in the model naming when entering the MQTT topic for the Shelly Plug and Shelly Plugs S ( shellyplug / shellyplug-s). Light vs Switch setup ¶

Some time ago I switched from manually adding Shelly devices via MQTT configurations to an automated script: ha-shellies-discovery. When you’re working with MQTT in Home Assistant, you’ll know that it does require some manual configuration.

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 ¶ Using the configurations examples below to manually add Shelly devices via MQTT is still a valid option. 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 ¶

With the introduction of the Shelly 4Pro PM also came the introduction of a new generation of devices.If Channel Name is set in the device, the integration will use it to generate the entities’ name, e.g. Kitchen Light