Repository navigation
v13.113.0
v13.113.0 - 2026-10-22
- 🚀 Core Events & Devices are broadcast as CoT at most once every 10s per Entity - a create or update is still sent immediately unless that Entity was broadcast within the last 10s, in which case the next scheduled sweep carries it
- 🚀
POST /api/core/devicemirrorsPOST /api/core/event-channelsis required for users and a Connection or Layer token that omits it shares the Device with the active Channels of its Connection, so machine-created Devices are broadcast to the map instead of sitting unshared - 🚀
PATCH /api/core/device/:devicemirrors the Event API -channelscan no longer be cleared, and a Device of a Connection that has no Channels inherits the active Channels of its Connection on its next PATCH so previously unshared Devices reach the map - 🚀
PATCH /api/core/event/:eventfills in the active Channels of the Connection for an Event of a Connection that has none, the same as Devices - 🚀 Connection & Layer tokens can read a Device shared with an active Channel of their Connection, the same rule Events already followed - editing still requires the creator
- 🚀 Access control and Channel sharing for Core Events & Devices is shared through one
EntityControlinstead of separate Event & Device control classes
