Problem with setting up security mode

Hello!
Several Hub M1S Gen 2 centers are used and opening and motion sensors are connected. The night mode of arming by timer is used. When any sensor is triggered, only one Hub M1S Gen 2 gave a siren signal with a 2-second limitation. Everything worked fine for one week, but then the following happened. If the security sensor is triggered, the siren emits a signal continuously without a time limit. It can only be turned off by pressing the notification button on the phone, and after that the night light on the concentrator lights up, which has to be turned off manually in the program. In addition, the list of alarm ringtones has stopped displaying in the security triggering settings, due to which the program does not allow changing the sounding time. When trying to save the settings, it asks to select a ringtone from the list, but the list is empty. There are 4 users in the system. The situation is repeated under different users and for any concentrator in the system. Why could this happen and how to fix the problem? Thank you.

@mintukov Hello!

It sounds like you’re experiencing a few issues with your Hub M1S Gen 2 setup, particularly with the security mode and alarm settings. Based on the reference information, there are a few things you might want to check:

  1. Alarm Duration and Ringtone Settings: The problem with the siren continuously sounding might be related to the settings within the Aqara Home app. Since the list of alarm ringtones is not displaying, it could be a software issue. Make sure that your app is updated to the latest version, as updates often fix bugs that might cause issues like this.

  2. Multiple User Setup: Since the issue occurs under different users, there might be a setting conflict. Ensure that all users have the same app version and that the app permissions are correctly configured for all devices.

  3. Automation and Scene Settings: The Hub M1S Gen 2 supports various automation actions such as turning the night light on/off when a certain condition is met. Ensure that your automation rules haven’t been inadvertently changed, which might affect how the siren and night light behave.

  4. Resetting the Hub: If the problem persists, consider resetting the Hub M1S Gen 2 by long-pressing the reset button until the yellow light blinks. This can sometimes resolve persistent software glitches. However, note that this will also require you to set up your Hub again.

  5. Wi-Fi and Network Issues: Make sure your hub is connected to a 2.4GHz Wi-Fi network, as it might affect the connectivity and functionality of the hub.

If these steps don’t resolve the issue, it might be best to reach out to Aqara’s customer support for further assistance. You can contact them via the Aqara Home App by going to Profile > Help & Feedback > Customer Service or scanning the QR code below:

If you do not have an Aqara Home account, please click here to create a ticket.

I hope these suggestions help you get your system back in working order! If you find a solution, please share it with the community, as it can help others facing similar issues.

Are there any developers on this forum?

@mintukov Hello mintukov! While the forum primarily consists of users sharing experiences and tips, there are sometimes developers and technical experts who participate as well. If you have specific technical questions, feel free to post them—there might be someone with the expertise to help. You can also consider reaching out to Aqara’s official support channels for direct assistance from the developers or their technical team.

Can you provide a list of official channels for contacting the developers?

@mintukov Certainly! For official channels to contact Aqara developers, you have a couple of options:

These channels should help you connect directly with Aqara’s technical and business teams for more in-depth assistance. If you have further questions or if there’s anything else you want to discuss, feel free to continue the conversation here. The community is always eager to help!

Looks like it is a bug, please contact the customer team directly