Repository navigation
Integrations
A required dependency must be installed and compatible before activation. An optional dependency adds a feature only when that plug-in is installed, enabled and healthy. Each plug-in page lists both kinds and links directly to their documentation.
Plug-ins declaring ospy.provider.v1 expose cached measurements, resources and explicitly declared actions to consumers such as Automation Rules. Reading a provider value must not trigger another hardware measurement. Provider actions are available only when declared by a running compatible provider and invoked through OSPy's validated action entry point.
A manifest with Mobile API v1 can provide status cards, measurements, history, guarded actions or downloads to a compatible OSPy mobile client. The exact capabilities are listed on the plug-in page and may require a minimum OSPy or mobile-app version.
Common service plug-ins include Database Connector for SQL storage, MQTT for broker access, Shelly Cloud Integration for cached Shelly devices, RS485 Communication for serialized bus operations and the notification plug-ins used by monitoring and automation extensions.
Start
Reference
Catalog sections