detection problem

[titof2375]

hello, I have installed zmeventnotification and when a camera detection something, I find myself with that for the detection

DBG-2:2021-01-16,11:46:28 PARENT: ---------->Tick START<-------------- DBG-2:2021-01-16,11:46:28 PARENT: After tick: TOTAL: 1, ES_CONTROL: 1, FCM+WEB: 0, FCM: 0, WEB: 0, MQTT:1, invalid WEB: 0, PENDING: 0 DBG-2:2021-01-16,11:46:28 PARENT: There are 1 active child forks... DBG-2:2021-01-16,11:46:28 PARENT: Closing unclosed event:141 of Monitor:1 as we are in a new event INF:2021-01-16,11:46:28 PARENT: New event 142 reported for Monitor:1 (Name:Camera devant) Motion All[last processed eid:141] 01/16/21 11:46:28.111661 zmeventnotification[9167].INF [main:989] [PARENT: New event 142 reported for Monitor:1 (Name:Camera devant) Motion All[last processed eid:141]] DBG-2:2021-01-16,11:46:28 PARENT: checkEvents() new events found=1 DBG-2:2021-01-16,11:46:28 PARENT: There are 1 new Events to process DBG-2:2021-01-16,11:46:28 PARENT: ---------->Tick END<-------------- DBG-1:2021-01-16,11:46:28 PARENT: Forked process:9194 to handle alarm eid:142 DBG-2:2021-01-16,11:46:28 |----> FORK:Camera devant (1), eid:142 Adding event path:/var/cache/zoneminder/events/1/2021-01-16/142 to hook for image storage DBG-1:2021-01-16,11:46:28 |----> FORK:Camera devant (1), eid:142 Invoking hook on event start:'/var/lib/zmeventnotification/bin/zm_event_start.sh' 142 1 "Camera devant" "Motion All" "/var/cache/zoneminder/events/1/2021-01-16/142" DBG-2:2021-01-16,11:46:29 |----> FORK:Camera devant (1), eid:142 parse of hook: and [] DBG-1:2021-01-16,11:46:29 |----> FORK:Camera devant (1), eid:142 hook start returned with text: json:[] exit:1 DBG-3:2021-01-16,11:46:29 |----> FORK:Camera devant (1), eid:141 For 1 (Camera devant), SHM says: state=2, eid=142 INF:2021-01-16,11:46:29 |----> FORK:Camera devant (1), eid:141 Event 141 for Monitor 1 has finished 01/16/21 11:46:29.062943 zmeventnotification[9174].INF [main:989] [|----> FORK:Camera devant (1), eid:141 Event 141 for Monitor 1 has finished] DBG-3:2021-01-16,11:46:29 |----> FORK:Camera devant (1), eid:141 Event end object is: state=>pending with cause=>Motion: All DBG-2:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:142 rules: Checking rules for alarm caused by eid:142, monitor:1, at: Sat Jan 16 11:46:31 2021 with cause:Motion All DBG-1:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:142 rules: No rules found for Monitor, allowing:1 DBG-1:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:142 Matching alarm to connection rules... DBG-1:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:142 Checking alarm conditions for MQTT 192.168.1.3 DBG-1:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:142 Monitor 1 event: should send out as 9.94012999534607 is >= interval of DBG-1:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:142 shouldSendEventToConn returned true, so calling sendEvent DBG-2:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:142 isAllowedChannel: got type:event_start resCode:1 INF:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:142 Not sending over MQTT as notify filters are on_success:all and on_fail:none 01/16/21 11:46:31.030303 zmeventnotification[9194].INF [main:989] [|----> FORK:Camera devant (1), eid:142 Not sending over MQTT as notify filters are on_success:all and on_fail:none] DBG-3:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:142 child finished writing to parent DBG-2:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:141 Adding event path:/var/cache/zoneminder/events/1/2021-01-16/141 to hook for image storage DBG-1:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:141 Invoking hook on event end:'/var/lib/zmeventnotification/bin/zm_event_end.sh' 141 1 "Camera devant" "Motion: All" "/var/cache/zoneminder/events/1/2021-01-16/141" DBG-2:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:141 parse of hook:Motion: All and [] DBG-1:2021-01-16,11:46:31 |----> FORK:Camera devant (1), eid:141 hook end returned with text:Motion: All json:[] exit:0 DBG-2:2021-01-16,11:46:33 |----> FORK:Camera devant (1), eid:141 rules: Checking rules for alarm caused by eid:141, monitor:1, at: Sat Jan 16 11:46:33 2021 with cause:Motion All DBG-1:2021-01-16,11:46:33 |----> FORK:Camera devant (1), eid:141 rules: No rules found for Monitor, allowing:1 INF:2021-01-16,11:46:33 |----> FORK:Camera devant (1), eid:141 Not sending event end alarm, as we did not send a start alarm for this, or start hook processing failed 01/16/21 11:46:33.069086 zmeventnotification[9174].INF [main:989] [|----> FORK:Camera devant (1), eid:141 Not sending event end alarm, as we did not send a start alarm for this, or start hook processing failed]

I think that one that I have wrongly parameterized one thing, because I have trouble understanding your explanation

[Magic919]

What is the question?

[titof2375]

hello, in fact my question is that I am not of notification see other log

[PARENT: New event 438 reported for Monitor:1 (Name:Camera devant) Motion Nouv.[last processed eid:435]]
03/01/21 06:47:16.149786 zmeventnotification[28394].INF [main:989] [|----> FORK:Camera devant (1), eid:438 Not sending over MQTT as notify filters are on_success:all and on_fail:none]
03/01/21 06:47:20.152020 zmeventnotification[28394].INF [main:989] [|----> FORK:Camera devant (1), eid:438 Event 438 for Monitor 1 has finished]
03/01/21 06:47:24.159008 zmeventnotification[28394].INF [main:989] [|----> FORK:Camera devant (1), eid:438 Not sending event end alarm, as we did not send a start alarm for this, or start hook processing failed]
03/01/21 06:48:53.116742 zmeventnotification[1671].INF [main:989] [PARENT: Re-loading monitors]

and that I am totally lost in zoneminder.

[Magic919]

This is not Zoneminder. ZMES is a separate product.

The logs look ok. What are you expecting?

[titof2375]

Ha sorry, or can I find a forum for that because when I pass the camera, I am not notifying anything in mqtt

[Magic919]

I would run through the steps here by manually running things https://zmeventnotification.readthedocs ... leshooting

Then you can post on the Mobile section here or on ZM Slack channel as the author watches both.