crowsnest VS sonar

pi@mainsailos:~ $ git clone https://github.com/mainsail-crew/crowsnest.git

[server] host: 0.0.0.0 port: 7125 klippy_uds_address: /home/biqu/printer_data/comms/klippy.sock [authorization] trusted_clients: 10.0.0.0/8 127.0.0.0/8 169.254.0.0/16 172.16.0.0/12 192.168.0.0/16 FE80::/10 ::1/128 cors_domains: *.lan *.local *://localhost *://localhost:* *://my.mainsail.xyz *://app.fluidd.xyz [octoprint_compat] [history] [update_manager] channel: dev refresh_interval: 168 [update_manager mainsail-config] type: git_repo primary_branch: master path: ~/mainsail-config origin: https://github.com/mainsail-crew/mainsail-config.git managed_services: klipper [update_manager mainsail] type: web channel: stable repo: mainsail-crew/mainsail path: ~/mainsail [update_manager crowsnest] type: git_repo path: ~/crowsnest origin: https://github.com/mainsail-crew/crowsnest.git install_script: tools/install.sh # Sonar update_manager entry [update_manager sonar] type: git_repo path: ~/sonar origin: https://github.com/mainsail-crew/sonar.git primary_branch: main managed_services: sonar install_script: tools/install.sh [update_manager timelapse] type: git_repo primary_branch: main path: ~/moonraker-timelapse origin: https://github.com/mainsail-crew/moonraker-timelapse.git managed_services: klipper moonraker [update_manager KlipperScreen] type: git_repo path: ~/KlipperScreen origin: https://github.com/jordanruthe/KlipperScreen.git env: ~/.KlipperScreen-env/bin/python requirements: scripts/KlipperScreen-requirements.txt install_script: scripts/KlipperScreen-install.sh managed_services: KlipperScreen

I'm runnin Mainsail on a RPI4 for my 3D printer, and I connected a Logitech C920 camera which is streaming video on http:///webcam/?action=stream using Crowsnest

