# Use MariaDB in a Docker Container as the Recorder Database
recorder:
  db_url: mysql://username:password()@127.0.0.1:3307/homeassistant?charset=utf8mb4
  commit_interval: 1
  purge_keep_days: 365
  auto_purge: true

# Use MariaDB in a Docker Container as the Recorder Database
recorder:
  db_url: mysql://username:password()@127.0.0.1:3307/homeassistant?charset=utf8mb4
  commit_interval: 1
  purge_keep_days: 365
  auto_purge: true

# Connect to InfluxDB2.8 for metrics
influxdb:
  api_version: 2
  host: 192.168.1.XXX
  port: 8086
  token: "************************************************************************"
  organization: "home"
  bucket: "homeassistant"
  ssl: false
  verify_ssl: false

# Connect to InfluxDB2.8 for metrics
influxdb:
  api_version: 2
  host: 192.168.1.XXX
  port: 8086
  token: "************************************************************************"
  organization: "home"
  bucket: "homeassistant"
  ssl: false
  verify_ssl: false

panel_custom:
  - name: Automations
    sidebar_title: Automations
    sidebar_icon: mdi:cog-transfer
    js_url: /api/hassio/app/entrypoint.js
    url_path: config/automation/dashboard
    embed_iframe: true
    require_admin: true
    config:
      ingress: core_configurator
  - name: Devices
    sidebar_title: Devices
    sidebar_icon: mdi:devices
    js_url: /api/hassio/app/entrypoint.js
    url_path: config/devices/dashboard
    embed_iframe: true
    require_admin: true
    config:
      ingress: core_configurator
  - name: Scenes
    sidebar_title: Scenes
    sidebar_icon: mdi:palette
    js_url: /api/hassio/app/entrypoint.js
    url_path: config/scene/dashboard
    embed_iframe: true
    require_admin: true
    config:
      ingress: core_configurator
  - name: Areas
    sidebar_title: Areas
    sidebar_icon: mdi:home-circle-outline
    js_url: /api/hassio/app/entrypoint.js
    url_path: config/areas/dashboard
    embed_iframe: true
    require_admin: true
    config:
      ingress: core_configurator
  - name: develop_states
    sidebar_title: States
    sidebar_icon: mdi:state-machine
    url_path: 'config/developer-tools/state'
    module_url: /api/hassio/app/entrypoint.js
    embed_iframe: true
    require_admin: true 
  - name: panel_develop
    sidebar_title: Developer Tools
    sidebar_icon: mdi:hammer
    url_path: 'config/developer-tools/yaml'
    module_url: /api/hassio/app/entrypoint.js
    embed_iframe: true
    require_admin: true
  - name: panel_develop
    sidebar_title: Helpers
    sidebar_icon: mdi:tools
    url_path: 'config/helpers'
    module_url: /api/hassio/app/entrypoint.js
    embed_iframe: true
    require_admin: true 
  - name: panel_boiler_switch
    sidebar_title: Boiler Switch Log
    sidebar_icon: mdi:toggle-switch-variant-off
    url_path: 'logbook?entity_id=switch.boiler_control_relay'
    module_url: /api/hassio/app/entrypoint.js
    embed_iframe: true
    require_admin: true 
  - name: node-red
    sidebar_title: Node Red
    sidebar_icon: si:nodered
    module_url: /local/panel-redirect.js
    config:
      target: "http://192.168.1.XXX:1880"

