@trillboards/edge-sdk 0.2.4 → 0.2.7

package/deploy/windows/trillboards-pair.cmd

@@ -0,0 +1,276 @@
+@echo off
+REM Trillboards first-run pairing helper — STAGED and HONEST. Every claim it
+REM prints is verified first (the Hiten failure was this script claiming
+REM "connected" while the TrillboardsEdge scheduled task was never registered
+REM and zero frames had ever been proven):
+REM   [1] pair       code -> config (device token delivered ONLY here)
+REM   [2] connection authenticated round-trip via `verify-connection`
+REM   [3] service    scheduled task EXISTS (auto-repair via register-task.ps1)
+REM   [4] running    task actually STARTED (state polled, locale-safe via PS)
+REM RESUMABLE: if a verified config already exists it skips straight to the
+REM service stages — re-running after a network/service fix needs NO new code.
+setlocal
+set "UI_MODE=0"
+set "UI_STATUS_FILE="
+
+:parse_args
+if "%~1"=="" goto :args_done
+if /I "%~1"=="--setup" (
+  set "UI_MODE=1"
+  shift /1
+  goto :parse_args
+)
+if /I "%~1"=="--status-file" (
+  set "UI_STATUS_FILE=%~2"
+  shift /1
+  shift /1
+  goto :parse_args
+)
+shift /1
+goto :parse_args
+
+:args_done
+for %%I in ("%~dp0..") do set "ROOT=%%~fI"
+set "CFG=%ROOT%\trillboards.config.json"
+set "LOGDIR=%LOCALAPPDATA%\Trillboards\logs"
+set "LOG=%LOGDIR%\pairing.log"
+set "TASK=TrillboardsEdge"
+if not exist "%LOGDIR%" mkdir "%LOGDIR%" >nul 2>&1
+
+echo ==================================================
+echo    Trillboards camera pairing
+echo ==================================================
+echo.
+
+REM Caution (non-blocking): sensing stops if this machine sleeps or turns off.
+powershell -NoProfile -NonInteractive -Command "$b=Get-CimInstance Win32_Battery -ErrorAction SilentlyContinue; if($b -and $b.BatteryStatus -eq 1){ exit 0 }; exit 1" >nul 2>&1
+if not errorlevel 1 (
+  echo NOTE: this computer is on battery. It must stay ON and PLUGGED IN for
+  echo your cameras to keep reporting. The connector prevents sleep while it
+  echo runs, but a closed lid / shutdown still stops it.
+  echo.
+)
+
+REM ── Resume path: a saved, complete pairing skips the code prompt. Branch on
+REM WHY verification failed: only an auth rejection (3) or a token-less config
+REM (4) needs a new code — a network/server failure (2/5) means the saved
+REM pairing is fine and the operator just fixes connectivity (NO new code).
+if not exist "%CFG%" goto :ask_code
+"%~dp0node.exe" "%~dp0check-feeds.js" "%CFG%" >nul 2>&1
+if errorlevel 1 goto :ask_code
+call "%~dp0trillboards-edge.cmd" verify-connection --config "%CFG%" >nul 2>&1
+set "VERIFY_RC=%ERRORLEVEL%"
+if "%VERIFY_RC%"=="0" (
+  echo Already paired on this computer ^(connection verified^) — checking the
+  echo background service...
+  echo [%date% %time%] resume: existing config verified >> "%LOG%"
+  goto :ensure_task
+)
+if "%VERIFY_RC%"=="2" goto :resume_offline
+if "%VERIFY_RC%"=="5" goto :resume_offline
+goto :ask_code
+
+:resume_offline
+echo This computer already has a saved Trillboards pairing, but it can't reach
+echo Trillboards right now. Check the internet connection ^(Wi-Fi/ethernet,
+echo firewall^), then re-open "Pair a camera" — you will NOT need a new code.
+echo [%date% %time%] resume: saved config, connection check failed ^(rc=%VERIFY_RC%^) >> "%LOG%"
+call :write_ui_status error "This computer is offline" "Check the internet connection, then try again. Your saved pairing is still secure."
+goto :done_fail
+
+:ask_code
+REM Dual-mode entry. DEFAULT (just press Enter) = the validate-first SETUP flow:
+REM this window shows a short code, you type it into the portal, and the portal
+REM proves every camera stream BEFORE anything is created. Pasting a code from
+REM the portal's classic Install step keeps the legacy claim-code flow working
+REM (old wizard versions, scripted installs).
+if "%UI_MODE%"=="1" goto :setup_mode
+echo Press ENTER to start camera setup (this window will show you a code
+echo to type into the Trillboards portal).
+echo.
+echo Or, if the portal already gave you a code (classic flow), paste it here.
+echo.
+set "CODE="
+set /p CODE="Code (or press Enter): "
+if "%CODE%"=="" goto :setup_mode
+
+call "%~dp0trillboards-edge.cmd" pair --code "%CODE%" --config "%CFG%"
+set "PAIR_RC=%ERRORLEVEL%"
+if "%PAIR_RC%"=="0" goto :paired
+if "%PAIR_RC%"=="7" (
+  REM Paired but the API REJECTED the fresh pairing (auth). Unlike rc=6, the
+  REM saved config is unusable — the owner genuinely needs a new code.
+  echo.
+  echo Trillboards rejected this new pairing. Generate a FRESH code in the
+  echo portal and run "Pair a camera" again.
+  echo [%date% %time%] pair: saved but auth-rejected ^(rc=7^) >> "%LOG%"
+  goto :done_fail
+)
+if "%PAIR_RC%"=="6" (
+  REM Paired + saved, but the connection check failed. The CLI already printed
+  REM the real reason (network/server) — the code is SPENT but NOT wasted.
+  echo.
+  echo Your pairing is saved on this computer. Fix the connection issue above,
+  echo then re-open "Pair a camera" from the Start Menu — it will pick up where
+  echo you left off. You will NOT need a new code.
+  echo [%date% %time%] pair: saved but unverified ^(rc=6^) >> "%LOG%"
+  goto :done_fail
+)
+REM Hard pair failure — the CLI printed the classified reason (bad/expired code,
+REM network, rate-limit, server). Do NOT add the old blanket "double-check the
+REM code" here: for non-code failures that message was a lie.
+echo [%date% %time%] pair: failed ^(rc=%PAIR_RC%^) >> "%LOG%"
+goto :done_fail
+
+:paired
+REM Gate on RTSP URLs before starting, mirroring the macOS pair.command guard:
+REM the creds-stay-on-prem pair path returns cameras WITHOUT an rtspUrl (written
+REM as empty placeholders) and pairing still exits 0, but cloud-sense would skip
+REM the URL-less feeds and exit with nothing - so do NOT start the task or claim
+REM "connected" until every feed has its rtsp:// URL (Codex P2 on #7731).
+"%~dp0node.exe" "%~dp0check-feeds.js" "%CFG%"
+if errorlevel 1 (
+  echo.
+  echo Paired, but one or more camera feeds still need an RTSP URL.
+  echo Camera credentials stay on this PC. Add the rtsp:// URL^(s^) to:
+  echo   "%CFG%"
+  echo then re-run this pairing helper to start. The connector was NOT
+  echo started yet, so it won't keep restarting on an incomplete config.
+  echo [%date% %time%] pair: ok, feeds missing rtspUrl — not started >> "%LOG%"
+  call :write_ui_status error "Camera links are incomplete" "One or more cameras still need a stream link. Contact Trillboards support."
+  goto :done_fail
+)
+goto :ensure_task
+
+
+:setup_mode
+REM ── Validate-first setup: the CLI displays the code, keeps this window's
+REM staged progress, and exits 0 once the portal finalizes cameras and the
+REM config is written — then the SAME honest service stages below run.
+if defined UI_STATUS_FILE (
+  call "%~dp0trillboards-edge.cmd" setup --config "%CFG%" --status-file "%UI_STATUS_FILE%"
+) else (
+  call "%~dp0trillboards-edge.cmd" setup --config "%CFG%"
+)
+set "SETUP_RC=%ERRORLEVEL%"
+if "%SETUP_RC%"=="0" (
+  echo [%date% %time%] setup: config received >> "%LOG%"
+  goto :ensure_task
+)
+if "%SETUP_RC%"=="3" (
+  echo.
+  echo The new setup flow is not available yet on the server. Use the classic
+  echo flow instead: generate a code in the portal and paste it below.
+  echo [%date% %time%] setup: server 404 ^(rc=3^) — classic fallback >> "%LOG%"
+  if "%UI_MODE%"=="1" (
+    call :write_ui_status error "Setup is temporarily unavailable" "Try again shortly or contact Trillboards support."
+    goto :done_fail
+  )
+  goto :ask_code
+)
+if "%SETUP_RC%"=="2" (
+  echo.
+  echo Setup ended without finishing ^(expired or timed out^). Re-open
+  echo "Pair a camera" to start again — nothing was created, nothing is lost.
+  echo [%date% %time%] setup: expired/timeout ^(rc=2^) >> "%LOG%"
+  call :write_ui_status error "Setup ended before finishing" "Try again when you are ready. No cameras were created."
+  goto :done_fail
+)
+echo.
+echo Setup hit an error ^(see above^). Details were saved to:
+echo   "%LOG%"
+echo [%date% %time%] setup: failed ^(rc=%SETUP_RC%^) >> "%LOG%"
+call :write_ui_status error "Setup needs attention" "Try again. If the problem continues, contact Trillboards support."
+goto :done_fail
+
+:ensure_task
+REM Local AI is installed by the customer installer before this pairing helper
+REM can open. Re-check it synchronously in required-bundle mode: this may restart
+REM the service, but it can never download a missing model from the network.
+call :write_ui_status local_ai "Checking local AI" "Verifying the private AI service installed with Trillboards."
+if not exist "%~dp0setup-litertlm.ps1" (
+  echo [%date% %time%] local-ai: setup script missing >> "%LOG%"
+  call :write_ui_status local_ai_error "Local AI setup is incomplete" "Your cameras are paired. Reinstall the Trillboards CCTV connector."
+  goto :done_fail
+)
+if defined UI_STATUS_FILE (
+  powershell.exe -NoProfile -ExecutionPolicy Bypass -WindowStyle Hidden -File "%~dp0setup-litertlm.ps1" -RequireBundledModel -ProgressPath "%UI_STATUS_FILE%" >> "%LOG%" 2>&1
+) else (
+  powershell.exe -NoProfile -ExecutionPolicy Bypass -WindowStyle Hidden -File "%~dp0setup-litertlm.ps1" -RequireBundledModel >> "%LOG%" 2>&1
+)
+if errorlevel 1 (
+  echo [%date% %time%] local-ai: verification failed >> "%LOG%"
+  call :write_ui_status local_ai_error "Local AI needs attention" "The included local AI could not be started. Reinstall Trillboards CCTV Setup; your camera pairing is saved."
+  goto :done_fail
+)
+echo [%date% %time%] local-ai: bundled model and service verified >> "%LOG%"
+
+call :write_ui_status starting_service "Starting Trillboards" "Installing and verifying the background camera service."
+
+REM ── Stage 3: the background service must EXIST. The installer registers it,
+REM but that registration can fail silently (it did for Hiten) — so verify and
+REM self-repair here instead of assuming.
+powershell -NoProfile -NonInteractive -Command "if (Get-ScheduledTask -TaskName '%TASK%' -ErrorAction SilentlyContinue) { exit 0 }; exit 1" >nul 2>&1
+if not errorlevel 1 goto :start_task
+echo Background service is not installed — repairing...
+echo [%date% %time%] task: missing, running register-task.ps1 >> "%LOG%"
+powershell -NoProfile -ExecutionPolicy Bypass -File "%~dp0register-task.ps1" -InstallDir "%ROOT%" >> "%LOG%" 2>&1
+powershell -NoProfile -NonInteractive -Command "if (Get-ScheduledTask -TaskName '%TASK%' -ErrorAction SilentlyContinue) { exit 0 }; exit 1" >nul 2>&1
+if not errorlevel 1 goto :start_task
+echo.
+echo ERROR: could not install the background service ^(scheduled task "%TASK%"^).
+echo Your pairing IS saved — nothing is lost — but sensing cannot start until
+echo this is fixed. Details were saved to:
+echo   "%LOG%"
+  echo Please send that file to Trillboards support.
+  call :write_ui_status error "Background service could not be installed" "Your camera pairing is saved. Restart this computer, then try again."
+  goto :done_fail
+
+:start_task
+REM ── Stage 4: the service must actually RUN. Start it, then poll its state
+REM (PowerShell enum — locale-safe, unlike schtasks' localized "Running" text).
+powershell -NoProfile -NonInteractive -Command "Start-ScheduledTask -TaskName '%TASK%'" >> "%LOG%" 2>&1
+powershell -NoProfile -NonInteractive -Command "$d=[DateTime]::Now.AddSeconds(15); while([DateTime]::Now -lt $d){ $t=Get-ScheduledTask -TaskName '%TASK%' -ErrorAction SilentlyContinue; if($t -and $t.State -eq 'Running'){ exit 0 }; Start-Sleep -Milliseconds 800 }; exit 1" >nul 2>&1
+if errorlevel 1 (
+  echo.
+  echo ERROR: the background service is installed but would not start.
+  echo Your pairing IS saved. Try restarting this computer — the service starts
+  echo automatically at login. If it still fails, send this file to support:
+  echo   "%LOG%"
+  echo [%date% %time%] task: registered but did not reach Running in 15s >> "%LOG%"
+  call :write_ui_status error "Cameras paired, service not running" "Restart this computer, then open Trillboards CCTV Setup again. Your pairing is saved."
+  goto :done_fail
+)
+
+echo.
+echo   [OK] Paired
+echo   [OK] Connected to Trillboards
+echo   [OK] Private local AI installed and healthy
+echo   [OK] Background service installed and running
+echo.
+echo Setup is complete. Trillboards and private local AI are running.
+echo [%date% %time%] success: paired + verified + task running >> "%LOG%"
+call :write_ui_status ready "Camera setup is complete" "Trillboards and private local AI are running in the background."
+echo.
+if "%UI_MODE%"=="1" (
+  endlocal
+  exit /b 0
+)
+pause
+endlocal
+exit /b 0
+
+:done_fail
+echo.
+if "%UI_MODE%"=="1" (
+  endlocal
+  exit /b 1
+)
+pause
+endlocal
+exit /b 1
+
+:write_ui_status
+if not defined UI_STATUS_FILE exit /b 0
+call "%~dp0trillboards-edge.cmd" setup-status --status-file "%UI_STATUS_FILE%" --stage "%~1" --title "%~2" --message "%~3" >nul 2>&1
+exit /b 0