Protocol Use Cases
| Protocol | Plausible Use Cases | Operations | Underlying Implementation | Security |
|---|---|---|---|---|
| HTTP | Web Apps |
Properties, Actions, Events |
tornado |
username-password, device API key, IP filter, OAuth2 OIDC |
| ZMQ TCP | Networked Control Systems, devices in protected networks, containerized apps like in Kubernetes |
Properties, Actions, Events |
pyzmq | planned, likely may take upto end of 2026, please use HTTP if needed. Its not slow. |
| ZMQ IPC | Desktop Applications, Python Dashboards without exposing device API directly on network (streamlit, dash, panel etc.) | |||
| ZMQ INPROC | High Speed Desktop Applications (again, not exposed on network), currently you will need some CPP magic or disable GIL to leverage it fully | No security, meant for in-process communication only | ||
| MQTT | Reliable pub-sub & incorporating into existing systems that use MQTT for lightweight messaging |
Properties that emit change events, plain Events |
aiomqtt/Eclipse Paho |
username-password, TLS with client certificates (you set this up in the broker anyway) |
| MQTT with websockets | planned for April/May 2026 release. | |||
| CoAP | Planned, April 2026. | Will be updated | aiocoap | Will be updated |