panel_custom:
  - name: Automations
    sidebar_title: Automations
    sidebar_icon: mdi:cog-transfer
    js_url: /api/hassio/app/entrypoint.js
    url_path: config/automation/dashboard
    embed_iframe: true
    require_admin: true
    config:
      ingress: core_configurator
  - name: Devices
    sidebar_title: Devices
    sidebar_icon: mdi:devices
    js_url: /api/hassio/app/entrypoint.js
    url_path: config/devices/dashboard
    embed_iframe: true
    require_admin: true
    config:
      ingress: core_configurator
  - name: Scenes
    sidebar_title: Scenes
    sidebar_icon: mdi:palette
    js_url: /api/hassio/app/entrypoint.js
    url_path: config/scene/dashboard
    embed_iframe: true
    require_admin: true
    config:
      ingress: core_configurator
  - name: Areas
    sidebar_title: Areas
    sidebar_icon: mdi:home-circle-outline
    js_url: /api/hassio/app/entrypoint.js
    url_path: config/areas/dashboard
    embed_iframe: true
    require_admin: true
    config:
      ingress: core_configurator
  - name: develop_states
    sidebar_title: States
    sidebar_icon: mdi:state-machine
    url_path: 'config/developer-tools/state'
    module_url: /api/hassio/app/entrypoint.js
    embed_iframe: true
    require_admin: true 
  - name: panel_develop
    sidebar_title: Developer Tools
    sidebar_icon: mdi:hammer
    url_path: 'config/developer-tools/yaml'
    module_url: /api/hassio/app/entrypoint.js
    embed_iframe: true
    require_admin: true
  - name: panel_develop
    sidebar_title: Helpers
    sidebar_icon: mdi:tools
    url_path: 'config/helpers'
    module_url: /api/hassio/app/entrypoint.js
    embed_iframe: true
    require_admin: true 
  - name: panel_boiler_switch
    sidebar_title: Boiler Switch Log
    sidebar_icon: mdi:toggle-switch-variant-off
    url_path: 'logbook?entity_id=switch.boiler_control_relay'
    module_url: /api/hassio/app/entrypoint.js
    embed_iframe: true
    require_admin: true 
  - name: node-red
    sidebar_title: Node Red
    sidebar_icon: si:nodered
    module_url: /local/panel-redirect.js
    config:
      target: "http://192.168.1.XXX:1880"

# Expose the Boiler Switch as a Sensor for Graphing
template:
  - sensor:
      - name: "Numeric Boiler Relay State"
        unique_id: numeric_boiler_relay_state
        unit_of_measurement: "%"
        state_class: measurement
        state: >
          {% if is_state('switch.boiler_control_relay', 'on') %}
            100
          {% elif is_state('switch.boiler_control_relay', 'off') %}
            0
          {% else %}
            0
          {% endif %}

# Expose the Boiler Switch as a Sensor for Graphing
template:
  - sensor:
      - name: "Numeric Boiler Relay State"
        unique_id: numeric_boiler_relay_state
        unit_of_measurement: "%"
        state_class: measurement
        state: >
          {% if is_state('switch.boiler_control_relay', 'on') %}
            100
          {% elif is_state('switch.boiler_control_relay', 'off') %}
            0
          {% else %}
            0
          {% endif %}

http://192.168.1.XXX:8090/v1/qrcodelink?device_name=signal-api

http://192.168.1.XXX:8090/v1/qrcodelink?device_name=signal-api

curl -X POST -H "Content-Type: application/json" 'http://192.168.1.100:8090/v2/send' -d '{"message": "Hello World", "number": "+44XXXXXXXXXX", "recipients": [ "+44XXXXXXXXXX" ]}

curl -X POST -H "Content-Type: application/json" 'http://192.168.1.100:8090/v2/send' -d '{"message": "Hello World", "number": "+44XXXXXXXXXX", "recipients": [ "+44XXXXXXXXXX" ]}

# Signal Notifications
notify:
  - name: signal
    platform: signal_messenger
    url: "http://192.168.1.XXX:8090"
    number: "+440000000000"
    recipients:
      - "+449999999999"
  - name: signal_alert
    platform: signal_messenger
    url: "http://192.168.1.XXX:8090"
    number: "+440000000000"
    recipients:
      - "group.***********************************************************="
  - name: signal_log
    platform: signal_messenger
    url: "http://192.168.1.XXX:8090"
    number: "+440000000000"
    recipients:
      - "group.***********************************************************="
  - name: signal_debug
    platform: signal_messenger
    url: "http://192.168.1.XXX:8090"
    number: "+440000000000"
    recipients:
      - "group.***********************************************************="

# Signal Notifications
notify:
  - name: signal
    platform: signal_messenger
    url: "http://192.168.1.XXX:8090"
    number: "+440000000000"
    recipients:
      - "+449999999999"
  - name: signal_alert
    platform: signal_messenger
    url: "http://192.168.1.XXX:8090"
    number: "+440000000000"
    recipients:
      - "group.***********************************************************="
  - name: signal_log
    platform: signal_messenger
    url: "http://192.168.1.XXX:8090"
    number: "+440000000000"
    recipients:
      - "group.***********************************************************="
  - name: signal_debug
    platform: signal_messenger
    url: "http://192.168.1.XXX:8090"
    number: "+440000000000"
    recipients:
      - "group.***********************************************************="

http://192.168.1.XXX:8090/v1/groups/+44XXXXXXXXXX

http://192.168.1.XXX:8090/v1/groups/+44XXXXXXXXXX

Applications

Study Power

