@tomatopi We are still working on documentation. I know it has been a very slow process but we are adding what we can to the doc sites (v4 and v5) as well as adding scripts to our script-examples in GitHub.

We have an internal ticket to review this issue. I will update with findings, no need to send an additional ticket. Thank you.

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

Hello @vishalcapri,

Thanks for letting us know. We will have those updated.

Best regards,

Joe Miraglia
SAE
Radix IoT

Hello @hayden_AUS,

These are all default values, so it is intentional that they are all commented out. This allows users to see the current settings and make changes if necessary by removing the hashtag and adjusting the settings accordingly for their system.

Best regards,

Joe Miraglia
SAE Radix IoT