administrators group

joeamiraglia

Radix IoT's documentation has moved to a single, unified site: docs.radixiot.com. There's no separate v3 or v4 documentation anymore. Everything lives in one place now.

Sections:

Getting Started: installing Mango by Radix IoT, configuring your first data source, connecting your first device
Data Sources: OPC UA, Modbus, BACnet, MQTT, SQL, and 20+ industrial protocols
Configuration: publishers, event handlers, scripting engines, system settings
User Guide: data points, alarms, events, reports, dashboard designer
Administration: backups, database, diagnostics, logging, upgrades
Security: SSL/TLS, OAuth 2.0, user permissions, audit trails
Developers: REST API reference, module development, tutorials
Hardware: IO expansion tools and hardware integrations
Release Notes: per-series changelogs for every Mango 5.x release

There's a search bar in the header if you'd rather jump straight to a topic than browse.

If you run into a page that's missing something or out of date, flag it here. The site is actively maintained.

joeamiraglia

Summary of the Mango 5.7.x series (5.7.0 – 5.7.4). Full changelogs are on the documentation site.

5.7.0 (Apr 28, 2026) — Major release: Spring 7, Jetty EE11, and Jackson 3 upgrades; new open-source OPC UA data source built on Eclipse Milo; Maven-based upgrade delivery with PGP signature verification. Breaking changes: five modules removed (Control Core, Environment Canada, log4jDS, MangoIOTools, MangoES Configuration), CSRF now enforced on /httpds and /haystack, and the default gRPC service permission changed from superadmin-only to all users. Third-party modules built against 5.6.x APIs will not load — review the upgrade guide before moving to this series.
5.7.1 (May 13, 2026) — Same ClickHouse/TSL driver upgrade as 5.6.6; Excel report rollups now work correctly on TSL-backed installations.
5.7.2 (Jun 29, 2026) — Major camera-streaming overhaul: substantially lower CPU usage, smoother live video, more reliable connections; fixed a 5.7.0 regression that could crash the web server into a restart loop on certain blank mango.properties values.
5.7.3 (Jul 15, 2026) — Added OPC UA write-back support; isolated SNMP v3 credentials per target (security fix); fixed several data-source startup and event-handling issues.
5.7.4 (Aug 12, 2026, latest) — Added OAuth 2.0 bearer-token role-claim mapping; fixed a silent logging failure that could stop all logging on 5.7.0–5.7.3 after a runtime config reload (worth an immediate upgrade if you're on those versions); EMS/Platform Manager permissions are now enforced server-side rather than in the browser.

If you're upgrading from 5.6.x, read the 5.7.0 breaking changes carefully — this is a major-version-style jump for modules and integrations even though it's numbered as a minor release.

joeamiraglia

Summary of the Mango 5.6.x patch series (5.6.0 – 5.6.10). Full changelogs are on the documentation site.

5.6.0 (Dec 1, 2025) — Java 25 build support (Java 17 remains minimum), new Prometheus metrics endpoint, gRPC publisher offline queuing, multi-level email escalation, redesigned event-handler management UI.
5.6.1 (Dec 5, 2025) — Fixed the Users page loading all rows and producing infinite queries; fixed a circular-dependency exception on startup when an active event exists in the database.
5.6.2 (Dec 15, 2025) — Jetty upgraded to 12.1.5, resolving stale file content being served after on-disk changes; several EMS device-details fixes.
5.6.3 (Feb 19, 2026) — Improved NoSQL (ias-tsdb) "reload links" performance; EMS/Platform Manager filtering and UI fixes; Modbus tools UI now supports multi-select.
5.6.4 (Mar 10, 2026) — radix-tsl upgraded to 0.5.2 with multi-series query support; EMS null-check fixes.
5.6.5 (Mar 23, 2026) — Made ClickHouse FINAL query behavior optional for better performance; fixed gRPC publisher dropping inactive events re-raised after a crash.
5.6.6 (May 13, 2026) — ClickHouse JDBC driver moved to the official upstream release with retuned table defaults, improving ingest and query performance on TSL-backed installs. Requires manually migrating existing tables to take effect — see the docs before upgrading.
5.6.7 (Jun 16, 2026) — Fixed a startup issue affecting Modbus serial (ASCII/RTU) data sources.
5.6.8 (Jun 23, 2026) — Fixed a Cloud Connect user-sync bug that could break the client's web interface; breaking change: MySQL row-by-row result streaming removed (db.fetchSize=Integer.MIN_VALUE is no longer valid), backported from 5.7.
5.6.9 (Jul 22, 2026) — Fixed several data sources (ASCII File, Data File, TCP/IP) failing to register on startup; fixed BACnet/Modbus/gRPC write-back events not firing; fixed a Watchlist JSON import bug dropping chart configuration.
5.6.10 (Aug 4, 2026, latest) — Fixed chart data stopping updates when 3+ points are selected without combine-values.

As always, review the full release notes for your upgrade path before updating a production system.

joeamiraglia

Hi everyone,

The Radix IoT team will be at the following events for the rest of 2026. If you're in the area — whether or not you're attending the show itself — reply below or reach out to your account rep and we'll do our best to set up time: a quick coffee, a sit-down meeting, or a visit to see your Mango by Radix IoT deployment in person.

Upcoming Events:

RE+ MidAtlantic — Philadelphia, PA (Pennsylvania Convention Center) — Aug 12–13, 2026 — Booth 1005
AEE World Conference and Expo — Orlando, FL — Sep 16–18, 2026 — Booth 308
Yotta Show — Las Vegas, NV (Caesars Forum) — Sep 28–30, 2026 — Booth 1119
Smart Buildings — London, UK (ExCeL) — Oct 14–15, 2026 — Booth A17
DCD Connect — Lansdowne, VA (Lansdowne Resort & Spa) — Nov 3–4, 2026
IFMA World Workplace — Anaheim, CA — Nov 17–19, 2026 — Booth 1015

joeamiraglia

Hey Mango community,

We're excited to share that Radix IoT has launched a brand new website! We've put a lot of work into making it cleaner, easier to navigate, and a better reflection of everything we've been building.

Whether you're a long-time Mango user or just getting started, head over and take a look. You'll find:

Updated product information
Improved navigation and layout
Resources to help you get the most out of Mango

Check it out at Radix IoT and let us know what you think!

joeamiraglia

Hey everyone,

I wanted to see if anyone here has started using Portfolio Manager (Pi‑Portfolio) and would be willing to share their experience so far.
Specifically, I’m curious:

How you’re using it today (internal ops, customer reporting, multi‑site rollups, etc.)
What’s working well
Any challenges or gaps you’ve run into
Features you’d like to see improved or expanded

For reference, this is the documentation site Pi‑Portfolio is based on:

👉 https://docs.radixiot.com/docs/developers/tutorials/pi-portfolio/

If you’ve had hands‑on time with it—even in a limited or test capacity—I’d love to hear your thoughts.

Thanks in advance.

posted in User help

@mihairosu FYI - Image issue with the forum has been fixed.

posted in User help

Hello @mihairosu,

It sounds like your diagnosis is on the right track. Here are the most likely causes based on what you’ve described:

Check that the guest user actually has the Users role
Since the point shows Users = checked and Anonymous = unchecked, the guest account must:

Be successfully logged in
Belong to the Users role

If the guest account was created manually rather than through the usual user-creation workflow, it’s possible it never received that role.
You can verify under Administration → Users → guest.

Confirm whether auto‑login is actually succeeding
If your auto‑login fails silently, Mango will treat the session as Anonymous, and any point that does not allow Anonymous access will simply disappear with no warning.
To verify:

Open your dashboard URL in a private/incognito window
Check whether Mango shows you logged in as guest

Also, your example URL uses:
autoLoginPassword=guest1234

But you mentioned the password is guest. If those don’t match, the login will fail and the session becomes anonymous.

For meta points specifically

Meta data points inherit visibility from their own permissions, but their values come from underlying source points.
If the guest user does not have permission to read one of the source points a meta point depends on, the meta point may appear on the dashboard but will fail to resolve a value.
So make sure the source points also include the Users role (or whatever group your guest belongs to).

Version change (5.6.2 → 5.6.3)

Since this was working before the upgrade, it’s worth checking the 5.6.3 release notes. There have been a few changes recently around role evaluation and anonymous access. Even subtle permission tweaks could affect dashboards that rely on auto‑login.
https://docs-v5.radixiot.com/v5-release-notes-overview

posted in User help

Hello @mihairosu, Single data point not publishing from MangoES to MangoEnterprise, steps to try:

If other points on the same publisher are working but one specific point is not arriving on the Enterprise side, the most common cause is an XID mismatch introduced when the point was removed and re-added to the publisher. Work through these steps in order:

On MangoES:

Go to Publishers and open the publisher sending to MangoEnterprise
Find the entry for the affected data point and note its Published Point XID (this is separate from the data point XID, it typically looks like PP_xxxxxxxx)
Confirm the data point itself is healthy: add it to a Watch List and verify it is receiving fresh values from the Modbus source
Confirm the data point's Logging Type is not set to Do Not Log, some publisher configurations will not forward a point that has no logged values

On MangoEnterprise:

Go to the Data Source that receives published data from MangoES
Find the data point that is supposed to receive this value and open its configuration
Look at the Point Locator, it will contain the Published Point XID it is listening for
Compare this XID to the one you noted on MangoES, if they do not match, this is the cause

To fix:

Update the Point Locator on the MangoEnterprise data point to match the current Published Point XID from MangoES
Save the data point, then disable and re-enable the data source on MangoEnterprise to force it to reconnect

If the XIDs already match, also check:

The data point and its data source are both enabled on MangoEnterprise
The data type on the Enterprise point matches what MangoES is sending (e.g., both NUMERIC)
The publisher on MangoES shows a healthy connection status with no errors

The remove/re-add step almost always generates a new Published Point XID on MangoES while the Enterprise side still holds the old one, updating the Point Locator on Enterprise is usually all that is needed

joeamiraglia

@Jdiaz-co said in Timeout to lock table systemsettings:

hello good,

I'm having a problem. I'm using Mango 3.7.7 and the application crashes every so often.

The error I'm getting is this:

ERROR 2025-10-27T08:26:50,187 (com.serotonin.m2m2.util.timeout.TimeoutTask.run:61) - Uncaught Task Exception
org.springframework.dao.CannotAcquireLockException: PreparedStatementCallback; SQL [select settingValue from systemSettings where settingName=?]; Tiempo vencido intentando trabar (lock) la tabla "SYSTEMSETTINGS"
Timeout trying to lock table "SYSTEMSETTINGS"; SQL statement:
select settingValue from systemSettings where settingName=? [50200-199]; nested exception is org.h2.jdbc.JdbcSQLTimeoutException: Tiempo vencido intentando trabar (lock) la tabla "SYSTEMSETTINGS"

I would appreciate any help.

thank you

Hello,

This error comes from the embedded H2 database: something is holding a lock on the SYSTEMSETTINGS table too long, so reads (like select settingValue from systemSettings…) time out and throw CannotAcquireLockException.

Common causes:

Another process/tool (H2 console, external SQL client) connected to the same H2 DB while Mango is running.
Long-running DB operations (backups, purges, heavy writes) that keep the table locked.
Short default H2 LOCK_TIMEOUT (1s) causing normal contention to show up as errors.

Things to try:

Make sure only Mango is connected to the H2 DB (no external tools while it’s running).
Increase H2 lock timeout in env.properties/mango.properties, e.g.
db.url=jdbc:h2:${ma.home}/databases/mah2;LOCK_TIMEOUT=10000
Check logs around the crash time for other FATAL/DB errors that might be the real shutdown cause.

If this is a production system (not just a test setup), I strongly recommend:

Migrating from H2 to MySQL (more robust under load and concurrency).
Upgrading Mango to a more recent supported version if possible, to benefit from DB and stability fixes.

administrators

Posts

Member List