Why can't I use Cudy APP to manage my Cudy router?

Only Cudy routers that have been upgraded to a firmware version that supports Cudy APP management can be managed using the APP.

Therefore, it is very likely that your Cudy router has not been upgraded to a firmware version that supports APP management.

You can download the Cudy APP by scanning the QR code below. 

 

Please download the latest firmware version to upgrade.

Download Center

Model:  Cudy's wireless products will gradually release new firmware to support APP management. The following table lists some product models that already support APP. Other models may have been released. Please go to the download center to check the new firmware.

WR1300  V2 & V3
M3000
M1300
M1200
WR3000
WR1200
WR1500
M1800
X6
WR1300E V2
LT700E
LT15E

 

Note: The firmware version of all the Cudy routers with 2.x.x will support Cudy APP management.

Please click here to feedback if you have any questions or advice when using Cudy APP.

 

Back to blog

27 comments

When I update the WR1500 router from version 1.0.4-20241017-804431 to the latest version, it only flashes and never turns off, only when I unplug it from the electricity.”

Ahmad kha

@ Dear Ahmed,
Our technical support has sent you the solutions via email. Please check.
“When I update the WR1500 router from version 1.0.4-20241017-804431 to the latest version, it only flashes and never turns off, only when I unplug it from the electricity.”

Support

When I update the WR1500 router from version 1.0.4-20241017-804431 to the latest version, it only flashes and never turns off, only when I unplug it from the electricity.

Ahmed

@Dear Golam,
Our technical support has contacted you via email. Please check.

“Cudy wr1300 v3 latest 2.4.4 firmware bugs in cudy app cloud management after bind
System logs:
Sat Jun 28 16:56:03 2025 user.err : [“?:0: attempt to index a nil value”]
Sat Jun 28 16:56:12 2025 user.notice cmsd: check bindtoken
Sat Jun 28 16:56:14 2025 daemon.crit cmsd: recv 15 signal
Sat Jun 28 16:56:14 2025 daemon.notice cmsd: stop cmsd
Sat Jun 28 16:56:14 2025 kern.info kernel: [17706.957707]
Sat Jun 28 16:56:14 2025 kern.info kernel: [17706.957707] do_page_fault(): sending SIGSEGV to cmsd for invalid read access from 00000170
Sat Jun 28 16:56:14 2025 kern.info kernel: [17706.966288] epc = 00000170 in cmsd[400000+5000]
Sat Jun 28 16:56:14 2025 kern.info kernel: [17706.970973] ra = 77530371 in libmosquitto.so.1[7752a000+1f000]
Sat Jun 28 16:56:14 2025 kern.info kernel: [17706.977021]
Sat Jun 28 16:56:15 2025 daemon.notice cmsd: cmsd start
Sat Jun 28 16:56:22 2025 user.notice cmsd: start
Sat Jun 28 16:56:23 2025 daemon.notice cmsd: connect to mqtt server, Connection Refused: unknown reason.
Sat Jun 28 16:56:23 2025 daemon.notice cmsd: stop cmsd
Sat Jun 28 16:56:23 2025 daemon.err cmsd24413: Command failed: Unknown error”

Support

Cudy wr1300 v3 latest 2.4.4 firmware bugs in cudy app cloud management after bind
System logs:
Sat Jun 28 16:56:03 2025 user.err : [“?:0: attempt to index a nil value”]
Sat Jun 28 16:56:12 2025 user.notice cmsd: check bindtoken
Sat Jun 28 16:56:14 2025 daemon.crit cmsd: recv 15 signal
Sat Jun 28 16:56:14 2025 daemon.notice cmsd: stop cmsd
Sat Jun 28 16:56:14 2025 kern.info kernel: [17706.957707]
Sat Jun 28 16:56:14 2025 kern.info kernel: [17706.957707] do_page_fault(): sending SIGSEGV to cmsd for invalid read access from 00000170
Sat Jun 28 16:56:14 2025 kern.info kernel: [17706.966288] epc = 00000170 in cmsd[400000+5000]
Sat Jun 28 16:56:14 2025 kern.info kernel: [17706.970973] ra = 77530371 in libmosquitto.so.1[7752a000+1f000]
Sat Jun 28 16:56:14 2025 kern.info kernel: [17706.977021]
Sat Jun 28 16:56:15 2025 daemon.notice cmsd: cmsd start
Sat Jun 28 16:56:22 2025 user.notice cmsd: start
Sat Jun 28 16:56:23 2025 daemon.notice cmsd: connect to mqtt server, Connection Refused: unknown reason.
Sat Jun 28 16:56:23 2025 daemon.notice cmsd: stop cmsd
Sat Jun 28 16:56:23 2025 daemon.err cmsd24413: Command failed: Unknown error

Golam Mehbub Sifat

Leave a comment