I found the problem.
Firstly, the script that updates the crontab file creates an entry in the crontab that uses "getardoplist" instead of ".getardoplist-cron".
Secondly, the path to Pat's config file is incorrect in the ".getardoplist-cron" script.
The script ".getardop-cron" is using the wrong path to the Pat configuration file. It references the folder ".wl2k", which no longer exists with the latest version of Pat -- apparently, it got renamed to ".wl2k-old" during an update. The Pat configuration files are now in "/home/pi/.config/pat".
So, the two lines in ".getardoplist-cron" that say:
GRIDCK=$(jq .locator $HOME/.wl2k/config.json)
and
GRID=$(grep locator ~/.wl2k/config.json | sed 's/"locator"://;s/"//g;s/,//;s/ //g')
?
Should be changed to say:
GRIDCK=$(jq .locator $HOME/.config/pat/config.json)
and
GRID=$(grep locator ~/.config/pat/config.json | sed 's/"locator"://;s/"//g;s/,//;s/ //g')
After that, the crontab file needs to be edited ("crontab -e") and the last line changed to:
03 09 * * * /home/pi/patmenu2/.getardoplist-cron
Where "03 09"? is the time the job should be run every day - 9:03 am in this example.
Now the cron job runs correctly.
Julian
?
