Every plan gets every protocol, and extensions can add rule chain nodes

v0.1.59
•Platform

Features

  • Plans: protocol support no longer varies by plan. Every cloud plan can run every protocol, including BACnet, DNP3 and EtherNet/IP. Any protocol connection that a plan restriction had switched off is switched back on automatically after this update, and connections you disable yourself stay disabled.
  • Rule Chains: installed extensions can add their own action nodes to the Rule Chain editor. Extension nodes appear in the palette under their provider, come with a parameter form (device pickers, text, numbers, choices and expressions), and compile the same way whether you build the chain in the browser, let the node compile it automatically, or ask the AI assistant to write it. A chain that uses a node from an extension that is not installed is refused at load time instead of being silently altered.
  • Calendar: events can now fire hooks before they start. Set one or more lead times in minutes (for example 30, 20 and 10) and each fires once per occurrence with the lead time passed to the hook. Lead times that were already missed when a node starts are skipped rather than replayed all at once. Pre-start hooks are edited in the Calendar app alongside the existing start, end and periodic hooks.

Bug Fixes

  • Calendar: saving an event no longer rewrites lead times that are not a whole number of minutes, and the editor only writes lead times back when you actually changed them.
  • Calendar: a momentary lookup failure while opening an event no longer makes a later save silently skip some of its fields.