I have tried running a script on motion events to get notications on my android phone, with 3rd party app.
I testet it with SimplePush, which is not free however (one time fee, and low on functionalities).
A simple curl command is run to sent notification to the phone.
The command execution works, but it does not wait for the defined time delay, before new commands can be executed "Allow Next Command".
Se every new motion trigger is executed with command.
If the command function is intended for push notifications, i would suggest only executing them in Recording mode, as they cannot turn off again, as i assume most people would like to, when setting monitors to "Watch only mode".
Or is a dedicated feature for push notifications on the work table?
Ignoring large motion changes could also be acheived by setting minimum number of motion changes above the threshold, before a motion event is stored. This missing setting would remove many false motion events cause by exposure changes. I think it was also mentioned else where on the forum.
Currently Shinobi can't do that. Adding it would be simple in perspective. This is also an interesting thought, so ill move this over to the Suggestions section.
though the way Shinobi works it cannot be burned on to the stream. You cannot see this information unless you are viewing with a Shinobi interface of some kind, like the dashboard or embed window.
It's even possible to add on hover effects for such information if you want.
Also if i were to go about doing this i would not use a text file. I would make it so an API request would display this information. Like a GET or POST method.
Thanks for the idea! I will totally be looking to add this in.