AlarmLocal on NVR

[psyciknz]

Ok, I just tried and it works but not as I like.
I'm trying the NVR with one camera only and CameraEvents connects to it and to my mqtt broker.
But when I tryed a input alarm on the NVR I saw these command on mqtt:
CameraEvents/CAM-05/NVR = AlarmLocal
Now two things that I don't know:

1. why the NVR is listed under the camera name?
2. the alarm doesn't turn off when I close the alarm connected to the NVR input (but I see in the NVR log that alarm goes off)
   This becomes useless because my domotic hub knows when an alarm starts but not when it ends.

Can you help me?

My config reflects your example: I haven't listed the camera channels and I don't add the snapshotoffset

Originally posted by @valepe in #4 (comment)

[psyciknz]

This is the screenshot after I tried a tripwire alarm. It works but it doesn't report that it goes off

[psyciknz]

Little update. I'm using MQTT Explorer and I disconnect it then reconnected and all alarm are disappeared. Is this the behavior?
If yes, how can I integrate it in Home Assistant so it can know when an alarm is on and when is off?

But remains the issue of NVR under my camera name. What happens when I'll connect to the NVR all other cameras?

[psyciknz]

Little update. I'm using MQTT Explorer and I disconnect it then reconnected and all alarm are disappeared. Is this the behavior?
If yes, how can I integrate it in Home Assistant so it can know when an alarm is on and when is off?

I'll start with this one.

