Anycubic Cloud MQTT access blocked

[WaresWichall]

I have bad news for everyone using this.

At some point recently Anycubic updated their servers to block MQTT access for our "ac_web" tokens and only allows MQTT access via app/slicer tokens now.

This change was specifically targeting this home assistant integration since the basic anycubic web client doesn't need or support MQTT connections.

Having put many hours of work into this integration and witnessed Anycubic continually try to break it with questionable updates, now that I know for sure they're targeting this integration I've had enough and I'm moving on.

I'm tired of the way they treat their customers and all of my tickets/emails about API access have been ignored.

I will publish a final release soon with an option to disable MQTT connections, meaning the integration will only get updates every minute - until Anycubic shut that down too.

Again, sorry for anyone using this but I'm selling my printer and getting something else that doesn't try to harvest all my data.

[adamoutler]

I feel like there is a lot left to explore. Let's talk about the various pathways to getting info.

• MQTT - Off limits. Personally I wouldn't want to manage multiple users in an MQTT server. There are too many problems which could occur.
• SSH - we have the root username/password for some of the units but not all. Once in, we can access the comm binary and system logs as well as the internal system UARTs. There is certainly a key to MQTT there, but again, Anycubic probably doesn't want that. It adds a level of risk to the device as well where a local attacker could perform a denial of service on your printer or fire the lamp until dead. I'd expect this to be patched
• Telnet - same as above.
• WebUI - some units use OpenWRT and we have the user/pass but it grants access to ways to obtain access.
• Port 11311 - what is this? I don't know, but comm opens it. When you connect to this port it disconnected the device from AC Cloud and each message sent can be observed as received in the comm logs. After disconnect, the unit reconnects to AC Cloud within about 20s.

So based on this we can assume port 11311 is an alternative command and control function which allows local access to the device. Additionally it looks to be an undocumented feature, less problematic for AC than a MQTT connection, and supports SOME feature set using Telnet.

I don't have the time to reverse engineer this feature. I don't have any examples of it being used locally for setup/control/monitoring. If anyone knows, please reach out so that I can make something open source that can be used to tell us when our printers are finished.

[Cloud500]

Just back from vacation and now a message like this 😢

I had just set up my dashboard in a more or less satisfactory way and thanks to AppDeamon I was also able to automatically transfer the filament consumption to Spoolman 😭

Maybe there is still hope for the LAN mode...
Unfortunately, I don't have time for this at the moment either, but I'll see if I can run the LAN mode from time to time and see what happens "n the network".

[WaresWichall]

My understanding is that each type of printer handles local connections entirely differently with no unified API, so each model would need its own implementation.

The only thing that is the same on all their printers is that they connect to the cloud. So my suggestion to anyone that wants to focus on this would be to create a hassio docker addon emulating the cloud similar to this project: https://github.com/anjomro/kobra-unleashed

That could then be the "broker" to talk to a modified version of this home assistant integration, as long as there is a way to force each printer model to use a local broker.

I won't be taking part in that though I'm afraid.

[WaresWichall]

I made a pre-release with an option to "never connect" to MQTT to at least keep warnings out of the logs

https://github.com/WaresWichall/hass-anycubic_cloud/releases/tag/v0.2.0rc8

I won't bother making a full release or finalising the notes since all the MQTT functionality is now broken...

[adamoutler]

It seems like the future devices will be using comm binary. I'm going to need to check out that project you suggested. I'd really like some help with this port 11311 thing too. I can see OpenWRT being a passing fad, but it seems like comm is here to stay and comm has the port 11311 connection feature. Maybe if we can figure out what it needs, it may be a viable option for local communication.

[Cloud500]

Maybe there is another possibility, a completely different approach, but 2 things are interesting:

1. Anycubic seems to have released the firmware OpenSource (For the Kobra 3)
   (https://github.com/ANYCUBIC-3D/Kobra3)

2. There is a first (probably quite good) working CFW
   (https://github.com/utkabobr/DuckPro-Kobra3)

(And if nothing works, maybe we can connect an ESP directly to the UART 😆)

[adamoutler]

That's a microcontroller version but I do notice the command STATS seems to be the one I'd be interested in.

[Cloud500]

The more approaches, the better the chances ;-)

[duckida]

Is there a sniffer or something to get tokens out off the app or slicer? They are just web apps it seems.

[duckida]

The app link for the sign in seems to be http://anycubic-1307326732.cos.ap-guangzhou.myqcloud.com/, mqtt-universe.anycubic.com, or uc.makeronline.com

[WaresWichall]

@duckida the slicer usually stores tokens in a file in the config directory but it uses a slightly different login method which would need to be supported in this code.

The next problem is that Anycubic only permits one login per token which means that logging into the slicer would log you out in home assistant and vice versa

[duckida]

Then don’t use the slicer

[WaresWichall]

@duckida I'm not using anycubic anymore... :) just wanted to share the info I know

[duckida]

Not sure but it might be https://cloud-platform.anycubicloud.com/Login?redirect=%2Ffile