Ok, I’ve managed to get most of what I want, I just can’t figure out how to trigger it now.
File is executable:
-rwxr-xr-x 1 root root 418 Apr 12 14:59 /config/speedtest-net/mqtt_pub.sh
Contents:
#!/bin/bash
broker="192.168.1.221"
username="username_here"
password="password_here"
topic="homeassistant/sensor/speedtest-net"
message="`/config/speedtest-net/speedtest --accept-license --server-id=14335 --format=json`"
mosquitto_pub -h "$broker" -u "$username" -P "$password" -t "$topic" -m "$message"
When I run this from SSH it works flawlessly, pushes the data to MQTT and then a bunch of sensors I wrote pick them up perfectly!
So I tried to make an automation to call the shell command that works when I run it manually:
# Call script which publishes readings to MQTT
shell_command:
speedtest_net_run_test: '/config/speedtest-net/mqtt_pub.sh'
automation:
# Run the test on startup, and hourly
- alias: speedtest_net_run_test
trigger:
- platform: homeassistant
event: start
- platform: time_pattern
minutes: 0
action:
service: shell_command.speedtest_net_run_test
When the automation triggers, I get error code 127.
I’m out of ideas…I even tried at one point hard coding the full path to the mosquitto_pub command and it still didn’t like it. I even tried simply “touching” a file from my script, and that was fine…seems to be somehow it just really doesn’t want to correctly do the pub?
Maybe this is an easier problem to fix?
EDIT: I’ve finally found this post which tells how to use the console to get to the actual hassio environment (WOW what an undocumented PITA, how does anyone dev anything without knowing the environment?)
So it looks like the mosquieto pub executable is missing somehow? Why? How do I fix that?
EDIT2: I managed to make it run by randomly copying libs and executables into my /config area and forcing LD_LIBRARY_PATH…but this can’t be remotely the right way of doing things. I need to figure out how to make it actually work semi-correctly