Tunnel Client: a new extension that publishes a service on your local network on a port of a remote ControlBird node, over an outbound HTTPS tunnel. Each tunnel is set up on its own, picks up edits without a restart, and shows its status and last error.
IO Manager: the IO Manager service ships as its own extension.
Integrations: ESPHome, Tuya, Zigbee2MQTT, Z-Wave JS UI, PulseAudio, SMTP, Aladhan, Open-Meteo, WeatherAPI, Google TTS and Telegram suggest a tag ID for every data point when you add devices, and find the tags they made before, renamed ones included, when you add devices again.
Tuya: adding devices reads each product's data points, so every data point gets its own tag.
Z-Wave JS UI: each Z-Wave node is its own device, so two nodes of the same model are two devices.
SMTP: a second SMTP instance no longer collides with the first.
Demo Scene: a Demo Simulation connection tags every simulated value.
Bug Fixes
DNP3: the outstation serves published tags, and a master command updates its tag once, at any index.
DNP3: binary inputs, analog events and multi-header reads follow the IEEE 1815 object layouts, and master tags read the point their source names.
DNP3: responses larger than one fragment are sent in confirmed fragments instead of being cut off, unsolicited responses wait for their confirmation and are retried, and the master discards stale fragments.
OPC UA: the client signs in with a configured username and password, which Engineers and above may set, and the server uses its configured security policy, mode and certificate.
MQTT: the embedded broker applies its queue limit and keep alive settings.
EtherNet/IP: tags honour their array index and element count.
Modbus: Modbus server tags pass on a received write only when the value changes, while other server protocols pass on every write.
⚠️ Breaking Changes
These extension versions require platform v0.2.22. A node on an earlier version keeps the extension versions it has.
OPC UA: the security policy and message security mode are now chosen from a list. A node that already has OPC UA installed must uninstall and reinstall it to upgrade, and its OPC UA connections must be set up again.