Overview: Events and integrations
Events and integrations connect server observations with accepted work and effects in other application lifecycles.
An event can arrive more than once, and a successful receipt can precede a downstream action. Permissions and notification rules add further decisions, while an in-process plugin follows the host's own extension lifecycle. This area gives those boundaries enough context to build a coherent workflow around Emby state.
Receiving events and state
Event and state reception uses pushed messages or repeated queries with different timing and recovery properties.Event delivery and retries
Event retries recover from uncertain delivery but can duplicate processing, so event identity, durable recording and effect semantics need separate boundaries.Integration permissions
Integration access depends on the accepted identity and permitted operation at each system involved, including server policy and underlying resource access.Plugins
Plugin architecture and compatibility connect an extension's code and persisted state with the host's supported contracts.Notification delivery
Notification delivery connects a source event to a selected recipient through processing and provider stages, each with its own completion evidence.Playback events in home automation
Playback-driven home automation maps particular player observations into room policy and physical effects, with multiple sessions and uncertain events requiring explicit state handling.