Ability to enter IP of Printer(s)

[TheCableGuy99]

Is your feature request related to a problem? Please describe.
Yes, I've started to use LAN mode now video is supported. But the printers reside on a separate IoT subnet where scanning is not allowed and therefore printers cannot be auto-discovered.

Describe the solution you'd like
The ability to enter the IP address of the printer and it allows it to be a different subnet. For example, if my PC is on 192.168.1.10 and one of the printers is on 192.168.2.10 then I can enter rhis and it stores it until I decide to edit it. This must support multiple printers.

Describe alternatives you've considered
Putting my PC and printer on the same subnet and allowing scanning is the only way to get LAN mode working that I can see.

Additional context
I think the above is clear enough but please let me know if you need any further clarification.

[Znubbis]

+1, if they want to sell printer to corporations this is required to be possible.

[Alex-Schaefer]

This feature is an absolute necessity, why is this not implemented?

Bambu Studio can't find the printer in LAN only mode, because different network, but using FTP to connect works. So it's not a network problem, it's a Bambu Studio Problem. I suppose being able to input the printer IP it should work in Bambu Studio, too.

Can't use the printer like that in the company.

[Alex-Schaefer]

There is an ugly workaround: Send a fake SSDP discovery packet.

Either use this Linux only script from #702: https://github.com/gashton/bambustudio_tools/blob/master/bambudiscovery.sh
Or my Python implementation (tested on Windows 10): https://gist.github.com/Alex-Schaefer/72a9e2491a42da2ef99fb87601955cc3

Nevertheless, this issue should be addressed by Bambu

[timothyzalusky]

Adding a +1 to try and get some more visibility to this feature. Expectation would be that this should simplify users like me who have a printer at home and Bambu Printers at work and would like to keep them separate.

[Technology89]

There is an ugly workaround: Send a fake SSDP discovery packet.

Either use this Linux only script from #702: https://github.com/gashton/bambustudio_tools/blob/master/bambudiscovery.sh Or my Python implementation (tested on Windows 10): https://gist.github.com/Alex-Schaefer/72a9e2491a42da2ef99fb87601955cc3

Nevertheless, this issue should be addressed by Bambu

Thanks for the Python Script. Is there some specific thing i need to put in for the P1S? Tried "3DPrinter-P1S" but it still shows "Model: Unknown" in Update Page and can't access the camera.

Btw +1 for this feature.

[OndrejLycka]

I, too, miss that option a lot.

[wilk-polarny]

Yes, such an option is essential. Especially IF printers are on different subnets, the regular UDP announcement will not work. I have a separate WiFi and network for all IoT stuff and would like to keep things isolated.

The workarounds posted above do work, but I'll have to send fake broadcasts each time I open up bambu studio...

Please, add an option to add printer IP addresses and REMEMBER them in Bambu Studio!

[hoegge]

It is quite crazy you cannot add a printer by IP - it means a lot of user simply cannot connect to it and means you can return the printer and get a refund, since it does not work.

[myklemu]

+1 for attention on this important issue. Bambu has previously gotten a lot of heat for their lacking IT security, so they should be very interested in implementing this.

[ColColonCleaner]

We really need the ability to add printers by IP. I cannot use an X1C on my network because of this problem.

The scripted workarounds are not working for me either. Not sure if that was blocked in a recent BambuStudio update, which would be very bad.

[theonlytruth]

We bought one X1E for using it in an enterprise network with multiple VLAN. Bambu promotes this device for usage in complex enterprise networks. But in reality one get stopped by such a little thing like not be able to add a printer by IP. This is bad. If this would work the X1E may be a good printer to replace our other old Ultimaker.

[timothyzalusky]

@walterwongbbl I would expect 10k users actually want this implemented (or more). This needs to be a priority. Can you give us a rough timeline for implementation?

[SaltWei]

This will be supported in next studio version

[ColColonCleaner]

This will be supported in next studio version

Excellent news. Looking forward to the update. Cheers.
I'm sure all the people asking for this back in #702 will also be happy.

[timothyzalusky]

This will close out almost 10 different issue items, excited to see it.

[timothyzalusky]

@SaltWei Just saw a new release of studio just dropped, but it looks like this feature was left out. Any timeline for the implementation of this feature?

[alebre-lithoz]

I know its a bit early since the new new release is only 40 minutes old but these feature wasn't implemented as far as I see.

[wilk-polarny]

I know its a bit early since the new new release is only 40 minutes old but these feature wasn't implemented as far as I see.

They said next studio version, but not which one (a or the) ;)

[SaltWei]

That is a queue jumping release for some bug fix. The version for this issue is next big release 1.10 which may come 1.5 month later.

…

From: ***@***.***> Date: 2024年8月26日 (周一) 21:46 Subject: Re: [bambulab/BambuStudio] Ability to enter IP of Printer(s) (Issue #2232) To: ***@***.***> Cc: ***@***.***>, ***@***.***> > I know its a bit early since the new new release is only 40 minutes old but these feature wasn't implemented as far as I see. They said next studio version , but not which one ;) — Reply to this email directly, view it on GitHub<#2232 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A2MIWNY2FDF2JBNMTAYP6N3ZTMWSPAVCNFSM6AAAAAA3JJDYYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJQGI2TQMBRGE>. You are receiving this because you were mentioned.[image]Message ID: ***@***.***>

[ColColonCleaner]

@SaltWei thank you for confirming this fix is coming and the specific version it's coming in.
Understandable it would be a larger release since both studio and the network plugin require updates for this.

[meisnick]

This is still absolutely unacceptable for the X1E a "Enterprise" sale product for institutions to have to work around this issue. This has been open for Over a year please provide a timeline for this. Even in the beta 1.10 release entering a IP and Access code for both a X1E and X1C results in "The device does not support using ip and Access Code for connection"

[bradich]

Looks like this is coming in the next release. It's in the public beta of Studio now. https://github.com/bambulab/BambuStudio/releases/tag/v01.10.00.74

[giggls]

Looks like this is coming in the next release. It's in the public beta of Studio now. https://github.com/bambulab/BambuStudio/releases/tag/v01.10.00.74

Which does not work. See previous comment of @meisnick

[ColColonCleaner]

"The device does not support using ip and Access Code for connection"

Wait... How is it possible that the printer "does not support" connection by IP and Access Code? That's how it already works if you spoof the SSDP data, so the only change is making studio be able to manually enter the IP and serial number.

Unless there is currently no way to get the serial number from the printer without the SSDP data? I know when integrating with HA it requires the serial number to be known ahead of time. Did they need a firmware update just to get the serial number? For anyone wanting to enter an IP manually, they would also have the serial number on hand, I'm fine with entering that myself too.

[giggls]

Whatever they did the functionality seems to be there in public beta but does not work.

[mikeafish]

When I tried to use it in the beta, Bambu Studio crashed.Best,MichaelOn Oct 21, 2024, at 9:35 AM, Sven Geggus ***@***.***> wrote: Whatever they did the functionality seems to be there in public beta but does not work. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mwdle]

This functionality is also not working for me on the beta. My issue is described on this thread