Between the electronics desk with all of my test and measurement equipment, and my PC with all of its peripherals, I have many devices plugged into the mains. I have sockets all over the place to avoid the use of power strips / multi-way extension cords.

In the photo above, the boxes are not all mains sockets – there are a number of USB, speaker, ethernet and other outlets.

See the Study & Electronics Lab panorama for the bigger picture.

It would not be feasible to switch individual sockets on and off every day, and I am not prepared to leave all this equipment on permanently for two reasons: Fire risk and wasted energy. To allow me to switch all sockets on or off at once (without simply switching the RCBO in the consumer unit off), I installed a small consumer unit with 3 20A contactors (essentially high power relays), controlled by 3 Shelly relays. Each contactor serves a radial 4mm² circuit.

The mains sockets are split into 3 zones: Main PC desk; electronics desk and all sockets down the left along the windows. I can now switch zones on and off as necessary from the panel itself, my phone, or any Shelly enabled button or control panel.

Study Lights

When I did the garage conversion, I added a control cabinet into the utility storage cupboards side of the partition wall to house the shelly devices.

The cables for the 3 banks of spotlights for the study feed into the top of the cabinet, along with live and neutral. When I was young I worked as an industrial control panel wirer, and I was able to use those skills here to layout the Shelly devices and wire them up. Using connection blocks is standard and allows me to remove the back-tray if required.

Interestingly the WiFi signal has no problem getting through the metal enclosure, although I do have a WiFi extender close by. It will definitely attenuate the signal to a degree though. The dimmers in the below photo have an RSSI of between -45dBm and -60dBm, which is significantly higher than the advised lower limit of -80dBm, and within the -30dBm to -67dBm window for reliable operation.

The cables exiting from the right-hand of the back-tray and through the bottom go to the switch panel on the other side of the wall.

The final product. The first 6 buttons from the top left control the 3 banks of lights directly. The remaining buttons are programmable and can activate scenes or automations, or anything else I configure. They connect to Shelly i4s, which are devices that simply handle button pushes and relay that information to Home Assistant to be assigned a function.

Simplified diagram of one bank of lights:

Study Desk Lights & Controls

For the desks I have RGBW LED strip lighting, controlled by a Shelly RGBW 2 controller. I have a strip running underneath the top shelf as well as along the ceiling behind a wooden beam. This provides a nice backlight for my monitors, considering the windows are behind me to my left.

Mounted on the shelf support above my monitor are 16 buttons wired to four Shelly i4 DC devices. These are powered by the LED strip power supply, which is overrated so can power the additional load with ease – not that they draw much current anyway.

These control both the LED strip lights and the main lighting. Each button triggers a Home Assistant scene, and thanks to Shelly’s multi-action support – single press, double press, triple press, and long press – each button can activate up to four distinct scenes. To keep things intuitive, I typically assign one button to control a specific light group, while the alternate press types adjust brightness levels.

The larger middle button with the blue LED ring is the power button and LED for my PC, which is hidden in a ventilated cupboard down to the left under the desk.

I have a smaller set of controls with one Shelly i4 DC above the electronics bench to control the main lights above the desk, the under-shelf strip lights and the shelf-mounted spotlights.

Dining Room Controls

I have installed and configured a Shelly Wall Display to show my Home Assistant dashboard, giving me full control over lighting and scenes for any device in the house. I’m planning to add Shelly TRVs to manage the radiators, and once I’ve configured heating zones and schedules, I’ll be able to control those from the display too. I of course also have access to Home Assistant on my phone.

To the right of the Shelly Wall Display are the directly connected home-made buttons for the dimmers and relays (these are well earthed!). It’s prudent to have these available in case the Home Assistant server (Raspberry PI) goes down, and to be honest it is much easier switching the light on and off with a dedicated button. The top and bottom buttons control the dimmer for the spotlights, and the middle button controls the relay for the chandeliers. There are 3 sub-rooms (open plan), therefore 3 sets of buttons.

Dining Room Wall Unit

I built a wall unit in the dining room, which features recessed RGBW LED strip lighting under each shelf, controlled by a Shelly RGBW2 and an amplifier, as the power demand is greater than what the RGBW controller can provide natively. This version of the Shelly RGBW2 accommodated potentiometers for controlling the 4 channels. The firmware allows for overriding the potentiometer values and vice versa, so whatever control method you use overrides the other.

Hive Heating Replacement

See my Hive Heating Replacement project for details of how I replaced Hive with Home Assistant and Shelly TRVs (thermostatic radiator valves).