Business Community > Video Recorders > Vigi Event Type/Sub Type on JSON data sent
< Video Recorders

Vigi Event Type/Sub Type on JSON data sent

Vigi Event Type/Sub Type on JSON data sent

Vigi Event Type/Sub Type on JSON data sent
Vigi Event Type/Sub Type on JSON data sent
2025-07-22 14:26:48 - last edited 2025-07-25 00:36:39
Tags: #Alarm #event triggers
Model: VIGI NVR1008H-8P  
Hardware Version: V1
Firmware Version: 1.2.1 Build 241227 Rel.58554n

Hallo! 

I am just looking for some info on the JSON data sent via the NVR alarm/event trigger. 

Each event has a type and then a sub type. Is there a list/manual with this information in so that I can process it a bit better in my application? 

All the other data makes sense, just the types/sub types that I need a bit more info on. 

I searched the forums as well as some of the user documentation and could not find any more infor on this. 


Thanks!

  0      
 
  0      
 
#1
Options
2 Accepted Solutions
Re:Vigi Event Type/Sub Type on JSON data sent-Solution
2025-07-23 07:05:49 - last edited 2025-07-25 00:36:39

  @Reaper_za 

Reaper_za wrote

  @Clive_A 

 

I receive the JSON data from the trigger event, however there are two entries I need clarity on.

JSON data: {
"device_id": "deviceidremoved",
"device_name": "VIGI NVR1008H-8P(UN) 1.20",
"messages": [{
"type": 1, "sub_type": [ 2 ],
"localtime": "2025-07-22 20:23:14",
"channel": "3",
"channel_name": "TPLINKPTZ",
"imgId": 0
}
]
}


So out of this, "type" and "sub_type" is what I need. a list of.

As there is multiple Types and sub_types, so want to just know what they are so I can allocate them properly on my side.

We are not able to provide a list of it based on the evaluation. 

 

But FYI, this might help you understand the type you need. 

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced. ● I don't provide ETA for any products/features. No comment.
Recommended Solution
  0  
  0  
#4
Options
Re:Vigi Event Type/Sub Type on JSON data sent-Solution
2025-07-24 11:01:49 - last edited 2025-07-25 00:36:43

  @Clive_A 

 

Ok some info after doing some reverse engineering and tests.

This is the JSON data that we receive from the NVR to the "Alarm Server"


Full data Structure:

   Full data structure: {
  "device_id": "YOUR_DEVICE_ID",
  "device_name": "VIGI NVR1008H-8P(UN) 1.20",
  "messages": [
    {
      "type": 1,
      "sub_type": [
        2,

        101
      ],
      "localtime": "2025-07-24 12:43:42",
      "channel": "2",
      "channel_name": "VIGI C540V",
      "imgId": 0
    }
  ]
}


Raw Message Data
{
  "type": 1,
  "sub_type": [
    2,
    101
  ],
  "localtime": "2025-07-24 12:28:54",
  "channel": "2",
  "channel_name": "VIGI C540V",
  "imgId": 1
}

 

Type=1 seems to be any Normal event, ie motion. (be it basic or smart event)

Then here is the sub type breakdown I received from the testing.

2: "Basic Motion", 
4: "Line Crossing",
6: "Region Entering",
7: "Region Exiting",
14: "Abnormal Sound",
21: "Human Identification",
22: "Vehicle Identification",
101: "Human",
102: "Vehicle"

Sub-types 2,4,6,7 all have classification types which is 101 or 102.

21 and 22 is stand alone sub-types specifically for human or vehicle. 

There is a few of the smart events that I could not test, but think this covers most of them!

I hope this helps someone else in the future.

Recommended Solution
  1  
  1  
#8
Options
8 Reply
Re:Vigi Event Type/Sub Type on JSON data sent
2025-07-23 03:42:28 - last edited 2025-07-23 06:20:07

  @Reaper_za 

JSON for the alarm server, or the triggered event?

Which one do you need? 

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced. ● I don't provide ETA for any products/features. No comment.
  0  
  0  
#2
Options
Re:Vigi Event Type/Sub Type on JSON data sent
2025-07-23 06:42:40

  @Clive_A 

 

I receive the JSON data from the trigger event, however there are two entries I need clarity on.

JSON data: {
"device_id": "deviceidremoved",
"device_name": "VIGI NVR1008H-8P(UN) 1.20",
"messages": [{
"type": 1, "sub_type": [ 2 ],
"localtime": "2025-07-22 20:23:14",
"channel": "3",
"channel_name": "TPLINKPTZ",
"imgId": 0
}
]
}


So out of this, "type" and "sub_type" is what I need. a list of.

As there is multiple Types and sub_types, so want to just know what they are so I can allocate them properly on my side.

  0  
  0  
#3
Options
Re:Vigi Event Type/Sub Type on JSON data sent-Solution
2025-07-23 07:05:49 - last edited 2025-07-25 00:36:39

  @Reaper_za 

Reaper_za wrote

  @Clive_A 

 

I receive the JSON data from the trigger event, however there are two entries I need clarity on.

