mqtt-notify/mqtt-notify.service, branch masterMQTT to Desktop Notification script, for use with irssi's mqtt-notify.plhttp://git.mattst88.com/irssi/mqtt-notify/atom/mqtt-notify.service?&h=master2026-09-10T03:51:47Zmqtt-notify: Recover from lost connections2026-09-10T03:51:47ZMatt Turnermattst88@gmail.com2026-09-10T03:51:47Zurn:sha1:45219840a205abc11e11f86ddfc60f87f6f6ed8b
The service runs for as long as the session does, so it has to survive
laptop suspends and network changes. It did not: a connection that died
while the machine was asleep could leave the client wedged, with no way
back short of restarting the unit by hand.
Tighten the reconnect behavior and add a way out when it still fails:
- Bound paho's reconnect backoff to 30 seconds. The default grows to
two minutes between attempts, so even a successful reconnect could
take minutes to happen.
- Drop the keepalive from 60 to 30 seconds so that a connection which
went away without a FIN is noticed sooner.
- Track how long we have been disconnected and exit if that exceeds
two minutes, and set Restart=always in the unit file so that systemd
brings us back with a fresh client. CLOCK_MONOTONIC excludes time
spent suspended, so this does not fire spuriously on resume.
Also stop calling sys.exit() from on_message(). It runs on paho's
network thread, where SystemExit only kills that thread and leaves the
main loop running with no connection. Quit the main loop instead.
mqtt-notify.service: Set PYTHONUNBUFFERED=12020-10-04T06:46:52ZMatt Turnermattst88@gmail.com2020-10-04T06:41:59Zurn:sha1:faf488e04683970f912d857a99ea481808011350
This ensures that the prints appear in journald.
Initial import2019-10-10T06:01:26ZMatt Turnermattst88@gmail.com2019-10-10T06:01:26Zurn:sha1:d297e86f2217a7a5c1ddd66fea12c9ffa34f180e