Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

BACnet4J 7.0.0 has landed with an implementation of BACnet Secure Connect (BACnet/SC). Worth knowing about, but also worth being clear-eyed on what it does and doesn't cover yet.

What's there:

• BACnet4J can now act as an SC node connecting to a Hub. If you already have a BACnet/SC Hub Function on your network (from another vendor's device or software), BACnet4J can join it as a node.
• Alongside it, 7.0.0 brings a batch of spec-compliance work: protocol revision bumped to 20 (with further fixes toward revision 30 compliance), a rewritten segmentation handler (clause 5.4 / addendum 135-2020ch-1), stricter decoding of malformed messages, and the new NetworkPortObject and related structures from the 2024 spec.

What's missing:

• No Hub Function. BACnet4J only implements the node side of BACnet/SC. It cannot act as the SC Hub itself, so you still need a separate Hub (another BACnet/SC device or product) for nodes to connect through.
• Not in Mango yet. This is 7.0.0 of the standalone BACnet4J library. Mango's BACnet data source currently ships BACnet4J 6.1.1 (as of Mango 5.6.11 / 5.7.5). BACnet/SC support has not been integrated into the Mango data source or local device configuration, so you can't configure it from the Mango UI today. That's a separate piece of work from the library update.
• 7.0.0 is a breaking release. If you consume BACnet4J directly in your own code, this version carries a long list of breaking API changes (Unsigned32 vs UnsignedInteger, renamed classes, changed exception types, stricter decoding that can now fail reads that previously "succeeded" with garbage data). It's not a drop-in upgrade from 6.x.

If BACnet/SC support in Mango itself is something you need, let us know in this thread.

Repo and full release notes: github.com/RadixIoT/BACnet4J

Mango 5.6.11 / 5.6.12 (Aug 25 and Sep 1, 2026) and Mango 5.7.5 (Aug 25, 2026) contain fixes for several security issues. If you're running an earlier version on either line, we recommend upgrading as soon as your maintenance window allows.

Affected versions: All 5.6.x releases prior to 5.6.11, and all 5.7.x releases prior to 5.7.5.

Vulnerabilities fixed:

• Privilege escalation (core). Any user with a script engine permission could evaluate scripts with arbitrary roles, including superadmin.
• Path traversal (core). File store operations did not reject paths that traverse a symbolic link pointing outside the file store. A symlink placed inside a file store could be used to escape it.
• Modbus serial permission bypass (modbus-ds). The Modbus serial locator, serial write, and scan tools did not require the data source permission, unlike their IP equivalents. Any authenticated user could write to serial Modbus devices or trigger scans.
• BACnet denial of service (bacnet-ds). A malformed or malicious BACnet message could trigger an infinite loop. Fixed by upgrading BACnet4J to 6.1.1.
• Dependency CVEs. A broad set of third-party libraries were updated to patched versions, including Spring Framework, Spring Security, Jetty, Netty, Jackson, PostgreSQL JDBC, jOOQ, log4j, BouncyCastle, and Apache HttpComponents. lz4-java was upgraded to 1.11.1, fixing CVE-2026-59949 (a native-code JVM crash), and Spring LDAP was upgraded to address CVE-2026-41720.

Breaking changes to review before upgrading:

• Evaluating a script while requesting roles the caller does not hold now fails with a permission error instead of being silently allowed. If any of your scripts request roles beyond what the calling user holds, update them before upgrading.
• (5.7.5 only) The REST API now ignores the read-only id property in request bodies. Object identity comes from the URL path or xid instead.
• (5.6.11 only) BACnet REST serialization of CharacterString values now represents the character encoding as an object rather than a byte.

Also in 5.6.12: a fix for OAuth 2.0 / OpenID Connect logins resetting a user's roles to user when oauth2.client.registration.{registrationId}.userMapping.roles.sync is set to false. Roles assigned by an administrator in Mango are now preserved across logins.

As with any upgrade, back up your database and configuration first and test in a non-production environment before rolling out to production. Full details are in the 5.6.x and 5.7.x release notes.

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.

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.

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.

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

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!

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.

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

Hello @mihairosu,

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

1. 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.

2. 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.

3. 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).

4. 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

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

@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.

v5 Release Notes Overview

Mango 5.5.4 Release Notes (09/25/25)

access-control

