Autonoma Gateway Changelog

Additions, improvements, and fixes to Autonoma Gateways

New

• Network scans now report which networks were skipped for being too large, rather than omitting them silently.

Improvements

• Network scan results are now returned progressively as devices are found, rather than only once the scan completes.
• Network scanning is now limited to one scan at a time, with very large networks automatically capped to keep scans fast and reliable.
• Network scans no longer impact other gateway operations, such as cloud communication, while running.
• The gateway now runs on a newer, more secure Node.js runtime. No action required.

Fixes

• Network scan results no longer include duplicate devices.
• Network scans now always report a final result upon completion.

New

• OPC-UA events and alarms are now supported, allowing alarm conditions defined at the PLC to be surfaced and used for analysis directly in the platform.

Improvements

• Browsing large node trees during OPC-UA connector configuration is now faster, using streaming to retrieve child nodes incrementally instead of all at once.
• Invalid nodes are no longer automatically removed from datastream configuration. A cool-off period now applies first, protecting against configuration loss from temporary connectivity issues.

New

• The Siemens S7 connector now reports errors with specific detail, identifying the failure type: connection failure, connection lost, PLC unreachable, data point not found, or read failure.

Improvements

• Streams suspended due to read errors are now automatically resumed and re-read via RPC after a successful reconnect.
• Error messages now include the specific data point affected, making it easier to identify which sensor or value caused the problem.
• A missing or invalid configuration file now produces a clear error message on startup instead of failing silently.

Fixes

• Fixed data points that hit a read error (e.g. a misconfigured address) being dropped permanently and requiring an app restart to recover; they are now paused automatically and resume once the connection is healthy again.
• Resolved values being treated as unchanged after a PLC reconnect and not resent; all values are now refreshed and sent immediately after reconnecting.

New

• Requests can now be authenticated using Basic auth, a bearer token, or an API key, sent as a header or in the query string.
• A base URL can now be set once and reused by every stream that uses a relative path.
• Per-request timeout and SSL certificate verification are now configurable, preventing requests from hanging indefinitely if a service never responds.
• Responses can now be read as plain text in addition to JSON.
• Values can now be extracted using bracket-path or JSON Pointer notation, in addition to dot-path.
• Requests can now check for a specific expected HTTP status code and treat any other response as an error.
• PATCH is now a supported request method, alongside GET, POST, PUT, and DELETE.

Improvements

• Only boolean, text, and number values are published now; other JSON values, including objects, arrays, and empty or null values, are no longer forwarded unchecked.
• Requests no longer follow redirects automatically, and URLs with embedded login credentials are rejected.
• The configured HTTP method must now match the exact case used by the request (e.g. "GET", not "get").
• Error reporting is now more specific, with separate errors for timeouts, connection issues, authentication failures, and invalid responses.

Fixes

• Fixed the connector stopping entirely when a single stream's request failed; failing streams are now retried automatically and paused independently, recovering on their own once requests succeed again.
• Resolved streams set to update only on value change never sending any updates.
• Corrected POST requests being reported as successful regardless of the actual status code returned by the API.

New

• Hardware-accelerated encoding is now available for video streams, reducing encoding overhead and improving streaming performance (only for supported hardware).
• VNC streams now support Remote Control, allowing mouse and keyboard input to be sent to the remote session directly from the platform.
• Mouse wheel input is now supported during Remote Control sessions.
• Remote Control is now limited to one viewer at a time when multiple sessions use the same stream, so control input only comes from a single user.
• Streams now indicate whether Remote Control is available, making supported streams easy to identify.

Improvements

• Mouse cursor responsiveness during Remote Control sessions has been increased, and stream setup time has been reduced.
• The connector binary size has been reduced.
• Additional RFB pixel format encodings are now supported, extending compatibility with more VNC-based sources.
• Video during fast motion is now clearer and more accurate, with quicker recovery after large screen changes.
• Connections now wait until video is fully ready before completing setup, reducing failed connection attempts.
• Multiple viewers can now watch the same stream in parallel more reliably.
• Streams start more smoothly, with fewer cases of video failing to load after connecting.
• Simultaneous video refresh requests from multiple browsers are now handled correctly.

Fixes

• Fixed a crash occurring when the installation path contained special characters.
• Resolved connection problems caused by TURN server configuration.
• Addressed a failed connection attempt (e.g. to an offline RTSP camera) permanently blocking that stream from reconnecting; a connector restart is no longer required.
• Restored successful connections to VNC servers configured without password security.
• Corrected input latency that increased over time when streaming from certain VNC server applications.
• Stabilized video delivery to additional viewers on hardware-accelerated streams, fixing cases where a second or third viewer received no picture.
• Fixed input latency that increased over time when streaming from certain VNC server applications.
• Resolved a single momentary network error dropping the entire stream.

New

• Gateway LEDs now indicate status, error, and operational state information through color and blink patterns.
• [Limited availability] Support for IoT-Link and DIN-IMX8Plus device types are now available for select customers. General availability is planned for Q2 2026.
• [Add-on required] Streaming support is included by default for customers with the VPN/VNC add-on.
• Container base images have been updated for improved security and stability. No action required.