Thanks for your work, i’ve been using your plugin since my begining with HA.
Just migrate from Octoprint to the new plugin 3D printer, backup seem to be working without major issues.
Only my printer profile was missing but this is a matter of seconds to make it again. And of course my database of spool manager but that’s on me, i’ve completely forget to export it.
Need mor time to see if there is any problem with the backup but so far it look complete !
I can’t start this plugin. I tried everything what I can with this and still…
[22:27:13] INFO: OctoPrint cont-init.d
Traceback (most recent call last):
File "/data/python/octoprint/bin/octoprint", line 8, in <module>
sys.exit(main())
File "/data/python/octoprint/lib/python3.9/site-packages/octoprint/__init__.py", line 959, in main
from octoprint.util.fixes import patch_sarge_async_on_py2
File "/data/python/octoprint/lib/python3.9/site-packages/octoprint/util/__init__.py", line 52, in <module>
from octoprint.util.connectivity import ConnectivityChecker # noqa: F401
File "/data/python/octoprint/lib/python3.9/site-packages/octoprint/util/connectivity.py", line 12, in <module>
from octoprint.util.net import resolve_host, server_reachable
File "/data/python/octoprint/lib/python3.9/site-packages/octoprint/util/net.py", line 14, in <module>
import netifaces
ModuleNotFoundError: No module named 'netifaces'
[cont-init.d] octoprint.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
s6-nuke: fatal: unable to kill: No such process
I assume this is with the 3DPrinter addon, on what hardware and architecture? Was this from a clean install of the addon or did you attempt to restore a backup?
Could you try with the latest update, 2021.11.2.? I haven’t had time to test it more than update from an intentionally broken system (removed netifaces), but the changes have mainly been to the script that prepares OctoPrint startup.
Is it the same with 3dprinter addon version 2021.11.3? I added py-netifaces after a suggestion on GitHub, other than that it should be the same as 2021.11.2.
This is somewhat difficult for me to debug as I haven’t encountered the issue myself. Did you use the 32- or 64-bit install of Home Assistant OS?
Update: I installed the 32-bit version of Home Assistant OS on my Pi 3B and got the error, so now I should have a better chance to debug it.
I have updated to latest 2021.11.4 with the same problem. Im also using PI 3B [23:49:38] INFO: Starting octoprint... Traceback (most recent call last): File "/data/python/octoprint/bin/octoprint", line 8, in <module> sys.exit(main()) File "/data/python/octoprint/lib/python3.9/site-packages/octoprint/__init__.py", line 959, in main from octoprint.util.fixes import patch_sarge_async_on_py2 File "/data/python/octoprint/lib/python3.9/site-packages/octoprint/util/__init__.py", line 52, in <module> from octoprint.util.connectivity import ConnectivityChecker # noqa: F401 File "/data/python/octoprint/lib/python3.9/site-packages/octoprint/util/connectivity.py", line 12, in <module> from octoprint.util.net import resolve_host, server_reachable File "/data/python/octoprint/lib/python3.9/site-packages/octoprint/util/net.py", line 14, in <module> import netifaces ModuleNotFoundError: No module named 'netifaces''
I think I’ve isolated the issue to 32-bit installs of Home Assistant OS, and currently see two main options as I haven’t figured out how to fix it:
Disable support for architecture armv7, which I think is the only version affected by this.
Reinstall packages in the python virtual environment if OctoPrint install seems broken (octoprint --version fails).
I’m currently building and update with the second approach, it should be up within an hour but it will be sometime tomorrow that I can check if it really works. The main downside to this workaround is the time it takes to complete the reinstall of all pip packages.
Update: it’s available and seems to work.
@Bizzmo and @MarcinNo do you know if you installed the 32- or 64-bit version of Home Assistant OS?
Hello Fredrik
I recently installed your 3DPRINTER add-on to my Home Assistant running on a Raspberry Pi 4
It really makes a difference to be able to operate the Ender3 V2 from the web interface compared to running back and forth with an sd-card.
I have one issue that I hope you can assist with. It might come down to my less than stellar knowledge of Linux. I have attached a Microsoft Life-Cam to the Pi and have found the values of -r 1920x1080 -f 30 which I apparently need to add to a file called octopi.txt
However, I am unable to find this file, even if I remove the memory card from the Pi and insert it into my Windows 10 computer. After searching for a while, it seems Home Assistant is running in a container (?) which makes it challenging to find the file to edit. Am I correct in assuming these values must be entered into this specific file and that this is not possible somewhere in the web interface of 3DPRINTER?
I can use Putty to connect to the Pi using port 22, but I get the feeling this is not the correct way as I still cannot find the octopi.txt file anywhere.
Yes, the “3DPrinter” addon is a container, so the instructions for OctoPi or similar will not work.
You could try the following:
Enable the checkbox “mjpg-streamer” in addon settings,
Add the arguments to the field mjpg_input, it should be something like -i "input_uvc.so -n -r 1920x1080 -f 30".
Note that there is an issue where the video stream is not visible with Ingress, it may be necessary to either set the port for mjpg-streamer or setup a reverse proxy.
There is also a separate addon called mjpg-streamer that can be used.
2021-11-16 11:23:21,030 - tornado.access - WARNING - 403 GET /api/job (172.30.32.1) 13.00ms
2021-11-16 11:23:41,530 - octoprint.server.util.flask - INFO - Passively logging in user homeassistant from 172.30.32.2 via autologin
2021-11-16 11:23:41,532 - octoprint.access.users - INFO - Logged in user: homeassistant
2021-11-16 11:23:42,754 - tornado.access - WARNING - 403 GET /sockjs/909/0plwklsl/websocket (172.30.32.2) 2.03ms
2021-11-16 11:23:51,025 - tornado.access - WARNING - 403 GET /api/job (172.30.32.1) 10.27ms
2021-11-16 11:24:21,020 - tornado.access - WARNING - 403 GET /api/job (172.30.32.1) 8.47ms
2021-11-16 11:24:51,021 - tornado.access - WARNING - 403 GET /api/job (172.30.32.1) 10.25ms
2021-11-16 11:25:21,021 - tornado.access - WARNING - 403 GET /api/job (172.30.32.1) 8.70ms
2021-11-16 11:25:51,025 - tornado.access - WARNING - 403 GET /api/job (172.30.32.1) 11.13ms
2021-11-16 11:26:21,024 - tornado.access - WARNING - 403 GET /api/job (172.30.32.1) 11.20ms
2021-11-16 11:26:51,021 - tornado.access - WARNING - 403 GET /api/job (172.30.32.1) 8.58ms
2021-11-16 11:27:21,027 - tornado.access - WARNING - 403 GET /api/job (172.30.32.1) 7.29ms
2021-11-16 11:27:51,023 - tornado.access - WARNING - 403 GET /api/job (172.30.32.1) 10.76ms
Supervisor log:
21-11-16 11:22:04 INFO (SyncWorker_1) [supervisor.docker.interface] Stopping addon_774437fd_octoprint-next application
21-11-16 11:22:05 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_774437fd_octoprint-next application
21-11-16 11:22:11 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on fredrikbaberg/octoprint-aarch64-image with version 0.4.4
21-11-16 11:22:43 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.7:8099 ssl:default [Connect call failed (‘172.30.33.7’, 8099)]
21-11-16 11:23:42 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 403, message=‘Invalid response status’, url=URL(‘http://172.30.33.7:8099/sockjs/909/0plwklsl/websocket’)
This only happens in standard octoprint container.
This issue is not present in octoprint dev and octoprint next container.
I tried to remove container and reinstall it multiple times. Host reboot was also done.
Is there a specific reason you want to use the version “OctoPrint”? It was some time since I updated that version, I plan to remove it soon. I haven’t updated the descriptions yet, but I’ll do that this week to clarify that it shouldn’t be used anymore.
If you are starting form a clean install I’d suggest you try the addon called “3DPrinter”, I intend to deprecate and eventually remove all other versions.
With all the versions I understand the confusion of which one of the addons to use, especially if not following all the comments here. I’ve now marked all addons named something with “OctoPrint” as deprecated. I won’t remove them yet, but I also don’t intend to provide update to any of them.
For clarification I’ve:
Updated the first post in this thread.
Updated the name of each of those addons to reflect this.
Updated the stage of each addon named something with OctoPrint to “deprecated”.
Updated the README of each of those addons to reflect this.
Updated the repository README to reflect this.
I haven’t marked the addon 3DPrinter as stable yet, I’ll wait until the end of the month to see if any new bugs are discovered.
A big difference compared to the earlier versions is that I no longer have a “slim” version, the image of 3DPrinter addon is close to 1 GB. I don’t want to end up with a lot of different versions that I don’t maintain again, but let me know if there is a need for a basic version with only OctoPrint - no additional features such as build tools (useful for some plugins), mjpg-streamer, CuraEngine Legacy, Klipper etc.
I’m running the “3DPrinter” Addon version: 2021.11.7. I’ve successfully connected it to Cura and enabled the ports for OctoPrint WebUI (5000) and Camera WebUI (8000). I have a raspberry pi 5mp camera directly connected.
I checked the box for mpg_streamer and left the default config -i “input_uvc.so -n” and -o “output_http.so -w /www_mjpg -p 8080” for input and output alone.
Despite this both the webcam stream and snapshots do not show in octoprint UI or in Cura.
Is there anything further I need to configure to make this work? Do I leave the octoprine settings as just “/webcam/?action=stream” - When I click the test button nothing loads.
Have you also setup Home Assistant OS to be able to access the camera? There is a link in the following post that could be helpful there is a link in this reply that could be useful: Repository: OctoPrint - #151 by L4RGER. I did it the old way, modifying/replacing start_x.elf, fixup_elf.dat, but if you are using a recent version of Home Assistant OS it seems enough to modify config.txt.
If mjpg-streamer runs properly taking snapshots should work with the default configuration. You should be able to see if mjpg-streamer runs properly in the log, or if there is an issue accessing the camera.
No I had not. Luckily I was running Hass-OS 6.4 so just need to modify config and reboot. Thanks for your help!
I did have to replace the Stream URL inside the octoprint program with http://192.168.0.10:8000/?action=stream which make sense seeing as it’s being streamed from outside the container.