Simple sprinkler on/off via http

scanwinder · December 21, 2024, 4:31am

Hi,

I’m very new to home assistant and the first device i’m trying to setup is a remote relay board which turns sprinklers on and off. I think i’ve managed to set one of the relays up in configuration.yaml but, I have no idea how i can then trigger it via the home assistant interface.

I’ve found documentation on how to set it up in configuration.yaml - but no idea where to from there, it doesn’t appear in devices or integrations in the home assistant interface? I’m not sure if this suggests it doesn’t work, or i’m supposed to look elsewhere?

Any help even if it’s pointing me at the correct documentation would be much appreciated.

Here’s my configuration.yaml:

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

switch:
  - platform: command_line
    switches:
      axis:
        friendly_name: 'Sprinkler'
        command_on: 'curl -k "http://192.168.1.48/?relay1=off"'
        command_off: 'curl -k "http://192.168.1.48/?relay1=on"'

tom_l · December 21, 2024, 4:35am

You need to restart home assistant after adding that configuration.

Add the switch to a dashboard card and turn the switch on.

scanwinder · December 21, 2024, 6:12am

It actually looks like I do have an error in the log:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 366, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/usr/src/homeassistant/homeassistant/components/command_line/switch.py", line 43, in async_setup_platform
    slugify(discovery_info[CONF_NAME]): discovery_info
            ~~~~~~~~~~~~~~^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable

I found a github page talking about this error here:

github.com/home-assistant/core

Command Line switch stop working

opened 09:27PM - 01 Jan 24 UTC

closed 09:19AM - 02 Jan 24 UTC

w3corp

integration: command_line

### The problem I have a switch that activates my Proxmox's CPU performance m…ode, but it stopped working after an update. I don't know exactly which version it no longer worked in, but I believe it happened at the beginning of December. I did the tests trying to execute the commands via SSH from Home Assistant SSH and Terminal Addon and the command is executed successfully. I've also tried making the command "simpler", keeping only the essential to work as well as creating an auxiliary sensor but the error persists. I am sending my code and logs in the fields below. ### What version of Home Assistant Core has the issue? core-2023.12.4 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue _No response_ ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml switch: - platform: command_line switches: proxmox_power_performance: #https://community.home-assistant.io/t/psa-how-to-configure-proxmox-for-lower-power-usage/323731/17 friendly_name: Proxmox Power Performance unique_id: proxmox_power_performance command_on: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /config/.ssh/id_rsa [email protected] 'echo "performance" | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor' command_off: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /config/.ssh/id_rsa [email protected] 'echo "powersave" | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor' command_state: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /config/.ssh/id_rsa [email protected] 'cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor | grep -oc "performance"' icon_template: >- {% if states('switch.proxmox_power_performance') == on %} mdi:speedometer {% else %} mdi:speedometer-slow {% endif %} ``` ### Anything in the logs that might be useful for us? ```txt Logger: homeassistant.components.switch Source: helpers/entity_platform.py:361 Integration: Interruptor (documentation, issues) First occurred: 18:15:01 (1 occurrences) Last logged: 18:15:01 Error while setting up command_line platform for switch Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 361, in _async_setup_platform await asyncio.shield(task) File "/usr/src/homeassistant/homeassistant/components/command_line/switch.py", line 42, in async_setup_platform entities: dict[str, Any] = {slugify(discovery_info[CONF_NAME]): discovery_info} ~~~~~~~~~~~~~~^^^^^^^^^^^ TypeError: 'NoneType' object is not subscriptable ``` ### Additional information Here´s tha log for the sensor i´ve tried to test: Logger: homeassistant.components.sensor Source: helpers/entity_platform.py:361 Integration: Sensor (documentation, issues) First occurred: 18:14:56 (1 occurrences) Last logged: 18:14:56 Error while setting up command_line platform for sensor Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 361, in _async_setup_platform await asyncio.shield(task) File "/usr/src/homeassistant/homeassistant/components/command_line/sensor.py", line 66, in async_setup_platform name: str = sensor_config[CONF_NAME] ~~~~~~~~~~~~~^^^^^^^^^^^ TypeError: 'NoneType' object is not subscriptable

The last comment seems to suggest that this was because configuration syntax changed at some point. I try using the example in the linked documentation ( Command line - Home Assistant ) but now i get a different error:

Invalid config for ‘command_line’ at configuration.yaml, line 22: expected a dictionary for dictionary value ‘command_line->0->switch’, got None, please check the docs at Invalid config for ‘command_line’ at configuration.yaml, line 23: ‘name’ is an invalid option for ‘command_line’, check: command_line->0->name, please check the docs at Invalid config for ‘command_line’ at configuration.yaml, line 24: ‘command_on’ is an invalid option for ‘command_line’, check: command_line->0->command_on, please check the docs at Invalid config for ‘command_line’ at configuration.yaml, line 25: ‘command_off’ is an invalid option for ‘command_line’, check: command_line->0->command_off, please check the docs at

My current configuration is:

command_line:
 - switch:
   name: Sprinkler
   command_on: curl -k "http://192.168.1.48/relay1=off"
   command_off: curl -k "http://192.168.1.48/relay1=on"

tom_l · December 21, 2024, 6:32am

Watch your indentation. It is important. See the example here: https://www.home-assistant.io/integrations/command_line#example-switch-platform

command_line:
 - switch:
     name: Sprinkler
     command_on: curl -k "http://192.168.1.48/relay1=off"
     command_off: curl -k "http://192.168.1.48/relay1=on"