Repository navigation
Keeps pace with large OPC-UA servers and shuts out what should not reach the
device. Pages open fast against tens of thousands of variables, values return
within a second of a reconnect, struct arrays are read by position with their
members, and the browser redraws only what changed. A Dropdown can write a
variable and $compare gains contains. Projects stay at file format 12, so
a project saved by 1.3.0 still opens in 1.2.0. Read Changed before you
update: a username sign-in over a secured OPC-UA endpoint waits until you trust
the server's certificate, a site that shows NEXT HMI in a frame must be listed,
a custom widget bundles files from custom-widgets/ and external-libraries/
only, and the Docker image runs as uid 10001.
Added
- Pick the browse root from the tree
start-dev.pychecks the dependencies- A Dropdown writes to a variable
- Filter a list as the operator types
- Which release opens which project
Fixed
- The page tree opens fully collapsed
- Browse uses the settings you just typed
- A component input bound to an array element showed red
- A Repeater over an array of structs showed its members as no data
- Edit Value on a Repeater item showed no range
- A Repeater over a PLC array that counts from 1
- Pages open fast on a large OPC-UA server
- Writes to TwinCAT and S7 PLCs were refused
- A page with about 1,800 bindings never loaded
- The no-connection cross no longer flashes on every navigation
- The runtime no longer stalls on a page switch against a large PLC
- A struct-array binding at a fixed index could show the wrong element
- A page could stop updating when several panels switched pages at once
- Large pages no longer drop the TwinCAT connection
- Values arrive sooner after a PLC reconnects
- Values were missing after the HMI connected to a PLC
- An outage no longer leaves load behind on the PLC for hours
- A page subscribes only what it shows
- A sidebar or variable trigger reading a whole array got no value
- Fewer requests per page switch
- Browser memory stays bounded on long sessions
- A variable removed from a datasource could reappear on an open screen
- Large Repeaters stay smooth
- Recipe change indicators follow the live values
- A header or sidebar showing one element of a struct array updates live
- Alarm text reads one element of a struct array as a page does
- A variable no longer goes without values after a busy PLC refused it
- A PLC that stops publishing a subscription is reconnected cleanly
- Saving a datasource's settings no longer undoes variable edits
- An agent's variable edit and an editor save no longer undo each other
- A static variable write updates the struct around its array
- Alarms and popups no longer redraw every widget
- No red flash when a page's metadata arrives late
- Saving a datasource no longer stalls live values
- Bursts of struct-array changes cost less
- Fast-changing struct arrays cost less server CPU
- The first page after a start or a datasource save no longer pauses
- Nested arrays of structs keep their shape
- Struct bindings deliver their nested arrays
- Re-browsing a large server is faster
- The Linux download starts on Ubuntu 24.04 again
- On Windows, a save or widget build could fail while a virus scanner held the file
- A translation key with
?or#in it reached the instance cut off - Starting a project from a source checkout used a different runtime home than the manager
Changed
- First-run setup asks for a setup code
- Secured OPC-UA connections wait for a certificate you trust
- The OPC-UA test server stays on the device
- Other sites can no longer show NEXT HMI in a frame
- Pairing with another device confirms its certificate first
- A project that carries code asks for trust before it is installed
- Custom widgets bundle files from
custom-widgets/andexternal-libraries/only - Writes to a disabled variable are refused
- Limits on what the open screens can ask for
- MCP asset uploads take image types only, and SVGs are rebuilt
- Sign-in locks only the address that keeps guessing
- Dashboard sign-ins can be ended
- A new device-admin password needs at least 8 characters
- Settings › Tokens lists paired devices
- Project ids ignore upper and lower case
- A Web Frame keeps its messages to the site its URL names
- The Docker image runs the app as the user
nexthmi(uid 10001) - A project serves at most 500 open screens at once
- A crashed project shows
startingwhile it restarts
Security
- A disabled OPC-UA variable could be written and read from the network
- A text variable bound to an icon could run script on the dashboard's address
- A project's widget build could read files elsewhere on the device and publish them
- An MCP write token could store a script in an asset, and a crafted SVG could freeze the manager
- Pairing could send the other device's admin password to an impostor on the network
- A website could claim a new install through DNS rebinding
- A website could frame the runtime screens and trick a click into a write
- The OPC-UA test server accepted an administrator with any password from the network
- The OPC-UA client trusted any server certificate
- Large request bodies, WebSocket messages and historian queries could exhaust the device's memory or stall it
- An MCP read token could read datasource passwords
- The
mcppackage moves to 2.2 or later - Five wrong passwords from anyone locked every admin out for a minute
- A copied dashboard cookie kept working after signing out
- A device-admin password could be one character long
- Any process on the device could call a project instance directly
- A
.or..segment in an editor path reached the instance's internal reload hook - A paired device could fill the disk or memory with its replies
- A flood of mDNS announcements could grow the manager's memory without limit
- Project ids that differ only in case shared folders on Windows and macOS
- On Windows, a theme id could read, write or delete
*.jsonfiles outside the project - Reusing an MCP idempotency key on another project or token skipped the write
- Another local user could freeze an instance through its translation lock in the shared temp directory
- A client could keep the PLC resubscribing and the live view busy
- A Web Frame sent its outbound value to whatever site it showed
- The Docker image ran the app as root
- Frontend dev dependencies are updated past npm audit findings: