Solo Cudy router che sono stati aggiornati a un firmware la versione che supporta la gestione dell'APP Cudy può essere gestita utilizzando l'APP.
Pertanto, è molto probabile che il tuo router Cudy non sia stato aggiornato a una versione del firmware che supporti la gestione delle APP.
Puoi scaricare l'APP Cudy scansionando il codice QR qui sotto.
Scarica la versione più recente del firmware per eseguire l'aggiornamento.
Centro download< /p>
Modello: i prodotti wireless di Cudy rilasceranno gradualmente nuovo firmware per supportare la gestione delle APP. La tabella seguente elenca alcuni modelli di prodotto che già supportano APP. Potrebbero essere stati rilasciati altri modelli. Vai al centro download per verificare il nuovo firmware.
| WR1300 V2 & V3 |
| M3000 |
| M1300 |
| M1200 |
| WR3000 |
| WR1200 |
| WR1500 |
| M1800 |
| X6 |
| WR1300E V2 |
| LT700E |
| LT15E |
39 commenti
@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”
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
@Estimado Yonnel,
¿Cuál es la versión del firmware ahora?
“No puedo administrar mi router cudy AX1500 con la aplicación Cudy y intento actualizar el firmware 2025 y no lo admite dice formato de archivo inválido”
No puedo administrar mi router cudy AX1500 con la aplicación Cudy y intento actualizar el firmware 2025 y no lo admite dice formato de archivo inválido
@Dear Bartek,
Thank you for contacting Cudy support team.
If you want to use like this, please set it to the Access Point mode. Please follow the steps:
1. Disconnect the cable from your ISP router, connect the WAN port of WR3600 to your ISP router.
2. Disconnect and reconnect the phone to the router. Then you will be able to login in to the WEB page or see it in Cudy APP. Please set it to the Wireless Access Point mode. Then the router will disable NAT function. And you can also manage it via the APP or cudy.net.
“i dont see my brand new cudy wr3600 in app, nor in cudy.net, or even in 192.168.10.1,wifi and lan internet works, but i would like to acces config, i have connected it lan1-lan1 to my isp router/modem combo, and lan2 of cudy to my pc. i did it that way to not create double NAT, is it a problem? i would like it to stay in that config and still have access to admin panel”