Axis Events mapping KB2400

Hi,

I am having trouble with this KB.

1. I can’t get it to trigger a rule in Milestone.

2. How do I configure the temperature that triggers the event?

I have followed the KB as described, but I don’t understand how it would work. The KB does not describe what should be (if anything) configured in the camera.

Milestone Corporate R2 btw.

Don’t worry, I don’t understand the KB either.

Well, seriously: If you have ever configured a “Hardware motion detection event” (i.e. motion detection carried out by the camera, not by the recording Server), then you have almost won. It’s the same with the other events: You configure the camera (via its web interface) to fire the event (e.g. the crossline detection), and then you configure the XProtect server to subscribe to it.

There is just one real challenge: The same event is called differently on the camera and in Milestone. This challenge is adressed by the table in the bottom of the KB which maps the Axis names to Milestone names (separately for Professional and Advanced products).

Does this make sense?

Hi Torsten!

First of; thank you. I thought it was just me..

I have tried using the table, but a wireshark investigation of the communication between the camera and the recording server tells me that I have configured it wrong.

Clearly I am missing something here regarding the XPCO rule and the Axis name.

Could you please let me know how you would setup the RTSP stream logic string in the camera? it says “tns1:Device/tnsaxis:Status/Temperature/Above”

But i guess I would have to replace Device with something that is identified with Milestone.

Is there a manual that explains this on other events like you said motion detection by camera.

best regards,

Pål

Is the Axis name in the KB what the rule is supposed to be named? if so it is to long.. Axis will not accept that lenght for a rule..

So, now we know: You need to subscribe to “Temperature Detection Started” and “Temperature Detection Stopped”. Distinguishing between the different detection windows is made by a separate parameter to the event.

Good luck :slight_smile:

Torsten

P.S. Pls mark this post as “best answer” if you think it solves your issue.

I hope someone writes a manual for this kind of detection.

Thank you Thorsten great work!

Someone just did… KB article #2400 has been completely reworked. Have fun. /Torsten