[GH-ISSUE #661 ] [Bug Report] I have an A1 and a P2S. When I click the camera icon on the A1, it works the sa #435

Author

Owner

@maziggy commented on GitHub (Mar 10, 2026):

The log was captured before you tried streaming, so it doesn't contain the camera-specific diagnostics we need.

Could you try this:

https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging
Open the P2S camera stream (click the camera icon)
Wait for it to fail/timeout
Upload support package to this issue

We need to see the ffmpeg output — it will show exactly why the RTSP connection to your P2S is failing.

Also — you're on v0.2.2b1. The latest is 0.2.2b2 which includes several fixes. Could you update and try again? If the issue persists on 0.2.2b2, the new log will help us pinpoint the cause.

@maziggy commented on GitHub (Mar 10, 2026): The log was captured before you tried streaming, so it doesn't contain the camera-specific diagnostics we need. Could you try this: 1. https://wiki.bambuddy.cool/features/system-info/?h=debug#enable-debug-logging 2. Open the P2S camera stream (click the camera icon) 3. Wait for it to fail/timeout 3. Upload support package to this issue We need to see the ffmpeg output — it will show exactly why the RTSP connection to your P2S is failing. Also — you're on v0.2.2b1. The latest is 0.2.2b2 which includes several fixes. Could you update and try again? If the issue persists on 0.2.2b2, the new log will help us pinpoint the cause.

BreizhHardware commented

bambuddy-support-20260310-090529.zip

Author

Owner

@ddetton commented on GitHub (Mar 10, 2026):

Ok, updated to 0.2.2b2. Enabled debug. Reproduced error. Attaching file.

@ddetton commented on GitHub (Mar 10, 2026): Ok, updated to 0.2.2b2. Enabled debug. Reproduced error. Attaching file. [bambuddy-support-20260310-090529.zip](https://github.com/user-attachments/files/25876104/bambuddy-support-20260310-090529.zip)

BreizhHardware commented

Author

Owner

@maziggy commented on GitHub (Mar 11, 2026):

I can see 5 RTSP stream attempts to your P2S, all failing within seconds — ffmpeg starts but produces zero frames before exiting. Unfortunately, the current build doesn't capture ffmpeg's error output in this scenario, so we can't see why it's failing.

I've just added diagnostic logging that will capture the actual ffmpeg error message.

Please pull branch 0.2.2b3, rebuild your container and generate a new support package when trying to connect to the camera.

git checkout 0.2.2b3 && git pull && docker compose down && docker compose up --build -d

The ffmpeg error will tell us exactly what's going wrong — likely a TLS negotiation issue or RTSP auth rejection.

A couple of things that look fine in your logs, just to confirm:

Developer mode is enabled on the P2S ✓
MQTT is connected and printer is reachable ✓
Camera is on (ipcam_dev: '1') and RTSP URL is present ✓
Network mode is host ✓

So the printer-side config looks correct. We just need the ffmpeg error to pinpoint the failure.

@maziggy commented on GitHub (Mar 11, 2026): I can see 5 RTSP stream attempts to your P2S, all failing within seconds — ffmpeg starts but produces zero frames before exiting. Unfortunately, the current build doesn't capture ffmpeg's error output in this scenario, so we can't see why it's failing. I've just added diagnostic logging that will capture the actual ffmpeg error message. Please pull branch 0.2.2b3, rebuild your container and generate a new support package when trying to connect to the camera. git checkout 0.2.2b3 && git pull && docker compose down && docker compose up --build -d The ffmpeg error will tell us exactly what's going wrong — likely a TLS negotiation issue or RTSP auth rejection. A couple of things that look fine in your logs, just to confirm: - Developer mode is enabled on the P2S ✓ - MQTT is connected and printer is reachable ✓ - Camera is on (ipcam_dev: '1') and RTSP URL is present ✓ - Network mode is host ✓ So the printer-side config looks correct. We just need the ffmpeg error to pinpoint the failure.

BreizhHardware commented

bambuddy-support-20260311-133957.zip

Author

Owner

@ddetton commented on GitHub (Mar 11, 2026):

Ok, with the help of Google Gemini, I was able to configure my synology for git and build the container you requested. Here is the new support package. Thanks!

@ddetton commented on GitHub (Mar 11, 2026): Ok, with the help of Google Gemini, I was able to configure my synology for git and build the container you requested. Here is the new support package. Thanks! [bambuddy-support-20260311-133957.zip](https://github.com/user-attachments/files/25918955/bambuddy-support-20260311-133957.zip)

BreizhHardware commented

bambuddy-support-20260311-220324.zip

Author

Owner

@DMoenning commented on GitHub (Mar 11, 2026):

Ok, with the help of Google Gemini, I was able to configure my synology for git and build the container you requested. Here is the new support package. Thanks!

bambuddy-support-20260311-133957.zip

i firstly run in the same issue with git. you could just enable beta updates and then use docker compose pull && docker compose up -d

@maziggy ive got the same issue as @ddetton and heres my debug-log aswell

im on 0.2.2b3

@DMoenning commented on GitHub (Mar 11, 2026): > Ok, with the help of Google Gemini, I was able to configure my synology for git and build the container you requested. Here is the new support package. Thanks! > > [bambuddy-support-20260311-133957.zip](https://github.com/user-attachments/files/25918955/bambuddy-support-20260311-133957.zip) i firstly run in the same issue with git. you could just enable beta updates and then use `docker compose pull && docker compose up -d` @maziggy ive got the same issue as @ddetton and heres my debug-log aswell [bambuddy-support-20260311-220324.zip](https://github.com/user-attachments/files/25919298/bambuddy-support-20260311-220324.zip) im on 0.2.2b3

BreizhHardware commented

Author

Owner

@maziggy commented on GitHub (Mar 12, 2026):

The logs show the P2S firmware is actively dropping the RTSP session after a few seconds — ffmpeg connects, receives video, then gets Error during demuxing: Input/output error. This happens consistently on both your printers.

I've added transparent auto-reconnection in the next build: when ffmpeg's RTSP session dies, it respawns immediately and continues streaming MJPEG frames to the browser without interruption. You'll see a brief frame freeze (~1s) each time the P2S drops the connection, but the stream stays alive instead of failing.

Will be available in next daily release or by using branch dev.

please let me know if it works now.

@maziggy commented on GitHub (Mar 12, 2026): The logs show the P2S firmware is actively dropping the RTSP session after a few seconds — ffmpeg connects, receives video, then gets Error during demuxing: Input/output error. This happens consistently on both your printers. I've added transparent auto-reconnection in the next build: when ffmpeg's RTSP session dies, it respawns immediately and continues streaming MJPEG frames to the browser without interruption. You'll see a brief frame freeze (~1s) each time the P2S drops the connection, but the stream stays alive instead of failing. Will be available in next daily release or by using branch dev. please let me know if it works now.

BreizhHardware commented

bambuddy-support-20260312-135349.zip

Author

Owner

@ddetton commented on GitHub (Mar 12, 2026):

Thanks! I did a checkout and build on the dev branch. What it is doing now is flash a still image every 3-4 seconds. Before I set LAN only and Dev mode, Bambu Handy would stream live video. Not having live video is a dealbreaker for me. I don't think it is your problem. It appears that the p2s has a really finicky video stream service. Could this have anything to do with it being a 1080p video feed? One thing I tried was turning off LAN Liveview and it totally broke it. Turning it back on restored the still image cycle. Can other people running bambuddy view live video streams from the P2S? Is there any other setting that could affect this? Here is my current log.

@ddetton commented on GitHub (Mar 12, 2026): Thanks! I did a checkout and build on the dev branch. What it is doing now is flash a still image every 3-4 seconds. Before I set LAN only and Dev mode, Bambu Handy would stream live video. Not having live video is a dealbreaker for me. I don't think it is your problem. It appears that the p2s has a really finicky video stream service. Could this have anything to do with it being a 1080p video feed? One thing I tried was turning off LAN Liveview and it totally broke it. Turning it back on restored the still image cycle. Can other people running bambuddy view live video streams from the P2S? Is there any other setting that could affect this? Here is my current log. [bambuddy-support-20260312-135349.zip](https://github.com/user-attachments/files/25950702/bambuddy-support-20260312-135349.zip)

BreizhHardware commented

Author

Owner

@ddetton commented on GitHub (Mar 12, 2026):

I installed an instance of octoeverywhere to see if I could get the video stream to show up there. That one gets an error too. Here is the message posted to the docker log for that container:

2026-03-12 23:10:17,049 - WARNING -
Exception in QuickCam capture thread. [SSL:
SSLV3_ALERT_HANDSHAKE_FAILURE] ssl/tls alert handshake failure
(_ssl.c:1010)

I asked Google Gemini about this and here is what it said:
That error message is the "smoking gun." SSLV3_ALERT_HANDSHAKE_FAILURE confirms that the P2S is using an older or specific security protocol that modern, "secure" Linux environments (like your Synology's Docker containers) are now programmed to reject by default.

Is there any way that you could use a less secure TLS handshake to make this work?

@ddetton commented on GitHub (Mar 12, 2026): I installed an instance of octoeverywhere to see if I could get the video stream to show up there. That one gets an error too. Here is the message posted to the docker log for that container: 2026-03-12 23:10:17,049 - WARNING - Exception in QuickCam capture thread. [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] ssl/tls alert handshake failure (_ssl.c:1010) I asked Google Gemini about this and here is what it said: That error message is the "smoking gun." SSLV3_ALERT_HANDSHAKE_FAILURE confirms that the P2S is using an older or specific security protocol that modern, "secure" Linux environments (like your Synology's Docker containers) are now programmed to reject by default. Is there any way that you could use a less secure TLS handshake to make this work?

BreizhHardware commented

https://github.com/greghesp/ha-bambulab/issues/1602#issuecomment-3448502886

Author

Owner

@ddetton commented on GitHub (Mar 13, 2026):

This is interesting.

Google Gemini thinks that I can load a docker instance of webrtc to handle the video stream. I will be trying this out.

@ddetton commented on GitHub (Mar 13, 2026): This is interesting. https://github.com/greghesp/ha-bambulab/issues/1602#issuecomment-3448502886 Google Gemini thinks that I can load a docker instance of webrtc to handle the video stream. I will be trying this out.

BreizhHardware commented

Author

Owner

@DMoenning commented on GitHub (Mar 13, 2026):

Im using homeassistant with the Addon go2rtc.

I've configured my P2S there and I have a fluent 1080 stream. When I link it in bambuddy settings as external cam for P2S, I get the same problem like when I'm using the default cam for P2S.

So it must be something in bambuddy.

So @ddetton your rtc Container won't fix it

@DMoenning commented on GitHub (Mar 13, 2026): Im using homeassistant with the Addon go2rtc. I've configured my P2S there and I have a fluent 1080 stream. When I link it in bambuddy settings as external cam for P2S, I get the same problem like when I'm using the default cam for P2S. So it must be something in bambuddy. So @ddetton your rtc Container won't fix it

BreizhHardware commented

Author

Owner

@ddetton commented on GitHub (Mar 13, 2026):

I finally got go2rtc to display the video stream from the P2S. I'm running a go2rtc docker container . It finally started working when I changed my stream url to use rstps:

rtsps://bblp:[access_id]@192.168.101.41:322/streaming/live/1

With go2rtc, I can type this url into a browser window and the stream appears:

http://192.168.101.21:1984/stream.html?src=p2s_camera

The URL is the box go2rtc is on. None of this works in bambuddy but hopefully this will help @maziggy figure this out.

@ddetton commented on GitHub (Mar 13, 2026): I finally got go2rtc to display the video stream from the P2S. I'm running a go2rtc docker container . It finally started working when I changed my stream url to use rstps: ``` rtsps://bblp:[access_id]@192.168.101.41:322/streaming/live/1 ``` With go2rtc, I can type this url into a browser window and the stream appears: ``` http://192.168.101.21:1984/stream.html?src=p2s_camera ``` The URL is the box go2rtc is on. None of this works in bambuddy but hopefully this will help @maziggy figure this out.

BreizhHardware commented

Author

Owner

@ddetton commented on GitHub (Mar 13, 2026):

Im using homeassistant with the Addon go2rtc.

I've configured my P2S there and I have a fluent 1080 stream. When I link it in bambuddy settings as external cam for P2S, I get the same problem like when I'm using the default cam for P2S.

So it must be something in bambuddy.

So @ddetton your rtc Container won't fix it

@dmoenning I tried to follow the directions to get the camera working in HA but it was very confusing. The help gives you three options to load the go2rtc server side with the third option being deploy your own docker container, which is what I did. It appears that I just need to do the UI side of things now but I'm too tired to figure it out now. Thanks!

@ddetton commented on GitHub (Mar 13, 2026): > Im using homeassistant with the Addon go2rtc. > > I've configured my P2S there and I have a fluent 1080 stream. When I link it in bambuddy settings as external cam for P2S, I get the same problem like when I'm using the default cam for P2S. > > So it must be something in bambuddy. > > So [@ddetton](https://github.com/ddetton) your rtc Container won't fix it @dmoenning I tried to follow the directions to get the camera working in HA but it was very confusing. The help gives you three options to load the go2rtc server side with the third option being deploy your own docker container, which is what I did. It appears that I just need to do the UI side of things now but I'm too tired to figure it out now. Thanks!

BreizhHardware commented

Author

Owner

@maziggy commented on GitHub (Mar 13, 2026):

Two changes in the latest build targeting this:

TLS compatibility fix
ffmpeg in the Docker image uses GnuTLS (not OpenSSL) for TLS. Debian's hardened GnuTLS defaults may be rejecting the P2S firmware's TLS renegotiation after the initial handshake succeeds — which would explain why ffmpeg connects and gets frames but the session drops after ~3 seconds. Added a GnuTLS config that allows unsafe renegotiation and legacy cipher compatibility.
Faster RTSP reconnect
Even if the P2S still drops sessions, the reconnect cycle is now much faster:

ffmpeg fast-start flags (-probesize 32 -analyzeduration 0 -fflags nobuffer -flags low_delay) to produce frames sooner
Reconnect delay reduced from 1.0s to 0.2s
Startup check reduced from 0.5s to 0.1s
Per-cycle overhead drops from ~3-4s to under 1s

Also fixed external camera streams (e.g. go2rtc) being choppy due to double rate-limiting in the proxy layer, so that path works smoothly as a fallback too.

@ddetton @DMoenning — please test with branch test/issue_661 and let me know if the stream is smoother. If it still drops, enable debug logging and share a support package — the new build includes GnuTLS debug output that will show us the exact TLS failure reason.

@maziggy commented on GitHub (Mar 13, 2026): Two changes in the latest build targeting this: 1. TLS compatibility fix ffmpeg in the Docker image uses GnuTLS (not OpenSSL) for TLS. Debian's hardened GnuTLS defaults may be rejecting the P2S firmware's TLS renegotiation after the initial handshake succeeds — which would explain why ffmpeg connects and gets frames but the session drops after ~3 seconds. Added a GnuTLS config that allows unsafe renegotiation and legacy cipher compatibility. 2. Faster RTSP reconnect Even if the P2S still drops sessions, the reconnect cycle is now much faster: - ffmpeg fast-start flags (-probesize 32 -analyzeduration 0 -fflags nobuffer -flags low_delay) to produce frames sooner - Reconnect delay reduced from 1.0s to 0.2s - Startup check reduced from 0.5s to 0.1s - Per-cycle overhead drops from ~3-4s to under 1s Also fixed external camera streams (e.g. go2rtc) being choppy due to double rate-limiting in the proxy layer, so that path works smoothly as a fallback too. @ddetton @DMoenning — please test with branch test/issue_661 and let me know if the stream is smoother. If it still drops, enable debug logging and share a support package — the new build includes GnuTLS debug output that will show us the exact TLS failure reason.

BreizhHardware commented

https://erugo.detton.me/shares/cool-shadow-black-meadow

Author

Owner

@ddetton commented on GitHub (Mar 13, 2026):

We are making progress! With internal camera selected, it connects successfully and displays a still image then does pause and refresh but still shows the same image. With external camera selected, RSTP stream and url pointing to my go2rtc instance, it fails to connect. I noticed the url for the external camera shows up as [bambuddy_url]/camera/1. When external camera is selected with New Window, can you just open the window with the specified url? When I enter my go2rtc url manually in a browser window, I get full motion video. Just so you can see the difference, I created a video of bambuddy pointing at internal camera and another video of the go2rtc instance manually entered in a browser. This download link expires on 3/20/26. Thanks!

@ddetton commented on GitHub (Mar 13, 2026): We are making progress! With internal camera selected, it connects successfully and displays a still image then does pause and refresh but still shows the same image. With external camera selected, RSTP stream and url pointing to my go2rtc instance, it fails to connect. I noticed the url for the external camera shows up as [bambuddy_url]/camera/1. When external camera is selected with New Window, can you just open the window with the specified url? When I enter my go2rtc url manually in a browser window, I get full motion video. Just so you can see the difference, I created a video of bambuddy pointing at internal camera and another video of the go2rtc instance manually entered in a browser. This download link expires on 3/20/26. Thanks! https://erugo.detton.me/shares/cool-shadow-black-meadow

BreizhHardware commented

Author

Owner

@rice1204 commented on GitHub (Mar 14, 2026):

Just discovered bambuddy. Amazing software!

Just wanted to report that I'm able to get very smooth (15-20fps) 1080p video on v0.2.2b4-daily.20260313. No discernable drops after watching the stream for about 10 minutes. My bambuddy instance is a fresh docker install. The printer is set to cloud connection with LAN video on.

@rice1204 commented on GitHub (Mar 14, 2026): Just discovered bambuddy. Amazing software! Just wanted to report that I'm able to get very smooth (15-20fps) 1080p video on v0.2.2b4-daily.20260313. No discernable drops after watching the stream for about 10 minutes. My bambuddy instance is a fresh docker install. The printer is set to cloud connection with LAN video on.

BreizhHardware commented

Author

Owner

@maziggy commented on GitHub (Mar 14, 2026):

please try again with branch test/issue_661.

@maziggy commented on GitHub (Mar 14, 2026): please try again with branch test/issue_661.

BreizhHardware commented

Author

Owner

@ddetton commented on GitHub (Mar 14, 2026):

Just discovered bambuddy. Amazing software!

Just wanted to report that I'm able to get very smooth (15-20fps) 1080p video on v0.2.2b4-daily.20260313. No discernable drops after watching the stream for about 10 minutes. My bambuddy instance is a fresh docker install. The printer is set to cloud connection with LAN video on.

@rice1204 Are you using a P2S? I just tried that daily build with LAN Only and again set to Cloud and I get no video stream on my P2S from BamBuddy. I am on firmware 01.01.03.00.

@ddetton commented on GitHub (Mar 14, 2026): > Just discovered bambuddy. Amazing software! > > Just wanted to report that I'm able to get very smooth (15-20fps) 1080p video on v0.2.2b4-daily.20260313. No discernable drops after watching the stream for about 10 minutes. My bambuddy instance is a fresh docker install. The printer is set to cloud connection with LAN video on. @rice1204 Are you using a P2S? I just tried that daily build with LAN Only and again set to Cloud and I get no video stream on my P2S from BamBuddy. I am on firmware 01.01.03.00.

BreizhHardware commented

bambuddy-support-20260314-123320.zip

Author

Owner

@ddetton commented on GitHub (Mar 14, 2026):

please try again with branch test/issue_661.

@maziggy No change from yesterday. internal cam stuck on still image and external times out. I can access the stream directly from go2rtc and it's totally fine. My support log is attached.

@ddetton commented on GitHub (Mar 14, 2026): > please try again with branch test/issue_661. @maziggy No change from yesterday. internal cam stuck on still image and external times out. I can access the stream directly from go2rtc and it's totally fine. My support log is attached. [bambuddy-support-20260314-123320.zip](https://github.com/user-attachments/files/25999698/bambuddy-support-20260314-123320.zip)

BreizhHardware commented

Author

Owner

@rice1204 commented on GitHub (Mar 14, 2026):

Oops! overlooked the test branch. I'll try that out when I get a chance.

@ddetton yes, this is on p2s. FW version 01.01.01.00 (the one that came from factory for me). I haven't tried other fw yet

@rice1204 commented on GitHub (Mar 14, 2026): Oops! overlooked the test branch. I'll try that out when I get a chance. @ddetton yes, this is on p2s. FW version 01.01.01.00 (the one that came from factory for me). I haven't tried other fw yet

BreizhHardware commented

Author

Owner

@ddetton commented on GitHub (Mar 14, 2026):

@rice1204 You might want to stick with 01.01.01.00. Yours works and mine does not. I am going to look into whether it's possible to downgrade firmware.

Ok, I downgraded my P2S to the same firmware @rice1204 is running 01.01.01.00 and tried it against test/issue_661, latest, and daily and I still can not get the video stream from the P2S. I also tried it in LAN Only/Developer mode and Cloud enabled and still nothing. WTF is different?

@ddetton commented on GitHub (Mar 14, 2026): @rice1204 You might want to stick with 01.01.01.00. Yours works and mine does not. I am going to look into whether it's possible to downgrade firmware. Ok, I downgraded my P2S to the same firmware @rice1204 is running 01.01.01.00 and tried it against test/issue_661, latest, and daily and I still can not get the video stream from the P2S. I also tried it in LAN Only/Developer mode and Cloud enabled and still nothing. WTF is different?

BreizhHardware commented

Author

Owner

@rice1204 commented on GitHub (Mar 15, 2026):

@ddetton

On the printer, did you reconfirm LAN video is on in the settings?
Also, I installed ffmpeg on the docker host as noted in the docs.

Those are the only 2 things I've changed out of the box that I can think of.

@rice1204 commented on GitHub (Mar 15, 2026): @ddetton - On the printer, did you reconfirm LAN video is on in the settings? - Also, I installed ffmpeg on the docker host as noted in the docs. Those are the only 2 things I've changed out of the box that I can think of.

BreizhHardware commented

Author

Owner

@ddetton commented on GitHub (Mar 15, 2026):

@rice1204

I have LAN Liveview enabled on the printer. Not sure if this is what you're calling LAN Video. Where did you find ffmpeg in the docs? Is it installed as another service in docker? I installed a go2rtc service in docker but not ffmpeg.

UPDATE: I just checked and ffmpeg 7.1.3 is baked into the bambuddy container. Not sure what else would need to be done related to this.

@ddetton commented on GitHub (Mar 15, 2026): @rice1204 I have LAN Liveview enabled on the printer. Not sure if this is what you're calling LAN Video. Where did you find ffmpeg in the docs? Is it installed as another service in docker? I installed a go2rtc service in docker but not ffmpeg. UPDATE: I just checked and ffmpeg 7.1.3 is baked into the bambuddy container. Not sure what else would need to be done related to this.

BreizhHardware commented

Author

Owner

@rice1204 commented on GitHub (Mar 15, 2026):

Sorry, I'm out of ideas. If you're running docker version, ffmpeg should already be included in the image.

I thought the setting on the printer was called LAN video but it could have been LAN liveview. When I get home, I'll try to get a photo of the exact configuration setting that enabled the camera.

@rice1204 commented on GitHub (Mar 15, 2026): Sorry, I'm out of ideas. If you're running docker version, ffmpeg should already be included in the image. I thought the setting on the printer was called LAN video but it could have been LAN liveview. When I get home, I'll try to get a photo of the exact configuration setting that enabled the camera.

BreizhHardware commented

Author

Owner

@ddetton commented on GitHub (Mar 15, 2026):

@maziggy

Got some help today from Google Gemini. We were able to get the P2S video stream to play in bambuddy using the external camera and go2rtc. I don't fully understand the solution but it's fast, reliable and has a decent frame rate. Here is the go2rtc.yaml config:

streams:
  # This is the primary stream from your P2S
  p2s_camera:
    - rtsps://bblp:[access_id]@192.168.101.41:322/streaming/live/1

  p2s_mjpeg:
    - "ffmpeg:http://127.0.0.1:1984/api/stream.mp4?src=p2s_camera#video=mjpeg#args=-r 2"

Here is the MJPEG url in BamBuddy:

http://192.168.101.21:1984/api/stream.mjpeg?src=p2s_mjpeg

Maybe you could set this up to see why this works and then refactor it into something a little more straight forward. Let me know if you need me to do anything for you.

@ddetton commented on GitHub (Mar 15, 2026): @maziggy Got some help today from Google Gemini. We were able to get the P2S video stream to play in bambuddy using the external camera and go2rtc. I don't fully understand the solution but it's fast, reliable and has a decent frame rate. Here is the go2rtc.yaml config: ``` streams: # This is the primary stream from your P2S p2s_camera: - rtsps://bblp:[access_id]@192.168.101.41:322/streaming/live/1 p2s_mjpeg: - "ffmpeg:http://127.0.0.1:1984/api/stream.mp4?src=p2s_camera#video=mjpeg#args=-r 2" ``` Here is the MJPEG url in BamBuddy: ``` http://192.168.101.21:1984/api/stream.mjpeg?src=p2s_mjpeg ``` Maybe you could set this up to see why this works and then refactor it into something a little more straight forward. Let me know if you need me to do anything for you.

BreizhHardware commented

Author

Owner

@maziggy commented on GitHub (Mar 15, 2026):

THe question is: what's different on your side? We have plenty of P2S users and don't received a bug report beside yours.

@maziggy commented on GitHub (Mar 15, 2026): THe question is: what's different on your side? We have plenty of P2S users and don't received a bug report beside yours.

BreizhHardware commented

Author

Owner

@DMoenning commented on GitHub (Mar 15, 2026):

I had the same bug since day 1. I started using bambuddy when u promoted it on reddit. I always thought anyone would have created anysway for the problem. But this wasn't the case.

@DMoenning commented on GitHub (Mar 15, 2026): I had the same bug since day 1. I started using bambuddy when u promoted it on reddit. I always thought anyone would have created anysway for the problem. But this wasn't the case.

BreizhHardware commented

Author

Owner

@maziggy commented on GitHub (Mar 15, 2026):

Mhhh.....your Docker network is set to mode host?

@maziggy commented on GitHub (Mar 15, 2026): Mhhh.....your Docker network is set to mode host?

BreizhHardware commented

Author

Owner

@maziggy commented on GitHub (Mar 15, 2026):

Please try again with dev branch.

@maziggy commented on GitHub (Mar 15, 2026): Please try again with dev branch.

BreizhHardware commented

bambuddy-support-20260315-104623.zip

Author

Owner

@ddetton commented on GitHub (Mar 15, 2026):

@maziggy

I wish I knew what is different on my side! I am running BamBuddy (sqlite) in a Docker container on a Synology DS-918+ running DSM 7.2-64570. Docker 24.0.2. ffmpeg 7.1.3. I have tried P2S firmware 01.01.01.00 and 01.01.03.00. On the P2S, I have LAN Only enabled, Dev mode enabled, LAN LiveView enabled. Firefox browser version 148.02 on Windows 11 Pro 25H2. What other specifics are relevant to this discussion?

I built the dev branch today and when external camera is disabled, live video just times out. When I enable external camera and point to my go2rtc instance, live video streaming works beautifully on the P2S using the same url and configuration as yesterday's post.

I have attached today's support log. The last thing I did was set the external camera to point to go2rtc. Just before that, I had external camera disabled.

Here is my docker compose file. Let me know if you recommend any changes.

services:
  bambuddy:
#    image: maziggy/bambuddy:0.2.2b4-daily.20260314
#    image: ghcr.io/maziggy/bambuddy:latest
    build: .    # This tells it to use the local files in the current folder    
    container_name: bambuddy
    user: "1026:100"
    network_mode: host
    # Add these lines to help the container stop faster on Synology
    stop_signal: SIGKILL
    stop_grace_period: 5s
    volumes:
# Change these paths to match your actual Synology folder structure
      - /volume1/docker/bambuddy/data:/app/data
      - /volume1/docker/bambuddy/logs:/app/logs
    environment:
      - TZ=America/Los_Angeles
      - PORT=8080
      - DEBUG=true         # Set to 'true' for detailed troubleshooting
      - LOG_LEVEL=DEBUG    # Options: DEBUG, INFO, WARNING, ERROR
      - HA_URL=https://xyz.ui.nabu.casa/
      - HA_TOKEN=xyz
    restart: unless-stopped

@ddetton commented on GitHub (Mar 15, 2026): @maziggy I wish I knew what is different on my side! I am running BamBuddy (sqlite) in a Docker container on a Synology DS-918+ running DSM 7.2-64570. Docker 24.0.2. ffmpeg 7.1.3. I have tried P2S firmware 01.01.01.00 and 01.01.03.00. On the P2S, I have LAN Only enabled, Dev mode enabled, LAN LiveView enabled. Firefox browser version 148.02 on Windows 11 Pro 25H2. What other specifics are relevant to this discussion? I built the dev branch today and when external camera is disabled, live video just times out. When I enable external camera and point to my go2rtc instance, live video streaming works beautifully on the P2S using the same url and configuration as yesterday's post. I have attached today's support log. The last thing I did was set the external camera to point to go2rtc. Just before that, I had external camera disabled. [bambuddy-support-20260315-104623.zip](https://github.com/user-attachments/files/26007638/bambuddy-support-20260315-104623.zip) Here is my docker compose file. Let me know if you recommend any changes. ``` services: bambuddy: # image: maziggy/bambuddy:0.2.2b4-daily.20260314 # image: ghcr.io/maziggy/bambuddy:latest build: . # This tells it to use the local files in the current folder container_name: bambuddy user: "1026:100" network_mode: host # Add these lines to help the container stop faster on Synology stop_signal: SIGKILL stop_grace_period: 5s volumes: # Change these paths to match your actual Synology folder structure - /volume1/docker/bambuddy/data:/app/data - /volume1/docker/bambuddy/logs:/app/logs environment: - TZ=America/Los_Angeles - PORT=8080 - DEBUG=true # Set to 'true' for detailed troubleshooting - LOG_LEVEL=DEBUG # Options: DEBUG, INFO, WARNING, ERROR - HA_URL=https://xyz.ui.nabu.casa/ - HA_TOKEN=xyz restart: unless-stopped ```

BreizhHardware commented

Author

Owner

@maziggy commented on GitHub (Mar 16, 2026):

I don't know the Synology system, maybe there's something different with the Docker installation or environment.

I would install Bambuddy on another host not running on the NAS to see if that makes any difference.

@maziggy commented on GitHub (Mar 16, 2026): I don't know the Synology system, maybe there's something different with the Docker installation or environment. I would install Bambuddy on another host not running on the NAS to see if that makes any difference.

BreizhHardware commented