How live updates work

What are live updates?

ZenDRIVE publishes an event whenever content changes in the storage network. You can subscribe to those events over MQTT and react immediately — for example, refreshing a mounted view or kicking off a media-library scan — so new files appear without you polling for them.

Why would I use them?

If you mount the storage (for streaming) or keep a local index, live updates keep that in sync automatically. Without them, your mount's cache or your media server might not notice new content until its next scheduled refresh.

Do I have to use MQTT?

No. It's entirely optional. ZenDRIVE S3 Access works fine with plain list and download. MQTT just removes the manual "check for new files" step.

How do I receive the events?

Run a subscriber that connects to the ZenDRIVE MQTT broker and acts on each message. The supported tool is ZenLocalPoller — see Setting up ZenLocalPoller. Any standard MQTT client can also subscribe if you'd rather build your own.

What's in an event?

Each message identifies content that changed in the storage, so your subscriber knows what to refresh or fetch. ZenLocalPoller turns these into rclone cache refreshes and optional media-server scans for you.

Is the stream secured?

Yes — the broker is reached over a TLS connection (WSS on port 443) and requires the MQTT credentials issued with your service. See Setting up ZenLocalPoller.

What do the events let me do?

• Refresh an rclone mount so new files appear instantly.
• Trigger a media server (Sonarr, Radarr, Lidarr, …) to scan just the changed paths.
• Drive any custom automation that should run when new content lands.