GoPro as dashcam : Issue on Motion detection trigger in a scheduled interval #322
Replies: 4 comments 29 replies
-
|
As for "Feel a little scammed on that issue because as a gopro customer and a developer every working feature from previous model must be included on newer model, especially with cameras industry. " That doesn't not apply to Labs and it would kill Labs if it did. Not all features from old Labs are supported on newer cameras, as the engineering for Labs needs to be nibble. We've had experimental features that don't work on the next model. e.g. encryption, introduced on HERO9, didn't work in HERO10 or 11. I expect HERO10 will see another Labs update this year, not anytime soon. BUT, if you read this forums close enough, patch versions are sometimes shared (not QA'd, not official,) I have not idea if the latest patch address HERO10 sleep issue so try it, good for few days more: https://www.dropbox.com/transfer/AAAAAFlTQ8vpofFqfchhxV5MlkWijDyyn9PoChwnQKAlQUV4OEtvzOw |
Beta Was this translation helpful? Give feedback.
-
|
!E command can only be paired with !S command, not !SM or !SI etc. This one of the many reason to obsolete the older triggers for the new scripting. !SM is both a start and end trigger, so script processing doesn't see !20:00E until the capture has ended due to the lack motion. It is not possible if motion is continuous. The closest would be something like !08:00NoMBOOT="!SM4H2<20:00!R" |
Beta Was this translation helpful? Give feedback.
-
|
Thanks David, I figure it out to have a stable script that makes possible simultaneously CASE 1, 3, 5, 6 (all case appart Hindsight which are CASE 2, 4, 7). Here the working script :
|
Beta Was this translation helpful? Give feedback.
-
This says wait until 8am, then save create the boot script. Weird. Remove the first !08:00N. The is the script saved is odd. <20:00!SM4H2~!10O!R This is if less than 8pm, motion detect else shutdown (after sleeping the camera for 10s), loop. This is nothing to wake the camera at 8am. It should be <20:00!SM4H2~!08:00R!R
|
Beta Was this translation helpful? Give feedback.
-
|
Your script is not working after trying for one week... : It just activate the motion detection if <20:00 and then sleep till 8:00, and then after waking up it does literally nothing (no more motion detection) What I want is a script similar to that so it will save on the SD card : |
Beta Was this translation helpful? Give feedback.
-
|
@dnewman-gpsw up ! Assistance may be appreciated |
Beta Was this translation helpful? Give feedback.
-
|
Hello @dnewman-gpsw, I recently tested the new H12 for the motion detection + hindsight (15s window) continuously, and I find out that this QR code previously working on H10 and H11 : Here the logs : So what happens is that the gopro do the following : motion detection + hindsight for 3 times perfectly, but then for the fourth time it stopped and the logs atm was |
Beta Was this translation helpful? Give feedback.
-
|
This script only involves Thanks for the "Labs Processing" explanation, now I know. Can you tell me if my script involving both MD and hindsight is working on your side ? |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, yes I meant it works with hs1, the full command was used. I do not get that illogical error. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, will this bug will be corrected for H12 soon ? The issue is that, this command don't run indefinitely in the H12 : Seems that this bug was corrected with an alternative Labs update on H10/H12 according to #187, maybe a workaround to do for H12 ? Thanks in advance |
Beta Was this translation helpful? Give feedback.
-
|
It is working on my HERO12s at the moment (running two continuously), however I did see the MD not start a couple of times. I solved that with hS1!1N!SM4H2hS0!R just give the camera a second between initializing the Hindsight and starting the motion detection. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, I didn't even think about adding time between each process, now I know. I tested it and it is working on H12, thanks. Now I will work on the other features and keep all updated. Have a good day @dnewman-gpsw and thanks again. |
Beta Was this translation helpful? Give feedback.
-
Introducing GoPro as a dashcamCamera compatibility :
Dashcam Mode while driving (day/night)
Dashcam Mode when parked (day)As gopro cameras had bad low light performance until H12 (01/10/23), it is not interesting to configure it for night time, but if there is a good outdoor lighting, just skip intervals condition and directly use the QR code n°2
note: The advantage of script 5 over 4 is that, script 5 had more control on time loops and when script must be executed. For example, if you run the script at 3AM in the morning, script 4 will enter the dashcam script immediately and start processing due to his single condition loop whereas script 5 will shutdown and run the dashcam script only if the time is between 5AM and 20AM due to his stacked conditionals loop. Use case n°5 is still under stress testing, will keep updated. Logs debuggingImprove logging verbosity (Debug Level 1)
Reset Labs
|
Beta Was this translation helpful? Give feedback.
-
ProblemThere is a bug in the stacked conditionals based on time, when this script
There is definitively a conditionals bad interpretation, i expect this script to do this : But it does not behave as expected, need help on that to fix it, can you please try this on your side, Thanks in advance |
Beta Was this translation helpful? Give feedback.
-
|
What did the log say? The errors will be in there.
Why is this wrong? This is what script askes for. The script is running but doing nothing, so it shows the "Labs processing" message. The camera remains awake as there is an assumption if you running a script you want it to remain running as there are command to sleep the camera.
This might require another !1N. The log will help explain. I can't try all users 24 hour scripts, you will need provide the debug logs. |
Beta Was this translation helpful? Give feedback.
-
|
Yes my bad I just corrected the previous comment with the actual error, everything doing pretty good but when the script enter the sleep mode, it does not always wake up the next day. I found that, when it enter the sleep mode, sometimes the gopro turn back ON several times for no reason and go back to sleep, maybe is it to keep time in memory while he is asleep ? What will be ideal is to apply the else to the first condition like that, so the script will be complete (and it will avoid the gopro to stay ON if it is activated after 23:59) : But I read the documentation and it says the following : "However the else can only be applied to the last condition." I will test the same script for 24 hours and provide more logs feedback. |
Beta Was this translation helpful? Give feedback.
-
|
Just do:
|
Beta Was this translation helpful? Give feedback.
-
|
Great idea. This script displays Corrected version : Will test it and keep updated ! |
Beta Was this translation helpful? Give feedback.
-
|
Issue fixed 🥇 After several tests and stress testing, the full needed features are finally working mainly on H12 and partially on H11, Advanced details here |
Beta Was this translation helpful? Give feedback.
-
Use case :
Trying to use my gopro as a dashcam while a motion detection occurs in a specific scheduled interval using 'boot' command. Note that the gopro is continuously powered by a powerbank and cooled with a fan (in case of hot weather).
Labs documentation :
I find the actual documentation for 'boot' command here (https://gopro.github.io/labs/control/extensions/), it says : e.g. !10:00NoMBOOT=”!SM3D4H5!R” <- Wake at 10am, then motion capture continuously. But the instructions does not work on the hero10 (also tried on the hero8 and do not work neither).
Troubleshooting :
Here, the command I was troubleshooting with :
CASE 1 - Start Motion Detection continuously: !SM4H2!R (✅ working)
CASE 2 - Start Motion Detection + Hindsight (15s window) continuously: mVhS1!SM4H2hS0!R (✅ working and already solved #187)
CASE 3 - Start Motion Detection continuously on a scheduled time at 8:00 AM : !08:00NoMBOOT="!SM4H2!R" or !08:00NoMBOOT=!SM4H2!R (❌ failed) -> boot at scheduled time OK, but the motion detection FAILED with message error*
CASE 4 - Start Motion Detection continuously on a scheduled time at 8:00 AM + Hindsight: !08:00NoMBOOT="mVhS1!SM4H2hS0!R" (❌ failed) -> boot at scheduled time OK, Hindsight OK, but the motion detection FAILED with message error*
CASE 5 - Boot + Motion detection + Adding an SD card based boot file (base on this example : https://gopro.github.io/labs/control/imutrigger/) : !MQRDR=1!08:00N!MBOOT="!Lmotion"!SAVEmotion=!SM4H2!R (❌ failed) -> same error from case 3 + but when restarting manually the gopro the motion detection begin without taking into account the time scheduled condition
CASE 6 - Start Motion Detection continuously on a scheduled time at 8:00 AM and stop it at 20:00 AM : help❓
CASE 7 (final) - All the above (motion + hindsight + start/stop schedule ) + upload on the cloud : help❓
Issue (MAIN) :
*Message error each time using 'boot' command: "CANCEL MOTION TRIGGER"
It is kinda frustrating to see that every single step can work separately on the hero10 and hero8 but when we combine with boot commands everything failed.
Issue (SECONDARY) :
I want the rear LCD screen to be turned OFF on hero10 while processing the script above because it :
I saw the issue here #77, but unfortunately technical support @dnewman-gpsw says that's not possible due to the architectural difference. I feel really sad that it works on previous models hero8, hero9 and newer model hero11 but not on hero10. Feel a little scammed on that issue because as a gopro customer and a developer every working feature from previous model must be included on newer model, especially with cameras industry. It might be a solution, if you can reopen that issue I will highly appreciate.
Logs (for case 4) :
Running on GoPro Hero 10, Firmware 01.50.70
Goal :
My goal is at least to find a solution to make CASE 3 functional as written in the documentation which is my biggest concern.
I take time to meticulously point the issue and improve gopro labs features, and expect a solution from it. Thanks in advance for the support.
Beta Was this translation helpful? Give feedback.
All reactions