Hi @Marija,
Is there an additional update beyond 7.14.2 to rectify issues? I will await updating any device in the interim. I hope to update to a tested firmware before additional remote devices are migrated.
Kind regards,
nick
FYI: I have running a RUT200 with 7.14.2 and RMS connection…
Hi Marija,
This is an extremely bad fault being introduced to the system with the 7.14 update…
We had one of the staff, who did not know about the problem, update one of our RUT11 routers to verion 7.14.2 as the system prompted him repeatedly… this did the same thing, broke all connection to the RMS exactly the same…
Luckily this is a locally accessible site, so I was able to reboot it, which did not fix the problem, I then downgraded the firmware to 7.13.4, however now the device is producing a slightly different error with RMS…
Device is temporarily blocked. 17 2025-05-24 10:59:29
Failed to verify device. 113 2025-05-24 10:59:23
The device is redirected to the authentication system. 20 2025-05-24 10:59:18
The device was working perfectly on RMS before the upgrade.
At least now I can download logs etc if you require…
Please advise how to proceed to fix this issue… ps. very uphappy about the situation this upgrade has left us in…
Hi @Marija,
I continue to have very frustrating issues with updated firmware affected devices connected the rut241’s.
I have updated two very remote 18hrs + driving to attend. 7.14.3 is not functioning as per previous. I have had to wind back to 7.12 to resume normal functionality.
Can you please confirm why there has been changes with these updates? why have port settings changed - locking out port 554 on RTSP for example?
Devices, if left on 7.14.3 are not connecting to RMS as per normal. I have to wind them back to 7.12 at least to obtain RMS connection.
Very frustrated customer.
Kind regards,
Nick
Hello @DarylW,
Could you please confirm whether the device is still unable to connect to RMS at this point? If it remains in the “temporarily blocked” state, typically re-registering the device resolves this. Have you had a chance to try that yet?
If not, please attempt to remove the device from RMS and re-add it, ensuring that all registration parameters are inserted correctly. Then, during the last registration phase, when the device is waiting for connection, you can either:
- Click Connect via WebUI under Services → Cloud Solutions,
or, if the device is remote: - Send an SMS command to the SIM card’s number in the format:
<password> <rms_connect>
and check its status afterward with:
<password> <rms_status>
If the device still fails to connect after these steps, run the /etc/init.d/rms_mqtt restart command via CLI, and in case nothing changes, I’d recommend performing a factory reset on the unit and repeating the registration process from the beginning.
Also, to note, after downgrading device firmware, the previously made settings, along with RMS certificates, are being deleted, therefore device has to be re-registered.
Best regards,