i have write a standalone application to allow end user enable or disable the device, however the rule still able to trigger the disabled device.how to prevent the rules trigger the disabled device?

MIP
, , ,
2

Can you please add more information? What is the device? What is the rule? When the device is disabled how does it look in the Management Client? If you disable the device from the Management Client can you still trigger it then?

3

Can you please add more information? What is the device? What is the rule? When the device is disabled how does it look in the Management Client?

the device is the output(speaker & beacon), the management client show the device disabled. but output still trigger by the VA rule(detect motion from camera).

If you disable the device from the Management Client can you still trigger it then?

haven’t test it yet.

4

and is there any code at sdk can trigger the management client to refresh? cause when the custom program and management client open simultaneous, i disable a device at custom program the management client need to manually refresh to show the new configuration(device disabled).

5

You will have to use Action → Refresh or the F5 button in the Management Client.

It is on our wishlist for future capabilities that a MIP plugin should be able to do this, but it is not there today.

6

how about the rule still able to trigger disable device?

i will get my colleague to test it on site to confirm is it available to trigger by rules for disable the device in management client.

7

hi, we have tested below scenario(not involved any custom program) ..

disable rules only from management client, the associated beacon will still able to activated when tested with trigger event manually or rules condition met.

disable beacon only from management client, the associated beacon will still able to activated when tested with trigger event manually or rules condition met.

it doesn’t make sense still activate the device(beacon) if we disable the rules only or device only.

To completely disable the beacon, it require disable both device(beacon) and associated rules, is this normal or system bug?

8

I have asked around. This does not fit any known issues I could find.

I would like to try to reproduce this issue.

Please explain what the device is and how it is setup? Is it a camera with an output? What is the make, model and firmware version of the device?

9

We were able to reproduce this as a more general issue and will not need additional information about your setup.

However in order to see if it is possible to come up with a solution or fix we need to know which version of XProtect you are using.

Let us know!

10

sorry for late reply, i was on leave during the CNY.

i have request my colleagues export the configuration, can you provide me email or ftp in order to send you the config…

Milestone version - 2018R3

11

We do not need the configuration from your system as we managed to reproduce this issue without it.

Perhaps we can get a hotfix, I will get back on this..

12

Please apply this hotfix installer on your recording server.

Note that the Alarm Manager log will continue logging the event sent but the fix is preventing the rule from executing when device is disabled.

http://download.milestonesys.com/MTSKB/KB000012594/Milestone.Hotfix.201902111150.RS.12.3a.8604.exe

Please provide feedback..

13

the hot fix is working…

is this hot fix can use at 2018R2 as some of the customer still using it?

14

https://supportcommunity.milestonesys.com/s/article/disabled-output-can-still-be-triggered?language=en_US