Unsure if I have retain turned on for the message. I'm assuming by what you say I don't. But if Home assistant is looking at it, it should hold the last state until it gets a change (ie when cameraeveents restarts and an alarm is posted. If no alarm is posted, then HA will continue to display the last state,

[psyciknz]

Ok, I just tried and it works but not as I like.
I'm trying the NVR with one camera only and CameraEvents connects to it and to my mqtt broker.
But when I tryed a input alarm on the NVR I saw these command on mqtt:
CameraEvents/CAM-05/NVR = AlarmLocal
Now two things that I don't know:

1. why the NVR is listed under the camera name?
2. the alarm doesn't turn off when I close the alarm connected to the NVR input (but I see in the NVR log that alarm goes off)
   This becomes useless because my domotic hub knows when an alarm starts but not when it ends.

Can you help me?

My config reflects your example: I haven't listed the camera channels and I don't add the snapshotoffset

Techinically if you only have one camera, and it's channel 1 (or 0), you don't tell to tell the "camera" it's an NVR. Thats said, I've not dealt with AlarmLocal as a state....is this an external alarm connected to a camera?

How would you expect to see it?
CameraEvents/CAM-05/AlarmLocal?

self.client.publish(self.basetopic +"/" + Alarm["channel"] + "/" + Alarm["name"],Alarm["Code"])

This could be it, which is part of a fall through of events, which looks like it's posted the channel name (CAM-05) then the name of the device (NVR - from the config.ini).

Where as an IVS event is

self.client.publish(self.basetopic +"/IVS/" + Alarm["channel"] ,regionText)

To be consistent, the fall through should be:
self.client.publish(self.basetopic +"/" + Alarm["Code"] + " /" + Alarm["channel"] ,true|false)

[psyciknz]

Little update. I'm using MQTT Explorer and I disconnect it then reconnected and all alarm are disappeared. Is this the behavior?
If yes, how can I integrate it in Home Assistant so it can know when an alarm is on and when is off?

I'll start with this one.

Unsure if I have retain turned on for the message. I'm assuming by what you say I don't. But if Home assistant is looking at it, it should hold the last state until it gets a change (ie when cameraeveents restarts and an alarm is posted. If no alarm is posted, then HA will continue to display the last state,

Is It possible to have an alarm on and an alarm off topics? I saw in the log that cameraevents receives the start and stop messages

[psyciknz]

Ok, I just tried and it works but not as I like.
I'm trying the NVR with one camera only and CameraEvents connects to it and to my mqtt broker.
But when I tryed a input alarm on the NVR I saw these command on mqtt:
CameraEvents/CAM-05/NVR = AlarmLocal
Now two things that I don't know:

1. why the NVR is listed under the camera name?
2. the alarm doesn't turn off when I close the alarm connected to the NVR input (but I see in the NVR log that alarm goes off)
   This becomes useless because my domotic hub knows when an alarm starts but not when it ends.

Can you help me?
My config reflects your example: I haven't listed the camera channels and I don't add the snapshotoffset

Techinically if you only have one camera, and it's channel 1 (or 0), you don't tell to tell the "camera" it's an NVR. Thats said, I've not dealt with AlarmLocal as a state....is this an external alarm connected to a camera?

How would you expect to see it?
CameraEvents/CAM-05/AlarmLocal?

No, this alarm is connected to alarm inputs of the NVR (not to the camera) so I'm expect to see a topic like CameraEvents/NVR/AlarmLocal and then the number of the alarm input (my NVR has 4 inputs and 2 outputs) and the start and stop states

[psyciknz]

Hmm any ideas how I would similate that, to look at it? Do I just need to jumper (make a circuit) the alarm input to trigger it?

Can you post this as a new issue. I think the mqtt authentication is done.

[psyciknz]

@valepe - Moved here.

[valepe]

Hmm any ideas how I would similate that, to look at it? Do I just need to jumper (make a circuit) the alarm input to trigger it?

Yes, I wired so on my NVR input then I enabled the alarm setting the NO (normally open) or the NC (normally closed) type.

[valepe]

I add an extract of my log if it can help you.
The lastest (time sequence) elements are the start and stop of tripwire alarm started on the camera and routed by the nvr.
The first two elements are the start and stop of the input alarm started on the nvr itself.
I can't try an input alarm on camera because mines haven't such feature.

log.txt

[psyciknz]

I might be able to do it off this. I’ll make it like a video motion event.

2020-02-12 22:53:23,stdout,"2020-02-12 22:53:23,836 - main - INFO - dahua_event_received: NVR Index: CAM-05 Code: AlarmLocal
2020-02-12 22:53:23,stdout,
2020-02-12 22:53:23,stdout,
2020-02-12 22:53:23,stdout,Code=AlarmLocal;action=Stop;index=0
2020-02-12 22:53:23,stdout,
2020-02-12 22:53:23,stdout,Content-Length:35
2020-02-12 22:53:23,stdout,Content-Type: text/plain
2020-02-12 22:53:23,stdout,"2020-02-12 22:53:23,836 - main - DEBUG - [NVR]: --myboundary
2020-02-12 22:53:16,stdout,"2020-02-12

In your log I don’t see a action=start, which I use the start the event.

[valepe]

I might be able to do it off this. I’ll make it like a video motion event.

2020-02-12 22:53:23,stdout,"2020-02-12 22:53:23,836 - main - INFO - dahua_event_received: NVR Index: CAM-05 Code: AlarmLocal
2020-02-12 22:53:23,stdout,
2020-02-12 22:53:23,stdout,
2020-02-12 22:53:23,stdout,Code=AlarmLocal;action=Stop;index=0
2020-02-12 22:53:23,stdout,
2020-02-12 22:53:23,stdout,Content-Length:35
2020-02-12 22:53:23,stdout,Content-Type: text/plain
2020-02-12 22:53:23,stdout,"2020-02-12 22:53:23,836 - main - DEBUG - [NVR]: --myboundary
2020-02-12 22:53:16,stdout,"2020-02-12

In your log I don’t see a action=start, which I use the start the event.

It is at the bottom of the file:
2020-02-12 22:53:16,stdout,Code=AlarmLocal;action=Start;index=0

Is it that do you search?

[valepe]

I haven't tryed but I suppose that the index number is the number of the triggered alarm input.
My nvr has four inputs so I expected a index range from 0 to 3.
If you want thiis evening I'll try it attaching a second switch to trigger the second alarm input.

[valepe]

I might be able to do it off this. I’ll make it like a video motion event.

So Video Modion events have a start and stop mqtt topics?

Good for alarms but for IVS events? Can you make them like video motion so?

[psyciknz]

Yeah, so should trigger something like CameraEvents/AlarmLocal/CAM-05 payload true or false or on off. Whatever I have in videomotion events. Then in home assistant you can have a switch, or something to report on it.