zmtrigger.pl wont fire an alarm

[olbasoil]

I am trying to use an MQTT event in Home assistant to send a message to Zoneminder to begin a recording. I have recently moved server, and can't get this working again. It used to work on 1.32.3.

Zoneminder 1,34,16 is running in a docker container (from quantumobject/docker-zoneminder) on Debian 10. OPT_TRIGGERS is on, and ZM re-started.

Using Telnet directly to send "1|on+25|0|cause1|text1|" to ZM ip: 6802 (forwarded in Docker) I can see the trigger and 25 seconds later the cancel action in the log, but no alarm event is started and no recording made:

2021-01-01 20:17:12.220970 zmtrigger[13436].INF-zmtrigger.pl [Cancelled event]
2021-01-01 20:17:12.210030 zmtrigger[13436].INF-zmtrigger.pl [Found action '1|cancel']
2021-01-01 20:17:12.200280 zmtrigger[13436].INF-zmtrigger.pl [Found 1actions expiring at 1609532231]
2021-01-01 20:17:05.403271 zma_m1[13424].INF-zm_monitor.cpp/1305 [drive: 4500 - Analysing at 8.33 fps]
2021-01-01 20:17:02.146148 zmc_m1[13421].INF-zm_monitor.cpp/2550 [drive: images:4500 - Capturing at 8.33 fps, capturing bandwidth 48203bytes/sec]
2021-01-01 20:16:53.440272 zma_m1[13424].INF-zm_monitor.cpp/1305 [drive: 4400 - Analysing at 8.33 fps]
2021-01-01 20:16:50.186815 zmc_m1[13421].INF-zm_monitor.cpp/2550 [drive: images:4400 - Capturing at 8.33 fps, capturing bandwidth 48818bytes/sec]
2021-01-01 20:16:46.859730 zmtrigger[13436].INF-zmtrigger.pl [Trigger 'on' 'cause1']

There is only one monitor which is set to Nodect. I can see the feed, and force an alarm manually.

Any ideas on how to get this working again? Or is there a newer way to send an external event in to start a recording?

[Magic919]

I don’t know about fixing that, but the ZM api would be another method.

[olbasoil]

I don’t know about fixing that, but the ZM api would be another method.

In case others are looking at this issue, I can confirm that this is good advice. I have added the nodered integration to home assistant, and that gives an easy way to connect to the ZM api.
I had used the telnet route for a few years, and still have no idea what went wrong, but I can see that the API is far more secure and future proofed.

[Magic919]

Thanks for updating the thread.