JSON data: {
"device_id": "deviceidremoved",
"device_name": "VIGI NVR1008H-8P(UN) 1.20",
"messages": [{
"type": 1, "sub_type": [ 2 ],
"localtime": "2025-07-22 20:23:14",
"channel": "3",
"channel_name": "TPLINKPTZ",
"imgId": 0
}
]
}


So out of this, "type" and "sub_type" is what I need. a list of.

As there is multiple Types and sub_types, so want to just know what they are so I can allocate them properly on my side.

We are not able to provide a list of it based on the evaluation. 

 

But FYI, this might help you understand the type you need. 

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced. ● I don't provide ETA for any products/features. No comment.
Recommended Solution
  0  
  0  
#4
Options
Re:Vigi Event Type/Sub Type on JSON data sent
2025-07-23 10:07:38 - last edited 2025-07-23 10:07:48

 

I realise now that this is directly from the NVR and not from the camera itself, and thats what the NVR sends.

I'm going to enable the alarm server on the camera now and see what it sends through. MAybe it is different. 

  0  
  0  
#5
Options
Re:Vigi Event Type/Sub Type on JSON data sent
2025-07-23 10:08:27
Thanks will see if I get something similar if I feed directly from the camera and not NVR
  0  
  0  
#6
Options
Re:Vigi Event Type/Sub Type on JSON data sent
2025-07-23 13:32:03

  @Clive_A 

OK did a bit of testing/digging and I do not receive a event_type returned i words from the NVR, I just get a type no and sub_type it seems.

I built a little program now to get the codes on each Type, so that I can reverse engineer it from there. 

Will post results here when I'm done incase someone else wants/needs them

 

  1  
  1  
#7
Options
Re:Vigi Event Type/Sub Type on JSON data sent-Solution
2025-07-24 11:01:49 - last edited 2025-07-25 00:36:43

  @Clive_A 

 

Ok some info after doing some reverse engineering and tests.

This is the JSON data that we receive from the NVR to the "Alarm Server"


Full data Structure:

   Full data structure: {
  "device_id": "YOUR_DEVICE_ID",
  "device_name": "VIGI NVR1008H-8P(UN) 1.20",
  "messages": [
    {
      "type": 1,
      "sub_type": [
        2,

        101
      ],
      "localtime": "2025-07-24 12:43:42",
      "channel": "2",
      "channel_name": "VIGI C540V",
      "imgId": 0
    }
  ]
}


Raw Message Data
{
  "type": 1,
  "sub_type": [
    2,
    101
  ],
  "localtime": "2025-07-24 12:28:54",
  "channel": "2",
  "channel_name": "VIGI C540V",
  "imgId": 1
}

 

Type=1 seems to be any Normal event, ie motion. (be it basic or smart event)

Then here is the sub type breakdown I received from the testing.

2: "Basic Motion", 
4: "Line Crossing",
6: "Region Entering",
7: "Region Exiting",
14: "Abnormal Sound",
21: "Human Identification",
22: "Vehicle Identification",
101: "Human",
102: "Vehicle"

Sub-types 2,4,6,7 all have classification types which is 101 or 102.

21 and 22 is stand alone sub-types specifically for human or vehicle. 

There is a few of the smart events that I could not test, but think this covers most of them!

I hope this helps someone else in the future.

Recommended Solution
  1  
  1  
#8
Options
Re:Vigi Event Type/Sub Type on JSON data sent
2025-07-25 00:24:04

  @Reaper_za 

Reaper_za wrote

  @Clive_A 

 

Ok some info after doing some reverse engineering and tests.

This is the JSON data that we receive from the NVR to the "Alarm Server"


Full data Structure:

   Full data structure: {
  "device_id": "YOUR_DEVICE_ID",
  "device_name": "VIGI NVR1008H-8P(UN) 1.20",
  "messages": [
    {
      "type": 1,
      "sub_type": [
        2,

        101
      ],
      "localtime": "2025-07-24 12:43:42",
      "channel": "2",
      "channel_name": "VIGI C540V",
      "imgId": 0
    }
  ]
}


Raw Message Data
{
  "type": 1,
  "sub_type": [
    2,
    101
  ],
  "localtime": "2025-07-24 12:28:54",
  "channel": "2",
  "channel_name": "VIGI C540V",
  "imgId": 1
}

 

Type=1 seems to be any Normal event, ie motion. (be it basic or smart event)

Then here is the sub type breakdown I received from the testing.

2: "Basic Motion", 
4: "Line Crossing",
6: "Region Entering",
7: "Region Exiting",
14: "Abnormal Sound",
21: "Human Identification",
22: "Vehicle Identification",
101: "Human",
102: "Vehicle"

Sub-types 2,4,6,7 all have classification types which is 101 or 102.

21 and 22 is stand alone sub-types specifically for human or vehicle. 

There is a few of the smart events that I could not test, but think this covers most of them!

I hope this helps someone else in the future.

Good for you. And that is very likely to be helpful for others. 

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced. ● I don't provide ETA for any products/features. No comment.
  0  
  0  
#9
Options

Information

Helpful: 0

Views: 211

Replies: 8

Tags

Alarm
event triggers
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.