-
Notifications
You must be signed in to change notification settings - Fork 768
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
How to resume logging when on the intranet? #91
Comments
It would be:
from your NAS via SSH you can run:
to suspend logging:
Full curl command: grafana runs on port 3000 and the actual API/teslamate container is running/listening on port 4000 |
Suspend and resume don't respond to anything but If that's not the case, you'll have to either invoke suspend/resume via the web interface ui button or send the request yourself via something like |
This is great - thank you. I also wanted to share that cURL it not out of the box in PowerShell - at least on Windows 10, so one doesn't need to do anything else. Ditto on SSH btw, and not need for putty or anything. Perhaps if we update the readme it might help others or point them back to this thread. Thanks again. |
Hi there, I tried that, but I only get a "Not Found" on the website. However, the sleep attempt is not aborted. I wanted to connect it to the front door so that logging starts again as soon as I open the door. Tesla Mate version 1.25.2 Has the path changed? |
Sorry not really an issue but a questions - I was looking to understand on how to resume logging when running this locally and not exposed online.
The documentation says to use Tasker or Shortcuts and all this:
PUT https://teslamate.your-domain.com/api/car/$car_id/logging/resume
I am running Docker on my Synology NAS; and and it its IP is 192.168.1.2, what do I use? And is there a way to tickle this IP without a PUT call? Would it be something like:
http://192.168.10.2:3000/api/car/$car_id/logging/resume
And I presume $car_id is the ID column from the cars table and not the eid or vid?
Thanks in advance!
The text was updated successfully, but these errors were encountered: