Triggering dzVents script on string in logfile ? [Solved]

[hkemal]

Hello all,

I have a script in dzVents that controls the plugs for my TV and Hifi based on the changes of the Kodi hardware.
In a trigger section I have devices = { 'Kodi' }, so my script gets triggered every time Kodi changes value (domoticz.devices('Kodi').state == "Video", "Audio" etc.). This is working fine..
What I want now is to scrap what is being played and act on that. But my script doesn't get triggered when the played title changes, for example SongA changes to SongB. The event is visible in Domoticz Log (Kodi: Event "Song A") and is shown on UI, but this doesn't trigger my script.
How can I get the script triggered on this event in the log?

Regards
K

[waaren]

I have a script in dzVents that controls the plugs for my TV and Hifi based on the changes of the Kodi hardware.
In a trigger section I have devices = { 'Kodi' }, so my script gets triggered every time Kodi changes value (domoticz.devices('Kodi').state == "Video", "Audio" etc.). This is working fine..
What I want now is to scrap what is being played and act on that. But my script doesn't get triggered when the played title changes, for example SongA changes to SongB. The event is visible in Domoticz Log (Kodi: Event "Song A") and is shown on UI, but this doesn't trigger my script.
How can I get the script triggered on this event in the log?

The Kodi hardware module update the device directly in the database on a played title change and does not use the route via the event system. So you need a workaround to catch this event.

One way is to trigger a bash script via os.execute() in a script, -crontab or with nohup. watching the domoticz log, waiting for a certain string and have it fire a customEvent when the string is send to the log.

bash script to monitor log file and trigger dzVents script.

Code: Select all

#!/bin/bash
#
# signal dzVents about a set string in domoticz logfile
#

#
# linux commands/ programs used in this script: echo, curl, tail, grep, sed, xxd and tr
#
# tail -f -n0 $file &           -->> only look at lines appended to $file after starting this command in the background 
# grep -m1 "$string"            -->> stop when finding the first appearance of $string 
# echo -ne $string              -->> echo string without newline and enable interpretation of backslash escapes
# xxd -plain $string            -->> converts $string to hexdump
# tr -d '\n' $string            -->> remove newline from $string
# sed 's/\(..\)/%\1/g') $string -->> insert % before every pair of chars in $string 
# curl                          -->> call domoticz API

#
# Root required
#
if [[ $EUID -ne 0 ]]; then
   # This script must be run as root
   exit 1
fi

customEvent=kodiLogEvent                # customEvent that triggers your dzVents script
domoticzPort=8084                       # change to port number you use for domoticz
domoticzLog=/var/log/domoticz.log       # logging to OS file required 
string2watch="Kodi: Event"              # Your string to watch for

while true ; do  
	result=$( ( tail -f -n0 $domoticzLog & ) | grep -m1  "$string2watch" )
	urlEncodedResult=$(echo -ne $result | xxd -plain | tr -d '\n' | sed 's/\(..\)/%\1/g')

	curl "http://localhost:$domoticzPort/json.htm?type=command&param=customevent&event=$customEvent&data=$urlEncodedResult"
done

dzVents to receive the catched logline

Code: Select all

scriptVar = 'kodiLogEvent'

return
{
    on =
    {
        customEvents =
        {
            scriptVar,
        },
    },

    logging =
    {
        level = domoticz.LOG_DEBUG, -- set to LOG_ERROR when tested and OK
        marker = scriptVar,
    },

    execute = function(dz, item)
        local lodash = dz.utils._

        dz.log(item.trigger .. ' triggered this script ',dz.LOG_DEBUG)

        -- do not echo the whole string in the log or you will create a loop
        dz.log('payload is: '.. lodash.str(item.data:gsub('Kodi: Event','')),dz.LOG_DEBUG)

    end

}