MythTV System Events
MythTV System Events are a new feature in MythTV 0.23. Historically MythEvents have been used to communicate between components of the system when blocking was not required for proper operation. Now it is possible for the end user to tap into a number of events as well as defining up to ten keypress events. These events are handled by running an external script with appropriate parameters. MythTV System Events are configured on a per box basis so each machine can have it's own system specific handlers.
These are the currently defined events:
- Recording pending
- Recording started
- Recording finished
- Recording deleted
- Recording expired
- Playback started
- Playback stopped
- Playback paused
- Playback unpaused
- Playback program changed
- Master backend started
- Master backend shutdown
- Client connected to master backend
- Client disconnected from master backend
- Slave backend connected to master
- Slave backend disconnected from master
- Network Control client connected
- Network Control client disconnected
- mythfilldatabase ran
- Scheduler ran
- Settings cache cleared
These events are all sent automatically when the appropriate condition is met, but it is also possible to send events from the command line, for example:
mythbackend --systemevent USER_1
sends the first user event to whatever handler has been defined for that event.
Defining event handlers
Events handlers are edited in the System Events section in mythtv-setup. Select the event you would like to edit in the event list and then type in the script path and name followed by any parameters that you would like to pass to the script. For example to run a script whenever a recording is pending you could select the "Recording pending" event and type:
That script could be a priming script to get a set top box out of it's sleep mode:
#!/bin/bash flock -x /tmp/chch.lock DEVICE="--address=cherry:5000" REMOTE_NAME=dish1 irsend $DEVICE SEND_ONCE $REMOTE_NAME select echo "Sent priming shortly before %1" >> /tmp/priming-debug.log
Parameters available to event handlers
The parameters that it is possible to pass to an event depends on the event.
Recording events have the following substitutions available:
- %DIR% -- Recording directory, may be undefined prior to recording start
- %FILE% -- Recording file, may be undefined prior to recording start
- %TITLE% -- Program title, may be undefined
- %SUBTITLE% -- Program subtitle, may be undefined
- %DESCRIPTION% -- Program title, may be undefined
- %CATEGORY% -- Program subject category, may be undefined
- %HOSTNAME% -- Backend which will or is handling the recording
- %RECGROUP% -- Recording group for recording
- %PLAYGROUP% -- Play group for recording
- %CHANID% -- Channel ID (for database lookups of tuning data)
- %STARTTIME% %STARTTIMEISO% %STARTTIMEISOUTC% -- Recording start time (estimated)
- %ENDTIME% %ENDTIMEISO% %ENDTIMEISOUTC% -- Recording end time (estimated)
- %PROGSTART% %PROGSTARTISO% %PROGSTARTISOUTC% -- Program's scheduled start time
- %PROGEND% %PROGENDISO% %PROGENDISOUTC% -- Program's scheduled end time
- %RECID%" -- Recording rule ID, for DB lookups
- %PARENTID% -- Parent recording rule ID, for DB lookups
- %FINDID% -- Find ID, for DB lookups
- %RECSTATUS% -- Recording status as an integer for completeness, not currently useful.
- %RECTYPE% -- This is the recording rule type as an integer, in the priming script example this could be used to do an extensive priming prior to some recordings and not others. These integers are listed in recordingtypes.h in the RecordingType enum.
- %REACTIVATE% -- 1 if this recording was reactivated after failing to start on time, 0 otherwise.
With time parameters, the first listed is in locale time & format suitable for user display, the second is in locale time & ISO format suitable for some scripts, the third is in UTC time & ISO format suitable for some script and generally preferred for scripts to avoid daylight savings issues. Parameters that may be undefined should be quoted to avoid parameter aliasing bugs.