Is there any API to change device name?

[ParticleG]

Since Bambu Farm Manager Server can change device name with it's electron client

[Doridian]

Try this one: https://github.com/Doridian/OpenBambuAPI/blob/main/cloud-http.md#patch-v1iot-serviceapiuserdeviceinfo

Like:

{
  "dev_id": "133742069",
  "name": "Foxes are best aminal"
}

[ParticleG]

Try this one: https://github.com/Doridian/OpenBambuAPI/blob/main/cloud-http.md#patch-v1iot-serviceapiuserdeviceinfo

Like:

{
  "dev_id": "133742069",
  "name": "Foxes are best aminal"
}

Where should I send http request to? There's an HTTP server on the printer?

[Doridian]

Where should I send http request to? There's an HTTP server on the printer?

The bambu cloud api as described at the top of the file I linked.

Or do you mean changing it via local control?

[ParticleG]

Where should I send http request to? There's an HTTP server on the printer?

The bambu cloud api as described at the top of the file I linked.

Or do you mean changing it via local control?

Yes, I mean change it via local

[ParticleG]

Is that possible? Because I used Wireshark to capture the MQTT message sent from my Farm Manager Server to the printer, and it's TLS-encrypted, I don't know how to decrypt it.

[synman]

necromancy here .. I would love to find a local mqtt message command to trigger this but as best as I can tell it is only available via a cloud connection --- at least the setting part.

you can sniff the ssdp broadcast the printers make to see the result:

NOTIFY * HTTP/1.1
Host: 239.255.255.250:1990
Server: UPnP/1.0
Location: xxx
NT: urn:bambulab-com:device:3dprinter:1
NTS: ssdp:alive
USN: xxx
Cache-Control: max-age=1800
DevModel.bambu.com: O1D
DevName.bambu.com: 3DP-094-913
DevConnect.bambu.com: lan
DevBind.bambu.com: free
Devseclink.bambu.com: secure
DevInf.bambu.com: wlan0
DevVersion.bambu.com: 01.02.00.00
DevCap.bambu.com: 1
---------
NOTIFY * HTTP/1.1
HOST: 239.255.255.250:1900
Server: UPnP/1.0
Location: yyy
NT: urn:bambulab-com:device:3dprinter:1
USN: yyy
Cache-Control: max-age=1800
DevModel.bambu.com: N2S
DevName.bambu.com: Shell's A1
DevSignal.bambu.com: -63
DevConnect.bambu.com: lan
DevBind.bambu.com: free
Devseclink.bambu.com: secure
DevVersion.bambu.com: 01.07.00.00
DevCap.bambu.com: 1

the first entry is my H2D that has never been cloud enabled. the second is my A1 which was originally cloud enabled and I changed its name at some point via Bambu Handy before disconnecting it from the cloud.

there is clearly some mechanism that allows us to change DevName.bambu.com but absent a means to decrypt the cloud TLS envelope we may never know the actual command. Even so, it may only be available when the printer is in "cloud" mode which would totally suck IMHO.

Here's the source the client above that captured ssdp broadcast the machines make:

import os
import socket
import sys
import time
import threading


def main():
    try:
        sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
        sock.bind(('', 2021))
        while True:
            data, addr = sock.recvfrom(1024)
            print(data.decode("utf-8"))
    except Exception as e:
        print(e)
        sock.close()


if __name__ == '__main__':
    main()

[synman]

I hate to suggest this but there is a way to "hack" it. It just dawned on me given some MITM stuff I did a while back faking out Bambu Studio to connect to my mosquito server instead of a real printer:

This example reroutes Bambu Studio to the machine running the script. You could just as easily preserve the actual printer ip address and override DevName.bambu.com instead:

import socket
import time

def main():
    fk = ['NOTIFY * HTTP/1.1',
            'HOST: 239.255.255.250:1900',
            'Server: Buildroot/2018.02-rc3 UPnP/1.0 ssdpd/1.8',
            f'Location: {socket.gethostbyname(socket.gethostname())}',
            'NT: urn:bambulab-com:device:3dprinter:1',
            'USN: xxx',
            'Cache-Control: max-age=1800',
            'DevModel.bambu.com: N2S',
            'DevName.bambu.com: 3DP-039-655',
            'DevSignal.bambu.com: -39',
            'DevConnect.bambu.com: lan',
            'DevBind.bambu.com: free', '', '']
    fk = "\r\n".join(fk)

    print()
    print(fk)
    print("creating and binding socket")
    fake = socket.socket(socket.AF_INET, socket.SOCK_DGRAM, socket.IPPROTO_UDP)
    fake.setsockopt(socket.SOL_SOCKET, socket.SO_BROADCAST, 1)
    fake.bind(('', 1900))

    print("entering main loop. . .")
    while True:
        fake.sendto(bytes(fk, "utf-8"), ('255.255.255.255', 2021))
        fake.sendto(bytes(fk, "utf-8"), ('239.255.255.250', 1990))
        time.sleep(5)

if __name__ == '__main__':
    main()

you'd also need to do something at a router level to suppress the printer's broadcast... a udp deny rule would likely do it scoped to just the actual printer(s).

Like I said, a really ugly hack but it'd do it.

[synman]

@Doridian as an FYI (perhaps old news)

I came back to this today out of sheer annoyance.

Put a machine in cloud mode

sent the rename request

was able to siphon the mqtt ack off the local mqtt response topic

 {'update': {'name': "Shell's H2D", 'reason': 'success', 'result': 'success', 'sequence_id': '0'}}

I then cleaned it up and played it back on a lan only machine:

 {'update': {'name': "Shells A1 Boo", 'sequence_id': '0'}}

worked like a charm

this suggests to me at least some of the cloud json payloads work via local mqtt.