MIRACLE 
Uninstalled Windows Media Player, Uninstalled BL STudio, restarted, installed Windows Media Player, restarted, installed BL Studio, restarted
It works.
Lex.
1 Like
I got something new in Bambu Handy. It prompted me for an IP address for the printer! Just one problem - there was no ‘.’ key, so I couldn’t put a valid thing in. So I guess it’s a half step closer.
Go into notepad on your iphone, enter your IP address, copy it, then paste it (it does allow to paste but its tricky to get the prompt)
Tried the reinstalling Windows Media Player bit, no luck. And seriously, Media Player??? Yuck! Turned off all the firewalls (HORRIBLE ADVICE!!) still no luck.
This has been open 28 days, and 20 days since any response from Bambu. This is not acceptable.
EDIT: I was able to get my desktop to connect to the camera. I had to move the P1P out of my IOT network, and into my semi-trusted network range.I then had to add a wi-fi adapter to the machine, and add that adapter to the semi-trusted network. I am not happy about this at all.
1 Like
@Hackmonkey, I agree. I also use a separate network for my IOT and for my PC, both WITHIN my home-network. I had to change the network of the X1CC to my data-network in order to use the streaming.
Not OK.
So perhaps someone from BL can comment on this?
Nevertheless: great machine so far!
Lex
In my case the problem was an old printer firmware.
After disconnecting the AMS the p1p came up with the update immediately.
No it works everything.
1 Like
This was it for me. I got the camera working in Bambu Handy. I feel all the dumb for not thinking about copy/paste. Also thanks to alexanderdubz’s post for the access code hint. Eight zeroes worked for me too.
2 Likes
Is updated my graphics card driver and it finally works on my Windows laptop! It was working fine on the iPhone.
I did not see any reference to graphics cards so I wanted to share.
Happy printing.
Windows Bambu Studio 1.4.0.18
P1P v 01.01.01.0
Sill getting missing LAN IP on PC. It works fine on ios Handy. I put a packet analyzer on the PC and can see that it is indeed receiving SSDP Notify broadcasts from the printer. However, Bambu Studio appears oblivious of it despite the firewall being turned off. In looking through the log files, I cannot see any evidence that Studio has received any SSDP packets. Indeed, after trying to show video, I see this error in the log file:
2023-01-18 16:54:49.769511[Thread 0x00000e44]:monitor: show_status = 2
2023-01-18 16:54:52.672214[Thread 0x00000e44]:MediaPlayCtrl::SetStatus: Initializing...
2023-01-18 16:54:52.734709[Thread 0x00000e44]:MediaPlayCtrl::SetStatus: Stopped.
2023-01-18 16:54:52.734709[Thread 0x00000e44]:MediaPlayCtrl::SetStatus: Initialize failed (Missing LAN ip of printer)!
2023-01-18 16:54:52.750077[Thread 0x00000e44]:MediaPlayCtrl::onStateChanged: 0, last_state: 3
I’ve also verified that SSDP Discovery service is running on the PC, so I don’t understand why Bambu Studio is not seeing the SSDP packets when the onboard analyzer sees it. That SSDP Notify broadcast contains the IP address of the printer, and if Studio can’t see it, it can’t know the IP address of the printer. BBL should just provide an alternative way to enter the local IP address of the printer instead of relying on SSDP.
Ok, I was looking at wrong log file. The network log file is attached below. Most of the logs are mqtt related, but they DO open a SSDP discovery processes on card number 0, presumably the only network interface on this machine. But there was a ssdp: stop() message before this, which is puzzling. But even after this start_ssdp process, there is another ssdp: stop() message further down below. That was the last ssdp message in the network log, so I believe the ssdp discovery process is not running after this, hence not discovering the IP address of the printer. There is no indication of why the ssdp: stop() occurred, so I don’t know what else to try. Come on Bambu Labs, give us a bone so we can figure this out!
** Edit: It looks like that last ssdp: stop() was when I closed the program in order to be able to see the network log. So they stopped the ssdp process as part of closing down the program. So that begs the question, if it was running, why does it not receive the Notify broadcast?
[2023-01-18 17:49:09.331878 -05:00] [I] [T 6388]: init log
[2023-01-18 17:49:09.332818 -05:00] [I] [T 6388]: init_log
[2023-01-18 17:49:09.332855 -05:00] [I] [T 6388]: Agent: set_cert_dir_name, dir=C:\Program Files\Bambu Studio\resources/cert, name=slicer_base64.cer
[2023-01-18 17:49:09.332930 -05:00] [I] [T 6388]: set_on_user_login_fn
[2023-01-18 17:49:09.332938 -05:00] [I] [T 6388]: set_on_server_connected_fn
[2023-01-18 17:49:09.332943 -05:00] [I] [T 6388]: set_on_printer_connected_fn
[2023-01-18 17:49:09.332945 -05:00] [I] [T 6388]: set_get_country_code_fn
[2023-01-18 17:49:09.332946 -05:00] [I] [T 6388]: set_on_local_connect_fn
[2023-01-18 17:49:09.332948 -05:00] [I] [T 6388]: set_on_message_fn
[2023-01-18 17:49:09.332949 -05:00] [I] [T 6388]: set_on_local_message_fn
[2023-01-18 17:49:09.332982 -05:00] [I] [T 6388]: set host to https://api.bambulab.com/v1
[2023-01-18 17:49:09.332986 -05:00] [I] [T 6388]: region update iot = https://api.bambulab.com/v1
[2023-01-18 17:49:09.332987 -05:00] [I] [T 6388]: region update api = https://api.bambulab.com/
[2023-01-18 17:49:09.332988 -05:00] [I] [T 6388]: region update mqtt = ssl://us.mqtt.bambulab.com:8883
[2023-01-18 17:49:09.332989 -05:00] [I] [T 6388]: region update tutk = US
[2023-01-18 17:49:09.332990 -05:00] [I] [T 6388]: region update base domain = bambulab.com
[2023-01-18 17:49:09.332991 -05:00] [I] [T 6388]: region update environment =
[2023-01-18 17:49:09.332991 -05:00] [I] [T 6388]: region update wifi_code = US
[2023-01-18 17:49:09.332992 -05:00] [I] [T 6388]: region update design = https://bambulab.com
[2023-01-18 17:49:09.332996 -05:00] [I] [T 6388]: Agent: load_config
[2023-01-18 17:49:09.333579 -05:00] [I] [T 6388]: load_user_info
[2023-01-18 17:49:13.975023 -05:00] [I] [T 6388]: connect_cloud_mqtt
[2023-01-18 17:49:14.700167 -05:00] [E] [T 6388]: bambu_network_send_message , send_message returned error:-1
[2023-01-18 17:49:15.539393 -05:00] [I] [T 8884]: cloud_conn_callback::on_success, Connection(mqtt) OK! cli id= slicer:1665238185:4bf5
[2023-01-18 17:49:15.539418 -05:00] [I] [T 8884]: cloud_conn_callback::on_success, Connection(mqtt) OK! cli id= slicer:1665238185:4bf5
[2023-01-18 17:49:15.539421 -05:00] [I] [T 8884]: cloud_conn_callback::connected!
[2023-01-18 17:49:17.418941 -05:00] [I] [T 6388]: set_on_http_error_fn
[2023-01-18 17:49:17.418956 -05:00] [I] [T 6388]: ssdp: stop()
[2023-01-18 17:49:17.428179 -05:00] [I] [T 6388]: SsdpDiscovery:start_ssdp with card number = 0
[2023-01-18 17:49:17.715782 -05:00] [I] [T 6388]: set monitor machine = 01S00A2BXXXXXXX
[2023-01-18 17:49:17.715824 -05:00] [I] [T 6388]: del_subscribe topic=device/01S00A2BXXXXXXX/report
[2023-01-18 17:49:17.717493 -05:00] [I] [T 6388]: add_subscribe topic=device/01S00A2BXXXXXXX/report
[2023-01-18 17:49:17.717498 -05:00] [I] [T 6388]: Agent: save_config
[2023-01-18 17:49:17.867042 -05:00] [I] [T 8884]: subscribe topic: device/01S00A2BXXXXXXX/report success
[2023-01-18 17:49:17.867090 -05:00] [I] [T 8884]: subscribe return code: 0
[2023-01-18 17:49:17.867091 -05:00] [I] [T 8884]: subscribe reason code: 0
[2023-01-18 17:49:18.358121 -05:00] [I] [T 6388]: publish_json topic=device/01S00A2BXXXXXXX/request, payload={"pushing":{"command":"pushall","sequence_id":"20001"}}
[2023-01-18 17:49:18.358532 -05:00] [I] [T 6388]: publish_json topic=device/01S00A2BXXXXXXX/request, payload={"info":{"command":"get_version","sequence_id":"20002"}}
[2023-01-18 17:49:19.104497 -05:00] [I] [T 6388]: publish_json topic=device/01S00A2BXXXXXXX0/request, payload={"info":{"command":"get_version","sequence_id":"20003"}}
[2023-01-18 17:54:26.536729 -05:00] [I] [T 6388]: ssdp: stop()
[2023-01-18 17:54:26.539326 -05:00] [I] [T 6388]: Agent: save_config
Hi everyone! Just dropping a message here that may be helpful;
P1P communicates on network using port 6000,
If you set up a dynamic hostname for your internet (or otherwise have a hostname), you can use the dynamic hostname to view the P1P’s camera outside of network.
To do this, set up port forwarding in your router for port 6000 from your P1P (might want to give it a DHCP reservation while you are there…), then, in bambu handy when on WAN, try to view video, wait until timeout, and put your hostname in the ip/hostname box, hit connect. Done, it works
@gabe.peters - Hi, Thanks, just tried this, port forwarding is setup on TCP 6000 and I have verified that the port is open.
But where is this “ip/hostname box” - I have no such box, all I have is an error message:
Ahh OK, Got it, that is the new firmware that has JUST been released, now I can see my P1P camera remotely.
The only problem is it only allows an IP address and not a hostname.
Also, on the iphone handy app, the numeric keypad is displayed without a peiod/dot so you cannot enter the IP.
The workaround is to open another app such as mail, type the IP address and then copy and paste into the IP Address box
@@@@@@@@@@@@@@
Bambu Lab Team,
- Please allow a hostname to be entered as well as an IP Address
- Fix problem with IPHONE handy app where you cannot actually enter an IP (or hostname)
Thanks
@@@@@@@@@@@@@@
Ok, Bambu Labs finally fixed this in Studio 1.4.2.13. Camera view finally works from the PC as well. They also added an option to enter the IP address of the printer if ssdp notify didn’t work.
However, when you try to look at Media, it still says ‘Missing Lan ip of printer’. Oh well, you can’t win them all!
1 Like
Mine finally started working after the last firmware and software update.
But like others the media option still fails 'Missing Lan ip of printer’.
After trying so many things eventually got rid of the issue by checking the camera preserve settings on iPhone.
If someone is struggling to connect with the windows app to the P1P camera, the latest public beta version (v1.7.0) of Bambu Studio solves this problem (at least for me)
Link to the GitHub release: Release v1.7.0 Public Beta · bambulab/BambuStudio · GitHub
I have a new P1S, and it has been working fine yesterday. However, this morning I just started getting the error on Bambu studio as follows:
Initialization failed (Missing LAN IP of printer)
I have a P1S. I am using the latest beta of bambu studio (1.7.0.65), because it is the beta that knows about the P1S printer. I am trying to view the camera through the “device” tab of the studio. The Bambu handy on my phone still connects to the camera ok.
Then, after about twenty minutes of reading online and writing in this forum, it suddenly worked again, without my doing anything specific to try and fix it.
I’m hoping Bambu will get some official word out on this specific problem with this specific error message.
I am having the same issue as @Wruin, only my camera has not come back on yet in Bambu Studio. I did begin working this evening in the Bambu Handy app on my Android. Kind of frustrating really, because the P1S id finely tuned, at least mine is. I have had it almost a week and printed both ABS and PETG without any adjustments at all. But when i first printed the PETG, I had to sit in front of the machine watching for signs of spaghetti or bed adhesion issues because at the time neither of the ways to view the camera feed was working.
I also cant connect via the Cloud to my Printer. It always ask for the LAN IP Adress and than throw the Error that either the Access Code or IP is wrong. Is there a Solution for that?