switches/energy/shelly_3em.yaml - platform: mqtt name: "3EM - Relay" expire_after: 604800 qos: 1 command_topic: "shellies/shellyem3-/relay/0/command" state_topic: "shellies/shellyem3-/relay/0" # Remove the line below if the value_template doesn't function properly value_template: {{ 'on' if value == 'on' else 'off' }} # Test for capturing 'overpower' state - platform: mqtt name: "3EM - Phase A - Reset Totals" expire_after: 604800 qos: 1 optimistic: true payload_on: "reset_totals" payload_off: "" command_topic: "shellies/shellyem3-/emeter/0/command" - platform: mqtt name: "3EM - Reset Device Data" expire_after: 604800 qos: 1 optimistic: true payload_on: "reset_data" payload_off: "" command_topic: "shellies/shellyem3-/command" Shelly 4Pro ¶

In case device name and channel names are not set, the entity name will be generated by the Device Type, Device ID and Channel Number. 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 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 Applications that can benefit from this feature include HVAC environmental controls, temperature monitoring systems inside buildings, equipment or machinery and process monitoring and control systems Features and Functionality: 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.When you’re working with MQTT in Home Assistant, you’ll know that it does require some manual configuration. If you can’t find the CoIoT peer settings in the device’s web panel, it’s probably using an ancient firmware version, and you should update it to the current one. The integration uses Device Name to name its entities if the device has only one relay or no relays at all. Some devices, like the Shelly2.5 have multiple switch inputs and outputs. These need to be added individually. Light vs Switch setup ¶ 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 compatible

For an introduction on MQTT for Shelly devices, see my blog post: Getting started with MQTT and Home Assistant (and Shelly). shellies-discovery ¶ 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. 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: 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) 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.The integration offers device services which can be triggered by a configuration button. OTA firmware update I won’t write a tutorial on doing this, as all required information can be found in the ha-shellies-discovery documentation. 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).