VST UI Fails to Load ROI and Tripwire Configurations - "Failed to get tripwire. Try again

Accelerated Computing Intelligent Video Analytics Metropolis Microservices for Jetson
1

Hello NVIDIA team,

I am currently using Jetson Platform Services (VST version 1.3.0-24.07.1) on Jetson Orin NX, following the official documentation strictly.

❗️Problem

Even though my RTSP stream is working and ROI + alert_rule entries are successfully added to Redis, the VST UI always shows:Also, no ROI or alert rule appears on the UI. I have verified:

  • RTSP camera is streaming successfully.
  • ROI and alert_rule are visible in Redis via CLI (XREAD emdx_config and emdx_alert_rule)
  • Sensor name and IDs are matching (e.g., sensor_id: ff2fc4c6-...)
  • emdx-webapi container is running and consuming streams.

✅ What I’ve tried

  • Added entries to Redis manually using XADD
  • Restarted emdx-webapi container after Redis updates
  • Checked webapi logs (see below)
  • Verified the ROI and alert_rule format matches the docs

🔧 System Details

  • Jetson Orin NX with JetPack 6.0
  • DeepStream 7.1
  • Redis running in Docker (emdx stack)
  • All services from JPS Quick Start guide are running

🔍 Logs

WebAPI container (docker logs emdx-webapi) shows:

However, Redis does contain the correct entries.

Is there a caching, sync, or schema validation issue?
Do we need to publish config updates in a different way to make them visible to the VST UI?

Thank you in advance!

3

Please refer this topic to set emdx endpoint in VST: VST EMDX-Analytics failure - #6 by kesong

4

Thank you @kesong,

We have already set the analytic_server_address in our vst_config.json as follows:

json

"analytic_server_address": "http://192.168.1.98:30080/emdx"

After setting this, we restarted the jetson-vst service using:

bash

sudo systemctl restart jetson-vst

However, the issue still remains — the VST UI continues to show “Failed to get tripwire. Try again”.

To troubleshoot, we compared our setup to another working Jetson system. On that working device, a request to:

ruby

http://192.168.1.98:30080/emdx/api/core/status/live

returns a valid response.

But on my system, the same request returns a 404 Not Found error.

So even though the analytics server IP is correctly set, and all services are running, something seems to be missing or misconfigured on my device related to the status/live endpoint or the web API.

We would greatly appreciate any additional suggestions to resolve this.

5

Hey ???

6

Is there no one to help?

7

HEYYYYYYY ???

8

Can you share the VST log of VST container when you get “Failed to get tripwire. Try again”?

9

emdx_webapi_log_last1000.txt (30.1 KB)
vst_log_last1000.txt (118.3 KB)

This log output originates from the emdx-webapi container of the NVIDIA Jetson Platform Services AI NVR system.
It shows that the Web API service starts correctly, initializes all processors (alerts, metadata, trajectory, events), and sets up the consumer groups for Redis streams.

However, at runtime, the service encounters multiple 422 (Unprocessable Entity) errors related to missing configuration data:

  • “Configs not present”
  • “FOV alert rules not present”
  • “Tripwire alert rules not present”
  • “ROI alert rules not present”

These errors indicate that no valid alert rule configurations or stream processing rules have been uploaded or injected into the system.
This typically occurs when the emdx_config Redis stream has not been populated, or the analytic configuration files were not properly reconciled at startup.

Additionally, the log timestamps are in UTC timezone, which may appear offset from the local system time (UTC+3).

10

You said one setup works fine and one setup fail. Maybe there is file permission issue. Can you the permission of this fold: /data/emdx-volume?

11

Unfortunately, this did not solve the problem. How do I solve this 422 error? Can you please help me?

12

Hey ?

13

HEEEEEEEEEY ???

14

What is the different between your two setup? Maybe we can get some hint form the diff as you said one setup works fine and one setup fail.

15

There is no update from you for a period, assuming this is not an issue anymore. Hence we are closing this topic. If need further support, please open a new one. Thanks

16

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.