Closed cayalag closed 1 month ago
Can you try updating to v2.0.21 and seeing if this still reproes. If it does, I'll need debug logs to see if that shed light on how the camera sensor has gone AWOL.
I tried but, but no luck. Let me know what you need and I’ll get the logs after work. Thanks !!
El 2 may 2024, a las 3:10, AdrianGarside @.***> escribió:
Can you try updating to v2.0.21 and seeing if this still reproes. If it does, I'll need debug logs to see if that shed light on how the camera sensor has gone AWOL.
— Reply to this email directly, view it on GitHubhttps://github.com/greghesp/ha-bambulab/issues/521#issuecomment-2089366227, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A53E2FBJOJCHQNRQSDWAYF3ZAGHAXAVCNFSM6AAAAABHB44YKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBZGM3DMMRSG4. You are receiving this because you authored the thread.Message ID: @.***>
On the P1S the image snapshot camera is under controls not sensors. I haven’t found a force home assistant to put it under sensors like the X1 video feed camera.
Actually… it’s seemingly not consistent. On my production HA instance camera and cover image are both under controls. But your cover image is under sensors. And on my test instance I think they’re both under sensors too (away from my PC so will have to confirm this).
The readme.md file in the root of the source has instructions on how to get debug logs.
Hey Adrian.
I thing I got the debug log. Let me know if that's not what you need.
Regarding where the camera should appear... the other P1S definitely shows the camera feed under sensors:
Thanks again ! Carlos
2024-05-01 18:14:46.048 ERROR (P1S-Chamber-112) [custom_components.bambu_lab.pybambu] Socket error: [SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1000)
Possible that's involved - not an error I've ever seen. One thing that's odd about your log - you said you have two printers but I'm only seeing log output for one?
Looks like I'll need to tweak the logging here since I'm not seeing log output I expect.
Yeah, both printers with the same firmware. The only difference is one of them has 2 AMS units connected to it, but I guess that's not key to the problem
Let me know if there is anything I can test on my side.
Thanks !
my camera stream is also not working
Heyo everyone, has anyone managed to get P1S camera into HomeBridge? I dont have a problem to watch the camera in Assistant (I also have it under Sensors). But when I try to import everything via HomeBridge, camera won't import.
@honzis1364 This is because this integration generates an image.printer_camera entity which is from the image domain, and homekit doesn't allow for image domain publishing. I've just created a ticket for this: https://github.com/greghesp/ha-bambulab/issues/531
I hade the same problem, the camera feed desapeared but after disabling the integration, restarted HA, and activating it again, it started working...
The camera started to work again.
I have had the same problem for two days. The image.camerafeed has disappeared. @xinux87: It's not working for me.
It was working for a bit on my X1C but is no longer working, feels like it stopped after that most recent firmware update? I tried disabling, and re-activating, reinstalling add-in and switching from cloud mode to local ip address mode, none have helped.
It was working for a bit on my X1C but is no longer working, feels like it stopped after that most recent firmware update? I tried disabling, and re-activating, reinstalling add-in and switching from cloud mode to local ip address mode, none have helped.
Power cycling the Bambu printer seems to have resolved this
Stale issue message
+1, No camera feed for my A1 Mini anywhere, ever.
I also never see a camera image with this integration for my X1C. The camera.x1c_<serialNumber>
entity from this integration appears in Home Assistant as Unavailable.
It worked previously, but it's been at least a month or two since I last recall seeing it work.
Integration version: v2.0.22 Bambu firmware version: 01.08.02.00
I have power-cycled my printer, uninstalled and reinstalled the integration, and configured it to talk to my printer over LAN. The camera entity still appears, but as unavailable, after the this process.
+1, No camera feed for my A1 Mini anywhere, ever.
A1 Mini AP07 missing camera is resolved with https://github.com/greghesp/ha-bambulab/pull/589 This will not help the X1C problems.
I am in the latest version of the repo and am also having issues seeing either of my x1 cameras
I am in the latest version of the repo and am also having issues seeing either of my x1 cameras
X1 rtsp support is just very buggy. There's a discussion post on how you can mitigate it using a go2rtc to proxy a single connection and keep it alive.
@cayalag are you still seeing this?
@cayalag are you still seeing this?
Hey Adrian ! Yeah still around. I keep having access to one of the P1S video feed but the other one no luck
Hi i see this issue too... powercycling the p1s helps for a it... Additional question: can i somehow Integrate the camera Feed to octoprint.... I got it working temporarily but the ha access token renews quickly and all i found was not so helpful or to complicated...
After updating both HA and BambuLab and rebooting both printers, the cameras show and consistently for 3 days now on my X1Cs
@cayalag can you provide debug logs of the non-working case please.
@cayalag can you provide debug logs of the non-working case please.
I have just updated to the last version of the integration and lost the camera feed on the printer that used to work !
These are the diagnostic files on both printers (first the one that never showed the camera, second the one that just lost the feed)
First:
config_entry-bambu_lab-57025516499b9b35642d620f801e222f-2.json
Second:
config_entry-bambu_lab-d3761cb7963f4d01d59058b9a2e23f0b.json
Same. For some reason the cameras on the printers in the middle of a job show no feed, but the one that is not shows a good feed. I will not know if it's only applicable to the non printing devices, until that job finishes tomorrow
@cayalag can you provide debug logs of the non-working case please.
I have just updated to the last version of the integration and lost the camera feed on the printer that used to work !
These are the diagnostic files on both printers (first the one that never showed the camera, second the one that just lost the feed)
First:
config_entry-bambu_lab-57025516499b9b35642d620f801e222f-2.json
Second:
config_entry-bambu_lab-d3761cb7963f4d01d59058b9a2e23f0b.json
The newer build replaced the image 'camera' with a camera camera. Which means the entity name changes. You'll need to delete that and put the new camera entity into your dashboards. Please check to see if one or both printers has that present and working.
Hi AdrianGarside i replaced the image entity with the camera entity on the dashboard after reconfigure the integration but still i got no image here is my debug log (hope this is the one you need ... )
home-assistant_bambu_lab_2024-10-27T03-11-58.787Z.log home-assistant_2024-10-27T03-14-04.555Z.log
Can you view the camera successfully from the device itself? There are gotchas trying to get a camera to be live in a dashboard so please confirm it's not working when viewed directly from the device:
Looks like you were adding/removing the printer repeatedly in the logs? Once added I see the chamber image thread started without any errors so as best I can tell the integration should be receiving the images at that point.
The second log file does have a timeout error for the chamber image connection seemingly out of the blue but also no log evens for a bit over a minute prior to that - did you turn the printer off?
strange :( i have tried to reconfig the printer for maximal debug logs :D in the Second log the printer was still on but not sure if it was printing at that moment....
In the Device itself the Entitiy is also not showing an image... all i get is the title
from the dev tools i can see that it should be able to accessible via the url - but it gives me an "500: Internal Server Error" ... maybe another hint?
access_token: redacted brand: Bambu Lab entity_picture: >- /api/camera_proxy/camera.p1s_xxxxxxxxxx_camera?token=redacted icon: mdi:camera friendly_name: P1S_xxxxxxxxxx Camera supported_features: 0
i got it working by refreshing the access code on the printer... still dont know what exactly the problem was... i viewed in the code of the camera.py - since i want to use obico via octoprint and some more plugins i need the stream there... when i want to grab the stream the rtpsps url must be rtsps://bblp:accesscode@192.168.2.119/streaming/live/1 am i right?
btw https://github.com/MrDrache333/webcamd works now too -.- thats my workaroud if the direct stream does not work
The newer build replaced the image 'camera' with a camera camera. Which means the entity name changes. You'll need to delete that and put the new camera entity into your dashboards. Please check to see if one or both printers has that present and working.
Now none of the printers have an entity that allows me to access the camera, it even disappeared from the Sensors section:
I'm a little newer to this; how do I remove the old camera entity and add the new entity? I go into the printer device and sensor location but it won't let me remove the "camera.old_bambu_entir_camera" and then add a new one. I'm sorry
@nramo013 The old one was image.[printer]_camera. When you upgrade that remains present but stops working. Clicking it should give you a popup saying that the integration is no longer providing this entity and an option (bottom left IIRC) to delete it.
The new is camera.[printer]_camera.
With an upgrade, both should be showing up in your device page - the image one sometimes showed up in the top 'controls' section inconsistently for some people.
i got it working by refreshing the access code on the printer... still dont know what exactly the problem was... i viewed in the code of the camera.py - since i want to use obico via octoprint and some more plugins i need the stream there... when i want to grab the stream the rtpsps url must be rtsps://bblp:accesscode@192.168.2.119/streaming/live/1 am i right?
btw https://github.com/MrDrache333/webcamd works now too -.- thats my workaroud if the direct stream does not work
No, the rtsp feed is solely for the X1. It has a completely different way to expose it's camera and you have an P1S. It just has a way of receiving static images every ~2 seconds from the printer and we used to just expose that as an image until just recently where someone found the built-in way to cheaply get HA to expose those images as a true camera.
@secco04 "i got it working by refreshing the access code on the printer..." - that means it was a permissions issue accessing the printer to get the camera images. But I would have expected to have seen errors for that in your logs. The timeouts are probably related since I've not observed those when I turn off my printers but in your logs one minute after the integration disconnects from the offline printer there was always a timeout error.
I am now at v2.0.26... deleted both printers, configure them back and none of them has a camera entity.
@AdrianGarside any other suggestion of what I can do at this stage ?
My cameras show up as camera._xxx_xxx__camera but they do not stream while I am printing. When they are idle, they will show:
@nramo013 the X1C camera issues are a different problem. See #221.
@cayalag can you get me a fresh debug log of HA startup with neither of your two printers getting the camera entity? And to double check - you provided the local IP address when adding the printers?
@cayalag can you get me a fresh debug log of HA startup with neither of your two printers getting the camera entity? And to double check - you provided the local IP address when adding the printers?
Full reset of HA and this is the log. Thanks !
@cayalag can you get me a fresh debug log of HA startup with neither of your two printers getting the camera entity? And to double check - you provided the local IP address when adding the printers?
Full reset of HA and this is the log. Thanks !
^^ Interesting lines in your log file.... FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3.10/site-packages/ffmpeg' 2024-10-27 21:00:17.443 WARNING (MainThread) [haffmpeg.tools] Error starting FFmpeg.
Some lines above state that python 3.12 is beeing used
ffmpeg being bust might explain missing visuals although I think it's unrelated to this integration, but wouldn't explain missing entities.
In the very latest dev release (2.0.27-dev1) I added extra logging to capture the case where we do not have printer IP address and/or access code. The latter gets auto populated during cloud setup of a printer but the local IP address you must enter manually. It is required for camera access. I don't think you provided that during printer setup?
ffmpeg being bust might explain missing visuals although I think it's unrelated to this integration, but wouldn't explain missing entities.
In the very latest dev release (2.0.27-dev1) I added extra logging to capture the case where we do not have printer IP address and/or access code. The latter gets auto populated during cloud setup of a printer but the local IP address you must enter manually. It is required for camera access. I don't think you provided that during printer setup?
I deleted everything, installed 2.0.27-dev2 and reinstalled the printers. If I add the IP address, it fails to connect to the printer:
When I don't provide the IP the printer gets recognized (however the one with 2 AMS gets only recognized as printer without AMS... which worked until previous version)
Still no camera for neither of the printers.
Last log attached:
Debug logs weren't enabled but it is expected that you won't get a camera if the printer IP isn't provided. I'd need debug logs to have a chance to know why it failed the test connection at that point. You'll need to turn debug logs on in the configuration.yaml to get them for the initial integration setup. All I see in these logs is that the mqtt connection to the printer is repetitively being denied with access denied. In one case (that I know of) the pin code retrieved from bambu cloud was incorrect for the printer which is why I show it in that screen - so double check that against what the printer says it should be.
configuration.yaml to turn on debug logs permanently for the integration. This is chatty so once we get you sorted you'll want to remove this:
logger:
default: info
logs:
custom_components.bambu_lab: debug
There's a race condition during setup where sometimes the AMS's don't get added that I haven't found a solution for yet. But so far they've always appeared on a reload of the integration / restart of home assistant. But this latest version did have a change to delete orphaned AMS's that could be misbehaving. So if they appear on restarting HA / reloading the integration then it's the known issue. If they remain MIA, please let me know (and provide debug logs of an integration load :)).
Debug logs weren't enabled but it is expected that you won't get a camera if the printer IP isn't provided. I'd need debug logs to have a chance to know why it failed the test connection at that point. You'll need to turn debug logs on in the configuration.yaml to get them for the initial integration setup. All I see in these logs is that the mqtt connection to the printer is repetitively being denied with access denied. In one case (that I know of) the pin code retrieved from bambu cloud was incorrect for the printer which is why I show it in that screen - so double check that against what the printer says it should be.
configuration.yaml to turn on debug logs permanently for the integration. This is chatty so once we get you sorted you'll want to remove this:
logger: default: info logs: custom_components.bambu_lab: debug
There's a race condition during setup where sometimes the AMS's don't get added that I haven't found a solution for yet. But so far they've always appeared on a reload of the integration / restart of home assistant. But this latest version did have a change to delete orphaned AMS's that could be misbehaving. So if they appear on restarting HA / reloading the integration then it's the known issue. If they remain MIA, please let me know (and provide debug logs of an integration load :)).
It Works !! With the last update to dev2 I had forgotten to activate debug logs as you said. So the only thing I did was to edit the yaml, delete printers once again... reset HA, config the printers again (this time it worked when adding IPs) and both of them show camera feeds and AMS.
Thanks Adrian !
Describe the bug
Hello !
I have added my second P1S and everything seems to be correct. However, I am missing the camera feed.
To Reproduce
Expected Behaviour
I was expecting to find it under Sensors, same as the other printer.
What device are you using?
P1S
Diagnostic Output
Log Extracts
No response
Other Information
No response