User Scripts examples: Difference between revisions
m (Fix the break lines of the article) |
m (Fixed the breaklines) |
||
Line 69: | Line 69: | ||
<code>done</code> | <code>done</code> | ||
''To use this script, replace the ‘DEVICE_FILE’, ‘SERVER_URL’, and ‘PAYLOAD’ variables with the appropriate values for your system and HTTP server.'' | ''To use this script, replace the ‘DEVICE_FILE’, ‘SERVER_URL’, and ‘PAYLOAD’ variables with the appropriate values for your system and HTTP server.'' | ||
Press the ‘esc’ on your keyboard to exit insert mode, then type :x, and press enter. | Press the ‘esc’ on your keyboard to exit insert mode, then type :x, and press enter. | ||
Line 107: | Line 108: | ||
This line uses '''‘ubus’''' command to call the '''‘ioman.gpio.onewire’''' service and execute the '''‘status’''' command. The output of this command is saved to the ''status'' variable. | This line uses '''‘ubus’''' command to call the '''‘ioman.gpio.onewire’''' service and execute the '''‘status’''' command. The output of this command is saved to the ''status'' variable. | ||
[[File:Networking trb user scripts cli code explanation1.png|left]] | [[File:Networking trb user scripts cli code explanation1.png|left]] | ||
Line 120: | Line 119: | ||
After that, it checks if the value stored in the '''‘value’''' variable is equal to 0. If it is, the '''‘ubus’''' command is used to call the '''‘ioman.gpio.onewire’''' service and execute the ‘update’ command, which updates the ‘value’ parameter to 1. | After that, it checks if the value stored in the '''‘value’''' variable is equal to 0. If it is, the '''‘ubus’''' command is used to call the '''‘ioman.gpio.onewire’''' service and execute the ‘update’ command, which updates the ‘value’ parameter to 1. | ||
[[File:Networking trb user scripts cli code explanation2.png|left]] | [[File:Networking trb user scripts cli code explanation2.png|left]] | ||
Line 133: | Line 130: | ||
This line sets the ‘BASE_DIR’ variable to the base directory for 1-wire devices. | This line sets the ‘BASE_DIR’ variable to the base directory for 1-wire devices. | ||
[[File:Networking trb user scripts cli code explanation3.png|left]] | [[File:Networking trb user scripts cli code explanation3.png|left]] | ||
Line 153: | Line 151: | ||
Which then converts the raw temperature value to degrees Celsius by dividing it by 1000 and then formatting it with two decimal places using '''‘printf’'''. The resulting temperature value is stored in the '''‘temp’''' variable. | Which then converts the raw temperature value to degrees Celsius by dividing it by 1000 and then formatting it with two decimal places using '''‘printf’'''. The resulting temperature value is stored in the '''‘temp’''' variable. | ||
[[File:Networking trb user scripts cli code explanation5.png|left]] | [[File:Networking trb user scripts cli code explanation5.png|left]] | ||
Line 160: | Line 160: | ||
These lines define the URL of the server to which the temperature data will be sent and the payload data that will be sent with each request. The payload includes the '''‘sensor_id’''' and '''‘temp’''' variables, formatted as a JSON object. | These lines define the URL of the server to which the temperature data will be sent and the payload data that will be sent with each request. The payload includes the '''‘sensor_id’''' and '''‘temp’''' variables, formatted as a JSON object. | ||
[[File:Networking trb user scripts cli code explanation6.png|left]] | [[File:Networking trb user scripts cli code explanation6.png|left]] | ||
Line 167: | Line 168: | ||
This line uses the '''‘curl’''' command to send an HTTP POST request to the server specified by '''‘$SERVER_URL’'''. The '''‘-X POST’''' option specifies that the request should be a POST request, and the '''‘-H “Content-Type: application/json”’''' option specifies that the payload data is in JSON format. The '''‘-d “$PAYLOAD”’''' option specifies the payload data to be sent with the request. | This line uses the '''‘curl’''' command to send an HTTP POST request to the server specified by '''‘$SERVER_URL’'''. The '''‘-X POST’''' option specifies that the request should be a POST request, and the '''‘-H “Content-Type: application/json”’''' option specifies that the payload data is in JSON format. The '''‘-d “$PAYLOAD”’''' option specifies the payload data to be sent with the request. | ||
[[File:Networking trb user scripts cli code explanation7.png|left]] | [[File:Networking trb user scripts cli code explanation7.png|left]] | ||
Line 174: | Line 177: | ||
=== Output === | === Output === | ||
[[File:Networking trb user scripts HTTP listener screenshot.png|left|800x800px]] | [[File:Networking trb user scripts HTTP listener screenshot.png|left|800x800px]] | ||
Revision as of 10:46, 6 April 2023
Introduction
User Scripts is a service in RUT routers that provides the user with the possibility to create custom shell scripts that run at the end of router's boot process.
This article will provide some examples on the usage of User Scripts. Although it must be noted that one should be at least be partially familiar with the syntax and basic principles of shell scripts beforehand as this guide will not provide a tutorial on shell scripts themselves.
Example 1: 1-Wire Data to Server for TRB141
Since there is no Web interface support for getting 1-wire data, it has to be accessed via SSH or Console modes. As of now, the Data to Server function for 1-wire sensor data can only be done by writing a custom script since there are no direct methods of storing this data.
This article will provide a step-by-step configuration on how to configure data to server using a custom script that allows 1-wire data to be sent on an HTTP server.
For the instruction on how to setup 1-Wire sensor with the TRB141 kindly navigate to this article that we have.
Writing the Script
Connect to the TRB141 CLI via SSH or WebUI.
Create a new directory for you to save the script that is to be created later. (Optional)
Navigate to it, then create a new sh file using the “vi” command followed by the filename of your choice. (Don’t forget to add the .sh extension at the end).
vi 1wire_script.sh
A text editor window will open and press the letter ‘i’ to enter insert mode.
Copy the provided code and paste it into your script file.
#!/bin/sh
# Capture output of ubus call ioman.gpio.onewire status command
status=$(ubus call ioman.gpio.onewire status)
# Parse value of "value" parameters
value=$(echo "$status" | grep -o '"value":[^,}]*' | sed 's/.*: *"\?\([^,"}]*\)"\?/\1/')
if [ "$value" -eq 0 ]; then
ubus call ioman.gpio.onewire update '{"value":"1"}'
fi
BASE_DIR="/sys/bus/w1/devices/"
do
# Iterate through each sensor directory
for sensor_dir in $BASE_DIR/28-*; do
sensor_id=$(basename $sensor_dir)
# Read temperature data from device file and filter it to display up to 2 decimal points
temp_raw=$(cat $sensor_dir/w1_slave | grep "t=" | awk -F"=" '{print $2}')
temp=$(echo "$temp_raw" | awk '{printf "%.2f", $1/1000}')
# Define HTTP server URL and payload data
SERVER_URL="192.168.2.227"
PAYLOAD="{\"SensorID\": \"$sensor_id\", \"temperature\": $temp}"
# Send temperature data to server using cURL
curl -X POST -H "Content-Type: application/json" -d "$PAYLOAD" $SERVER_URL
done
To use this script, replace the ‘DEVICE_FILE’, ‘SERVER_URL’, and ‘PAYLOAD’ variables with the appropriate values for your system and HTTP server. Press the ‘esc’ on your keyboard to exit insert mode, then type :x, and press enter.
Run the command: ‘chmod 777 <filename>’
to make the script executable on your end.
Code explanation
This line uses ‘ubus’ command to call the ‘ioman.gpio.onewire’ service and execute the ‘status’ command. The output of this command is saved to the status variable.
This block of code extracts the value of the ‘value’ parameter from the ‘status’ output using ‘grep’and ‘sed’ and stores it in the ‘value’ variable.
After that, it checks if the value stored in the ‘value’ variable is equal to 0. If it is, the ‘ubus’ command is used to call the ‘ioman.gpio.onewire’ service and execute the ‘update’ command, which updates the ‘value’ parameter to 1.
This line sets the ‘BASE_DIR’ variable to the base directory for 1-wire devices.
This line sets up a ‘for’ loop to iterate through all directories in ‘$BASE_DIR’ that start with ’28-‘, which is the prefix for 1-wire temperature sensors.
After that, it extracts the sensor ID from the sensor directory path using the ‘basename’ command and stores it in the ‘sensor_id’ variable.
This block reads the temperature data from the device file ‘$sensor_dir/w1_slave’ and extracts the raw temperature value using ‘grep’ and ‘awk’. The temperature value is encoded as an integer.
Which then converts the raw temperature value to degrees Celsius by dividing it by 1000 and then formatting it with two decimal places using ‘printf’. The resulting temperature value is stored in the ‘temp’ variable.
These lines define the URL of the server to which the temperature data will be sent and the payload data that will be sent with each request. The payload includes the ‘sensor_id’ and ‘temp’ variables, formatted as a JSON object.
This line uses the ‘curl’ command to send an HTTP POST request to the server specified by ‘$SERVER_URL’. The ‘-X POST’ option specifies that the request should be a POST request, and the ‘-H “Content-Type: application/json”’ option specifies that the payload data is in JSON format. The ‘-d “$PAYLOAD”’ option specifies the payload data to be sent with the request.
Output
Run the script by entering the file path of the file or ./<filename>.sh if you are in the same directory.
If configured correctly, you should be able to see the temperature data on your HTTP server.