Awake_start and awake_stop scripts for turning SentryMode on and off for archiving

[jjermany]

awake_start_MODIFIED.txt
awake_stop_MODIFIED.txt

Ill need someone to integrate this logic into our existing awake start and awake stop scripts. It uses TeslaFi (if you have an account). I added a variable to our config file:

TESLAFI WAKE MODE: Uncomment line below to choose stream or sentry

export TESLAFI_WAKE_MODE=sentry # or "stream"

[miles267]

@jjermany thanks for this. Look forward to the PR for START and STOP being integrated into the Teslausb code.

[jjermany]

No problem at all. I absolutely love this project and just happy to help.

[miles267]

@jjermany until this PR is merged into the main code, would mind providing some brief instructions on how to implement your scripts/process above? I'd like to use it for both of our Tesla cars. I'm already a TeslaFi user but the limited wake command support has caused my Teslausb syncs to no longer complete unless I leave sentry mode ON at home. In which case it also results in more video files.

For example, do I repace the awake_start and awake_stop files in /root/bin with the two files above? If I copy them into the /root/bin folder (without the *_modified.txt, of course), do they need to be chmod'd? Do I then just also add into the .conf file the export TESLAFI_WAKE_MODE=sentry entry? Do I need to re-run the teslausb upgrade script after that entry is made to the .conf file OR just reboot the teslausb system?

[jjermany]

@miles267 You will replace the awake_start and awake_stop files with the two above. You will also want to add the TESLAFI_WAKE_MODE=sentry to the conf file. This should get the desired result. Let me know if you have any issues after making these changes.

…

On Sat, Feb 8, 2025 at 12:04 PM miles267 ***@***.***> wrote: @jjermany <https://github.com/jjermany> until this PR is merged into the main code, would mind providing some brief instructions on how to implement your scripts/process above? I'd like to use it for both of our Tesla cars. I'm already a TeslaFi user but the limited wake command support has caused my Teslausb syncs to no longer complete unless I leave sentry mode ON at home. In which case it also results in more video files. For example, do I repace the awake_start and awake_stop files in /root/bin with the two files above? If I copy them into the /root/bin folder (without the *_modified.txt, of course), do they need to be chmod'd? Do I then just also add into the .conf file the export TESLAFI_WAKE_MODE=sentry entry? Do I need to re-run the teslausb upgrade script after that entry is made to the .conf file OR just reboot the teslausb system? — Reply to this email directly, view it on GitHub <#902 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A546GXJPY5TJOSFBQHCUIST2OZBK3AVCNFSM6AAAAABSOL25R6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJQGQ2TANI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[miles267]

@jjermany thanks. I'm online about to do this now 👍 Could you please tell me:

1.) once I copy those 2 scripts to /root/bin, do they need to be chmod'ded in a certain way? I'm asking because I'd prefer to keep both backups of the original files and place the new ones in that folder for use.

2.) after I've added the TESLAFI_WAKE_MODE=sentry entry to the .conf file, is it necessary to re-run the teslausb upgrade script? Or is rebooting the pi enough?

[jjermany]

You should not need to chmod those files. I did not have to. You are just replacing the current wake scripts with the new ones. No chmod is necessary here. Unfortunately, once you run the teslausb upgrade script, it will wipe out the wake files to the default ones. Rebooting works great in this case.

…

On Sat, Feb 8, 2025 at 12:14 PM miles267 ***@***.***> wrote: @jjermany <https://github.com/jjermany> thanks. I'm online about to do this now 👍 Could you please tell me: 1.) once I copy those 2 scripts to /root/bin, do they need to be chmod'ded in a certain way? I'm asking because I'd prefer to keep both backups of the original files and place the new ones in that folder for use. 2.) after I've added the TESLAFI_WAKE_MODE=sentry entry to the .conf file, is it necessary to re-run the teslausb upgrade script? Or is rebooting the pi enough? — Reply to this email directly, view it on GitHub <#902 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A546GXP27X2IXDE2B42TZWD2OZCRPAVCNFSM6AAAAABSOL25R6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJQGQ2TINQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[miles267]

Thanks again @jjermany. Sorry, hopefully one last question. Do I want the "Exclude Home" box to be CHECKED or UNCHECKED in the car's Sentry Mode config UI?

[jjermany]

