You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2022. It is now read-only.
Thanks for a great simple solution to generating Unifi camera motion snapshots. Worked flawlessly for me for months.
I just upgraded to unifi video 3.10.0 and the unifi-video-mqtt.sh script stopped doing what it should. A quick inspection shows that Ubiquiti added an extra field to motion.log, which breaks the line which extracts the camera ID from the log line. I got it to work again by updating the line which extracts LAST_CAM variable to be:
Thanks, it would be good if we could find a way to check the version of unifi video running or, we run a grep to see what format the file is in then we decide which way to grep it. I'll take a look at it soon.
If you figure out a good way to do the above feel free to create a PR
Fixesmzac#2mzac#5mzac#6
based on your Dockerfile, `grep -n1` isn't supported so I removed the -n1. I commented out all the variables at the top so they can be passed in with docker env vars instead.
Thanks for a great simple solution to generating Unifi camera motion snapshots. Worked flawlessly for me for months.
I just upgraded to unifi video 3.10.0 and the unifi-video-mqtt.sh script stopped doing what it should. A quick inspection shows that Ubiquiti added an extra field to motion.log, which breaks the line which extracts the camera ID from the log line. I got it to work again by updating the line which extracts LAST_CAM variable to be:
LAST_CAM=`echo $LAST_MESSAGE | awk -F 'Camera[][]' '{print $2}'`
Basically, I changed "[" to "Camera[" in the awk command.
There may be a better way to fix this, I'm no expert.
The text was updated successfully, but these errors were encountered: