Scheduled Maintenance (21-Apr-2025)

[Piyush]

As part of our commitment to providing a reliable and high-performing service, we will be conducting scheduled maintenance for some optimisations to our backend infrastructure.

Maintenance Schedule:
Date: 21st of April 2025
Time window: 03:00 – 05:00 UTC

During this time, our API endpoints may be temporarily unavailable and nodes may disconnect intermittently. However, the default retry logic will ensure that they connect back.

If you have any questions or concerns, please contact us at esp-rainmaker-support@espressif.com

[rajsimiot]

My nodes are still disconnected and when restarted its connecting and disconnecting continuously. Is the upgrade still going on or there is some issue ? as the update time has already exceeded.

[rupeshk74]

Hi,

The devices are now online and more stable after continuously going ONLINE and OFFLINE for more than an hour during the scheduled Maintenance, but now I have another issue that is I noticed that the alerts on iPhone are not displaying the actual custom messages sent using esp_rmaker_raise_alert("Front Door Opened"); in the Arduino code.

Instead, the iPhone only shows a generic message: "Alert received from a device", and the detailed text is missing. Additionally, these notifications are not appearing in the app’s notification history under Settings > Notifications.

This reduces the usefulness of alerts, as the actual context of the message is not visible.

Could you please help us resolve this issue?

Regards,
Rupesh

[Piyush]

I tested node alert notifications with the switch example, with CONFIG_EXAMPLE_ENABLE_TEST_NOTIFICATIONS set, which then alternates between using esp_rmaker_raise_alert() and esp_rmaker_param_update_and_notify() as you keep toggling the switch using BOOT button. On both, iOS and Android, the notifications were received and displayed correctly.

Media (15).jpeg (151.65 KiB) Viewed 8974 times

I have not tried with Arduino, but it is expected to be similar.

[Dorian]

Hi,

Something changed in the IOS Rainmaker that now breaks the Rainmaker alerts.
Similar to the previous post, longer alerts (2-3 lines) are not working anymore, and a simple "Alert received from a device" is sent. More than that, all alerts are received with 5-6 seconds delay or even more.

I've been using Rainmaker for a long time with both the official ESP32-S2-MINI-2 module and some clones, and this issue affects all of them equally. The problem appears to have started after updating to iOS version 18.4.1.

To make things worse, as of today, I can no longer connect to Rainmaker at all. Any attempt at provisioning fails and leads to the following "Confirming Node association" error "Node addition not confirmed" (validated also with older baselines and accounts).

Updated to the latest Rainmaker component 1.5.4 version and running IDF 5.1.6.

Are there maintenance activities ongoing?

Thank you

[vikas.chandra]

Hi,

Something changed in the IOS Rainmaker that now breaks the Rainmaker alerts.
Similar to the previous post, longer alerts (2-3 lines) are not working anymore, and a simple "Alert received from a device" is sent. More than that, all alerts are received with 5-6 seconds delay or even more.

I've been using Rainmaker for a long time with both the official ESP32-S2-MINI-2 module and some clones, and this issue affects all of them equally. The problem appears to have started after updating to iOS version 18.4.1.

To make things worse, as of today, I can no longer connect to Rainmaker at all. Any attempt at provisioning fails and leads to the following "Confirming Node association" error "Node addition not confirmed" (validated also with older baselines and accounts).

Updated to the latest Rainmaker component 1.5.4 version and running IDF 5.1.6.

Are there maintenance activities ongoing?

Thank you

Hi @Dorian ,

Thank you for bringing this to our attention. To investigate this further, could you please help us with the following information:

How is the node alert being triggered?

Node ID(s) of the affected devices — this will help us check the AWS logs for any anomalies or delays.

Looking forward to your response so we can assist you further.

[Dorian]

Hi @vikas.chandra

Thank you for your answer.

The delay and node allocation started to work as before since Saturday, so I suppose it was a temporary issue. I have used the same software/baseline, so nothing was changed in the code. Now, there are no delays or node allocation issues anymore.

The only issue that remains is regarding the alerts. I have observed that only using "\n" (new line) in the alert text caused this "Alert received from a device". Without new lines, I don't see a limitation in the size of the alert.

Previously, when there were no "Push notifications with sound" on IOS, I could send alerts that contained new lines and receive the notification properly formatted on my iPhone (with no default notification sound indeed). After the 3.1.0 update (03-Apr-2025), the sound was added to the notification, but also this limitation as well.

The Node ID is 10003BFBC214. The alert is triggered via esp_rmaker_raise_alert, and I don't see any error in the console logs.

Please let me know if I can provide extra info.

[vikas.chandra]

Hi @vikas.chandra

Thank you for your answer.

The delay and node allocation started to work as before since Saturday, so I suppose it was a temporary issue. I have used the same software/baseline, so nothing was changed in the code. Now, there are no delays or node allocation issues anymore.

The only issue that remains is regarding the alerts. I have observed that only using "\n" (new line) in the alert text caused this "Alert received from a device". Without new lines, I don't see a limitation in the size of the alert.

Previously, when there were no "Push notifications with sound" on IOS, I could send alerts that contained new lines and receive the notification properly formatted on my iPhone (with no default notification sound indeed). After the 3.1.0 update (03-Apr-2025), the sound was added to the notification, but also this limitation as well.

The Node ID is 10003BFBC214. The alert is triggered via esp_rmaker_raise_alert, and I don't see any error in the console logs.

Please let me know if I can provide extra info.

Hi @Dorian ,

Thank you for the detailed update.

Based on your observation and the reported error, it appears that the issue with the alerts was caused by the presence of unescaped newline characters (\n) in the alert string. On iOS, such unescaped control characters can lead to JSON parsing failures, which explains why the alert was not handled correctly.

To resolve this, you can modify your alert message by escaping the newline character using a double backslash (\\n). For example:

Code: Select all

esp_rmaker_raise_alert("Switch was turned off.\\nPlease check.")

This ensures that the JSON payload remains valid and is parsed correctly by iOS.

Let us know if you observe any further issues.

[Dorian]

Awesome, this solves all the issues, now everything is working perfectly.
Many thanks @vikas.chandra