Web Relays no longer work from SmartPlus (R25A)

Web Relays no longer work from SmartPlus (R25A)

2025-10-11 20:50 171 Views [Software&Cloud]

Edited by lix91 at 2025-10-11 20:54

Hello everyone,
I’m having an issue with the web relays on my R25A.

I’m currently running firmware 25.30.10.11.Everything used to work perfectly, but without making any changes, the webrelays have recently stopped working from the SmartPlus app (I’m using an iPhone).

My configuration (as shown in the attached photobelow) includes two web relays. When I first set everything up many months ago,I entered the numbers 1 and 2 in the “Web Relay Key” section todistinguish between the two relays. Previously, SmartPlus worked perfectly: Icould open door 1 and door 2 separately.

Now, this is what happens: with theconfiguration shown in the photo below, when I tap on SmartPlus, I get themessage “Door opening succeeded,” but nothing actually happens: the web relayis not activated. However, if I delete the values “1” and “2” from the “WebRelay Key” fields in the R25A configuration (leaving them blank), and then tapagain on SmartPlus, both web relays are activated simultaneously. This makes itunusable for me, because I need to be able to choose which door to open, ratherthan opening both at once.

It therefore seems that something has changedon the cloud side: the web relay keys are no longer being recognized.

I also tried updating the R25A firmware toversion 25.30.10.117, but it’sunusable for me, since with this version my SIP account doesn’t register to the cloud, for reasons I don’t understand.

I hope someone can help me.
Thank you very much.

This post contains more resources

You have to Login for download or view attachment(s). No Account? Register

All comments 5

Akuvox_Mia 6 day(s) ago

Hi, we need to verify this and will get back to you later.

1 Reply

Akuvox_Mia 5 day(s) ago

Web relay key actually matters with the settings on cloud. When adding device, you must have added multiple relays ,and ask you to setup the DTMF value. So for relay 1, the value need to be 1,then it can trigger action ID01, and for relay2, the value need to be 2, see picture below:

So we wondering whether the value have changed?

The other way to realize seperated trigger is through action URL, and for wbe relay tpye, need change to Both.
And configure from settings, action URL.
Access when relay A trigger,send http1, relay B trigger, send http2, see below picture.

Attachment: 11You have to Login for download or view attachment(s). No Account? Register

0 Reply

lix91 5 day(s) ago

Edited by lix91 at 2025-10-14 22:03

On the cloud, my configuration is identical to what you show in the image:
Relay 1 = DTMF code 1, Relay 2 = DTMF code 2.
It has never changed since the first installation, but it has stopped working.

I conducted further tests, and I believe what I noticed may be useful:

1- In the SmartPlus app on iPhone, nothing happens when I try to open, neither in monitor mode nor in call mode.

2- In the SmartPlus app on Android version 7.20.0007, it’s the same as on iPhone: it does not work in any way.

3- In the SmartPlus app on Android version 7.13.0005 (older version), there is a different behavior: in call mode, it works; when I tap one of the openings, you can hear the DTMF sound (I mean the phone tone), and the selected web relay works as it should. In monitor mode, however, nothing happens—the same as with the updated Android app and on iPhone.
I believe the older Android app (v.7.13.0005) uses DTMF to open during the call, which the newer v.7.20.0007 does not, while monitor mode seems to have been compromised on the cloud side, since it does not work even in the older Android version.

I don’t know what happened, but I hope this message can be analyzed by the app and cloud developers. Something has definitely changed, and it no longer works as it used to.

Regarding the Action URL solution, inserting the links there works. I had also performed this test, but I find it inelegant: in this way, the physical relays on the R25A trigger unnecessarily, and there is an extra step that could be avoided.

I hope a solution to this problem can be found.
Thank you for the support you are providing.

0 Reply

Akuvox_Mia 4 day(s) ago

lix91 replied at 2025-10-14 22:01
On the cloud, my configuration is identical to what you show in the image:
Relay 1 = DTMF code 1, R ...

You are right, we have change the open door mode to http API instead of DTMF, and the web relay Key settings is used to recognized the DTMF code and do action, that is why it not work any more.
The reason why we change to http API to open door from app is because of 2 advantages:
Advantages of change to http API open door are:
1. From HTTP API, the app will get the resoponse from device whether open door success, while if use DTMF, only send the command out, the app can not know whether open door success.
2. If use DTMF, sometimes the DTMF code from local device changed, maybe lead open door failed.

Due to the advantages we change the open door method which lead your issue. But since using web relay is not that regular, maybe you can just use the solution2 mentioned before for the project?

0 Reply

lix91 3 day(s) ago

Akuvox_Mia replied at 2025-10-15 17:16
You are right, we have change the open door mode to http API instead of DTMF, and the web relay Key ...

Okay, I get it, it's clear now.
I hope this issue is reported to developers so they can fix it in future updates. Web relays are rarely used, but they're essential in some situations where security isn't top-notch, so I hope this issue is resolved.

For now, I'm using the Action URL system, waiting for the new versions.

Thank you so much for your support.

0 Reply