Hi everyone,
I have a CR-10 Smart that used to work with Creality Cloud (confirmed by logs showing successful downloads from file-cdn.creality.com in July 2021), but it can no longer connect to the cloud.
The error (from the WiFi module logs via telnet):
[HAL_TCP_Establish] success to establish tcp, fd=8
[iotx_mc_wait_CONNACK] wait connack timeout
[_mqtt_connect] wait connect ACK timeout! rc = -14
[_iotx_linkkit_master_connect] DM Start Failed
The TCP connection to a1cinnxEHw4.iot-as-mqtt.cn-shanghai.aliyuncs.com:1883 succeeds, but the MQTT broker never sends back a CONNACK. I verified the same timeout from a separate machine, which strongly suggests the product key / device credentials are no longer registered on Alibaba Cloud IoT.
Device info (via telnet on WiFi module):
- WiFi module firmware: 2020-12-16 (BusyBox v1.12.1, MT7628)
- Product key in NVRAM:
a1cinnxEHw4(from /etc_ro/cxsw/cxsw_default_config) - Region: cn-shanghai (region=0)
- Device name:
66868912000D42 - Internet works fine (ping 8.8.8.8 OK, TCP to MQTT broker succeeds)
- Previously bound to a Creality account (ownerId in NVRAM)
What I’ve tried:
- Set correct product key
a1cinnxEHw4in NVRAM - Set region to cn-shanghai (region=0)
- Cleared previous owner binding (ownerId)
- Tried hardcoded fallback key
a1RIsMLz2BJ— same timeout
My theory is that Creality migrated their Alibaba Cloud IoT backend and old device registrations were lost.
Questions:
- Have product keys / device registrations for older CR-10 Smart devices been deprecated?
- Is there a re-provisioning procedure to get fresh cloud credentials?
- Is there a firmware update for the CR-10 Smart WiFi module with updated credentials?
Has anyone else seen this? Would love to hear if there’s a fix short of switching to OctoPrint.
Thanks!
So it reaches the server, but the MQTT broker isn’t accepting the device credentials? This usually happens when older devices are no longer registered on a backend system. Saw some posts on Reddit(Not CR-10 specific) where a few people have had luck by fully resetting the printer and re‑binding it through the Creality Cloud app or updating the WiFi module firmware, but if that doesn’t work, the only reliable option left is running it locally via OctoPrint or similar as you’ve mentioned.