• Live only cameras can now be accessed on-demand when motion detection is disabled.
• Added an option to limit the number of active camera readers simultaneously.
• Fixed reader and recorder timing, corrected camera view FPS, resolved reconnection issues, and improved livestream stability to prevent lag and frame loss.
• Live only camera readers prioritize UDP connections for better performance, automatically falling back to TCP if UDP is unavailable.
• Migrate to JavaCV-based video processing pipeline.
• VideoTransformer can be used with FFmpeg or JavaCV implementations.
• Bundles required native dependencies (OpenCV 4.9 / FFmpeg 6.1.1 via bytedeco) for simpler setup.

bacnet-ds

• The BACnet data source now uses the shared local device to emit an IAm message on initialization and listens for IAm messages from other devices to track certain properties.
• Previously, each data source performed these functions independently, resulting in unnecessary messaging.
• When a request for data to a device times out, only the polled points at that device are marked as unreliable.
• Previously, all polled points in the data source were marked unreliable, even if other devices were responsive.

radix-tsl

• Fixed an issue where Mango failed to start up when the TLS module was enabled.

@mihairosu - **Update ** Mango 5.5.3 has been released to the Mango Store yesterday on September 9, 2025.

v5.5.3 - Mango Store Download

v5.5.3 - Release Notes

@mihairosu said in Update core 5.4.1 core 5.5.2 failed:

mihairosu
2 days ago

I tried to update Core and all modules from 5.4.1 to 5.5.2 and now Mango won't start up. I don't have permissions

See link to ma.log file.

Hi @mihairosu,

Thanks for sharing the details and sorry to hear about the trouble after upgrading to 5.5.2.

This issue is related to a known bug that was introduced in Mango version 5.5.0 and will be resolved in the upcoming 5.5.3 release.

In the meantime, a workaround is available:

You can manually change the system setting for the alarm level of the system event MAX_ALARM_LEVEL_CHANGED directly in the database while Mango is offline. Here's the SQL command:

UPDATE PUBLIC.SYSTEMSETTINGS t
SET t.SETTINGVALUE = '0'
WHERE t.SETTINGNAME = 'systemEventAlarmLevel.MAX_ALARM_LEVEL_CHANGED';

This should help bypass the startup issue you're encountering. Once Mango is back online, you can verify the change and proceed with your upgrade path or if your not comfortable making this change wait for the Mango v5.5.3 release.

Let us know if you any further questions or if anything else comes up!

@SGAF Hello, you should be able to export the Meta Data Source and its points directly from the Data Source. Alternatively, you can use the Configuration Import/Export tool to export all data sources and/or data points and then make your edits. Please note that if you remove the XIDs from the Data Points and substitute the XID of the Data Source on the other system, new data points created during the import to the other system will be assigned new XIDs. As you mentioned, context points will need to be mapped. Thank you.

Hello @jcaballeroa, sorry for the delay on this topic but could you please open a support request at Radix IoT - Support? I would like to better assist on this topic but access to the files have expired. Also, have you tried to start a clean Mango v5 to see if you have any issue starting up Mango before upgrading?

@jcaballeroa You mentioned that you are testing Mango 5 in free mode. Could you please tell me how many data points you are using, and send the complete ma.log file again?

Additionally, assuming the server writes logs to /var/log/syslog, you might find more log entries related to Mango’s issues there. I often find the information I need in the syslog when Mango fails to start up correctly.

Thank you.

@jcaballeroa It appears the issue is related to this property:

pki.monitor.expiringSoonThreshold=25%

The problem may stem from unusual locale settings on your computer that do not properly recognize the percentage symbol (%). To address this, follow these steps in order:

Step 1: Modify the property

1. Edit the configuration file containing pki.monitor.expiringSoonThreshold=25%. Change this setting to the decimal format (0.25) instead of using a percentage, pki.monitor.expiringSoonThreshold=0.25.

2. Restart the Mango service to apply the new settings.

If the issue persists, proceed with Step 2:

Step 2: Check your locale settings

1. Ensure your system uses a standard locale, such as en_US, where the percentage symbol (%) is recognized correctly. Adjust your locale settings if necessary.

2. Restart the Mango service again to apply these changes.

Please implement these steps and let us know on the forum whether this resolves the issue. Your feedback is invaluable and can assist others experiencing similar issues.

Hello @jcaballeroa, I'm sorry to hear you're experiencing issues. To better understand the problem, I will need you to provide more details.

• Which Mango version are you using in v3, v3.7.12?
• Did this error start after upgrading to v5.2.1, or did you start with a clean install and your overrides added?
• Please share your SSL properties settings (those you feel comfortable sharing).
• Also, can you confirm that you are running Java 17 for the v5 Mango?

Sharing your ma.log file would greatly help in diagnosing the issue. Thank you.

BR,

Joe Miraglia
SAE/Radix IoT