● crowsnest.service - crowsnest - Multi Webcam/Streamer Control Deamon Loaded: loaded (/etc/systemd/system/crowsnest.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2023-06-07 11:14:19 EDT; 51min ago Docs: https://github.com/mainsail-crew/crowsnest Process: 1988 ExecStart=/usr/local/bin/crowsnest $CROWSNEST_ARGS (code=exited, status=1/FAILURE) Main PID: 1988 (code=exited, status=1/FAILURE) CPU: 1.660s

Hello, thank you for looking into this for me. The 3d printer is running Tailscale on a Raspberry Pi. I’ve tried accessing the stream from both Windows computers and iOS. There are no error messages, just a black screen with a forever-spinning wheel. I can access the GUI, it’s just the video stream that is not going thru. I’m not sure if it uses multicast trafficking. I’m a newbie in these matters. The specific service involved is called Crowsnest. https://github.com/mainsail-crew/crowsnest

That resolved the issue for me. Issue thread: https://github.com/mainsail-crew/crowsnest/issues/112

You need to install crowsnest

[server] host: 0.0.0.0 port: 7125 klippy_uds_address: /home/biqu/printer_data/comms/klippy.sock [authorization] trusted_clients: 10.0.0.0/8 127.0.0.0/8 169.254.0.0/16 172.16.0.0/12 192.168.0.0/16 FE80::/10 ::1/128 cors_domains: *.lan *.local *://localhost *://localhost:* *://my.mainsail.xyz *://app.fluidd.xyz [octoprint_compat] [history] [update_manager] channel: dev refresh_interval: 168 [update_manager mainsail-config] type: git_repo primary_branch: master path: ~/mainsail-config origin: https://github.com/mainsail-crew/mainsail-config.git managed_services: klipper [update_manager mainsail] type: web channel: stable repo: mainsail-crew/mainsail path: ~/mainsail [update_manager crowsnest] type: git_repo path: ~/crowsnest origin: https://github.com/mainsail-crew/crowsnest.git install_script: tools/install.sh # Sonar update_manager entry [update_manager sonar] type: git_repo path: ~/sonar origin: https://github.com/mainsail-crew/sonar.git primary_branch: main managed_services: sonar install_script: tools/install.sh [update_manager timelapse] type: git_repo primary_branch: main path: ~/moonraker-timelapse origin: https://github.com/mainsail-crew/moonraker-timelapse.git managed_services: klipper moonraker [update_manager KlipperScreen] type: git_repo path: ~/KlipperScreen origin: https://github.com/jordanruthe/KlipperScreen.git env: ~/.KlipperScreen-env/bin/python requirements: scripts/KlipperScreen-requirements.txt install_script: scripts/KlipperScreen-install.sh managed_services: KlipperScreen

Mainsail has a daemon tool to help fix the issue after which I used seemed to make thing much better… it’s called sonar https://github.com/mainsail-crew/sonar

I actually used sonar (https://github.com/mainsail-crew/sonar) and have not been disconnected for days... Kinda a hacky way to do it, but it works.

Set up Sonar, it will keep your wifi connection active so this doesn't happen.

Sonar

[server] host: 0.0.0.0 port: 7125 # The maximum size allowed for a file upload (in MiB). Default 1024 MiB max_upload_size: 1024 # Path to klippy Unix Domain Socket klippy_uds_address: ~/printer_data/comms/klippy.sock [file_manager] # post processing for object cancel. Not recommended for low resource SBCs such as a Pi Zero. Default False enable_object_processing: False [authorization] cors_domains: https://my.mainsail.xyz http://my.mainsail.xyz http://*.local http://*.lan trusted_clients: 10.0.0.0/8 127.0.0.0/8 169.254.0.0/16 172.16.0.0/12 192.168.0.0/16 FE80::/10 ::1/128 # enables partial support of Octoprint API [octoprint_compat] # enables moonraker to track and store print history. [history] # this enables moonraker announcements for mainsail [announcements] subscriptions: mainsail # this enables moonraker's update manager [update_manager] refresh_interval: 168 enable_auto_refresh: True [update_manager mainsail] type: web channel: stable repo: mainsail-crew/mainsail path: ~/mainsail [update_manager mainsail-config] type: git_repo primary_branch: master path: ~/mainsail-config origin: https://github.com/mainsail-crew/mainsail-config.git managed_services: klipper ### moonraker-timelapse ### Don't forget to include timelapse.cfg to your printer.cfg ### Uncomment to enable moonraker-timelapse #[update_manager timelapse] #type: git_repo #primary_branch: main #path: ~/moonraker-timelapse #origin: https://github.com/mainsail-crew/moonraker-timelapse.git #managed_services: klipper moonraker #[timelapse] ### Directory where the generated video will be saved #output_path: ~/timelapse/ ### Directory where ffmpeg is installed #ffmpeg_binary_path: /usr/bin/ffmpeg # Crowsnest update_manager entry [update_manager crowsnest] type: git_repo path: ~/crowsnest origin: https://github.com/mainsail-crew/crowsnest.git managed_services: crowsnest install_script: tools/install.sh # Sonar update_manager entry [update_manager sonar] type: git_repo path: ~/sonar origin: https://github.com/mainsail-crew/sonar.git primary_branch: main managed_services: sonar install_script: tools/install.sh [update_manager timelapse] type: git_repo primary_branch: main path: ~/moonraker-timelapse origin: https://github.com/mainsail-crew/moonraker-timelapse.git managed_services: klipper moonraker [timelapse] ## Following basic configuration is default to most images and don't need ## to be changed in most scenarios. Only uncomment and change it if your ## Image differ from standart installations. In most common scenarios ## a User only need [timelapse] in there configuration. #output_path: ~/timelapse/ ## Directory where the generated video will be saved #frame_path: /tmp/timelapse/ ## Directory where the temporary frames are saved #ffmpeg_binary_path: /usr/bin/ffmpeg ## Directory where ffmpeg is installed

Unparsed config option 'origin: https://github.com/mainsail-crew/sonar.git' detected in section [update_manager sonar]. This may be an option no longer available or could be the result of a module that failed to load. In the future this will result in a startup error.

Otherwise, you can use a tool like Sonar to keep the wifi connection alive.