Releases: raushel/tesla_wrappers
2020.27
VarLibrary.ps1 Update Required
- Added Trigger File Variables (required)
- Added Event.City and Event.Reason from event.json to generated Filenames
- Removed check if teslausb was online (replaced by Trigger File)
- Removed check of # files currently in /mnt/cam (Replaced by Trigger File)
Added:
- $Global:TeslaTrackModeClips
- $Global:trigger_file_saved
- $Global:trigger_file_sentry
- $Global:trigger_file_track #Placeholder for when this is added to TeslaUSB
Deprecated:
- $Global:usbname
- $Global:usbpw
Updated Naming:
2020.17
2020.11
2020.06.01
Added limited parameter support for tesla_dashcam:
Required parameter update (replaces $Global:Path):
$Global:SentryClips = '\teslausbShare\SentryClips'
$Global:SavedClips = '\teslausbShare\SavedClips'
#Additional command line modification available on line 73: StichTeslaCam.ps1
$Global:quality = 'HIGH'
$Global:layout = 'DIAMOND'
$Global:encoding = 'x265'
$Global:speedup = '2'
2020.06
Required VarLibrary.ps1 update below. This is required to support disabling all file logging and adding IFTTT webhook support.
#File Logging
$Global:file_log_enabled = $true #set to $false to disable all file logging
$Global:VerboseLogging = $true #set to $false to only log verbose entries, ignored if file_log_enabled is $false
$Global:MaxLogSizeInKB = 5120
#IFTTT
$Global:ifttt_enabled=$true
$Global:ifttt_event="tesla_wrappers"
$Global:ifttt_key="your ifttt key"
2019.48
2019.39
2019.34
2019.33
Minor Release:
- Re-enabled Timestamps (issue only occurred if trying to execute remotely over UNC path, use Hardlink if needed)
- tesla_dashcam still forced to 0.1.10 until 0.1.12 is released to fix folder output
- Added support to RecordingCleanup.ps1 for multiple BlackVue cameras
2019.31
- Pushover Support Added for Type 3, Error Events
- Updated Deletion logic in StitchTeslaCam.ps1 to support odd behavior seen in 0.1.11 of tesla_dashcam where --output to filename was being processed as a folder
- Tesla_DashCam forced back to 0.1.10 due to above issue
- --no-timestamp forced due to timestamp issues now being seen with 0.1.10 and 0.1.11 when executed over UNC path