The on and off scripts launch 4 times

[Jeffo31350]

I use a python script with a command tail of "0" for off, "1" for on and "2 for status. Both the on and off versions execute 4 time each in rapid succession whereas the status version only executes once. I have modified my server code to deal with these multiple connections but is there an option to modify this behaviour in the plugin config.
Cheers
Phil

[pponce]

HI,
Since i no longer use this plugin i don't want to make updates that i can't test easily to insure that nothing breaks.
But I think you can achieve what you want (maybe you already did something like this) by creating a script like the below that executes any custom script you want.
Create this "lockWrapperScript.sh" script.

#!/bin/bash

# Define the script you actually want to run
TARGET_SCRIPT="$1"
# Define a unique lock file path
LOCKFILE="/tmp/homebridge_script.lock"

# 1. Check if the lock file exists
if [ -e "$LOCKFILE" ]; then
    # Optional: Check if the process is actually still alive 
    # (prevents stale locks if the system crashed)
    PID=$(cat "$LOCKFILE")
    if ps -p $PID > /dev/null; then
        echo "Script is already running (PID: $PID). Exiting."
        exit 0
    fi
fi

# 2. Create the lock file with current Process ID
echo $$ > "$LOCKFILE"

# 3. Execute your actual script
# We use "shift" to pass any extra arguments (like 'on' or 'off')
shift
bash "$TARGET_SCRIPT" "$@"

# 4. Remove the lock file when finished
rm -f "$LOCKFILE"

Then for the plugin config you can instead of configuring your script like this:
"on": "/var/lib/homebridge/scripts/light_on.sh"
Configure it like this below:
"on": "/path/to/lockWrapperScript.sh /var/lib/homebridge/scripts/light_on.sh"

[Jeffo31350]

Hi and thanks for your prompt reply. I had already implemented a trap in my code to deal with multiple launches of the scripts. I was just interested if there was config issue I was unaware of. Many thanks for your help.
Kind regards.
Phil