You can have the car exclude your home. It will automatically pull your TeslaFi credentials and will turn on sentry mode. It will turn off after the sync is complete.

[miles267]

Interesting. I've done this now in both cars and it is not turning Sentry mode on/off. I'm editing the /root/teslausb_setup_variables.conf file (but not re-running the teslausb upgrade procedure). Should I be editing a different file to include this entry?

export TESLAFI_WAKE_MODE=sentry

[marcone]

Interesting. I've done this now in both cars and it is not turning Sentry mode on/off

This is likely because (as I mentioned in my review comments on the PR), you also need to set TESLA_WAKE_MODE to "sentry", because of the way this new code was intertwined with the existing code.

[miles267]

@marcone actually that didn't address the issue either. Yet I can confirm that I can manually toggle sentry mode ON and OFF via TeslaFi and the car responds accordingly. Hopefully this testing helps with the PR.

[jjermany]

Can you restart your pi and send us the archive loop log?

…

On Sat, Feb 8, 2025, 5:19 PM miles267 ***@***.***> wrote: @marcone <https://github.com/marcone> actually that didn't address the issue either. Yet I can confirm that I can manually toggle sentry mode ON and OFF via TeslaFi and the car responds accordingly. Hopefully this testing helps with the PR. — Reply to this email directly, view it on GitHub <#902 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A546GXPZM2HGSOD76VJGCM32O2GH3AVCNFSM6AAAAABSOL25R6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJQGU4DCNY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[marcone]

@marcone confirming I did replace both the awake_start and awake_stop files. I actually deleted the original ones from /root/bin, copying the new/modified ones in their place.

The archiveloop log shows otherwise though. The message that it is logging does not appear in either the modified awake_start attached above or the one from the PR. Therefore, you must still be using the original one.

However I had previously set TESLA_WAKE_MODE=sentry (not =stream) and TESLAFI_WAKE_MODE=sentry in the .conf file. Here is the archiveloop file with the awake_start and awake_stop replaced and only TESLAFI_WAKE_MODE=sentry. archiveloop2.log

What I was saying is that TESLA_WAKE_MODE needs to be set to "sentry" (at least for the awake_start from the PR), but the archiveloop log shows it was either set to "stream", or not set at all.

Edit: your new archiveloop log appears to show that awake_start is not being called, or failing without logging a message.
You can try running journalctl -u teslausb.service to see if that shows any additional error messages. Also make sure the replaced awake_start script is executable.

[miles267]

@marcone do I need to be doing something other than replacing awake_start and awake_stop in /root/bin folder with the new files from the PR? That’s what I’ve done yet it doesn’t use them. And I’m not re-running the Teslausb upgrade script that would overwrite them either.

[marcone]

try just running them manually and see if it complains about anything: sudo /root/bin/awake_start

[miles267]

@marcone when I attempt to run via: sudo /root/bin/awake_start, it says command not found. However if I run sudo -i and check the folder, it shows the folder is there. But perhaps a chmod command needs to be issued to make its permissions the same as the other scripts as shown here?

EDIT: I chmod +x to each script and they'll now run as sudo /root/bin/awake_start or awake_stop. Doesn't appear it's toggling sentry mode on and off though.

[marcone]

EDIT: I chmod +x to each script and they'll now run as sudo /root/bin/awake_start or awake_stop. Doesn't appear it's toggling sentry mode on and off though.

That could be because the relevant variables aren't set when called like this. It should work work when called from TeslaUSB, or you can verify like this:

sudo -i
source /root/bin/envsetup.sh
/root/bin/awake_start
/root/bin/awake_stop

[miles267]

Confirming I was able to get this to work using the two files: awake_start_MODIFIED.txt and awake_stop_MODIFIED.txt with TeslaFi. However it appears the awake and stop scripts in the PR are different (filesize, etc.) and wouldn't work when I placed them in /root/bin. @jjermany any progress on updating this PR so the code can be merged officially into teslausb main branch?

[miles267]

@jjermany I noticed today my Teslausb connected to wifi and began syncing as soon as I pulled into the garage, even before the car was put into PARK. This resulted in the TeslaFi attempt to enable sentry mode being rejected because the car wasn't yet parked. Is there any way to perhaps add a short delay to this (or a variable to allow for it), while you're compiling this PR?

02/11/2025 6:45 PM, set_sentry_mode, 123.123.123.123, car could not execute command: not_parked