spants

Community Developer
  • Posts

    637
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by spants

  1. On 3/19/2022 at 8:55 PM, 007craft said:


    When I use /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 (The only entry I have, and is indeed my printer as when I unplug it, that entry goes away), it doesn't work.  But when I use /dev/ttyUSB0 it works.  Why is this?

     

    I have no idea - it should work! (sorry, I know that isn't a proper answer. I will reinstall my setup and check in a couple of days)

  2. 11 hours ago, 007craft said:

    Is there a way to get multiple webcams working with this template?  I know it can be done, and theres an octoprint plugin to view multi webcams easily and octolapse also works with multiple webcams.  I just cant figure out how to pass multiple cameras into the container.  A second mjpeg streaming instance needs to be made for the second webcam I believe.

     

    You probably could by adding extra keys, but you can also spin up another docker (use one for each printer)-that is what I did!

     

  3. 54 minutes ago, bdydrp said:

    Not sure if i should post this in this mqtt thread or Nginx Proxy Manager thread, but since i have NPM woking for other proxys, i thought i would start here

    What i would like to do is be able to reach my mqtt broker form outside my local network. 

    I have a duckdns name set..eg. mymqtt.duckdnsorg

    In NPM have a a host a ssuch

    image.png.8d84df5576b4daecfbfc4d168d9ea48c.png

     

    But on my phone or nodered i cant access my mqtt broker

    Is this possible to achieve?

     

    I know i can leave my vpn running 24/7 on the phone, and just access it that way. but i'm looking for a different solution so i dont have to do that on my wifes phone

     

    Cheers

     

    just create a strong user/password and use port forwarding from your router to the mqtt port?. 

  4. 8 hours ago, OneMeanRabbit said:

    I'm getting a weird situation with node-red specifically (tried multiple images - same issue).  When it pulls the image and tries to copy /data into my persistent mapping - it fails.  It specifically is creating folders/files with:

     

    sonny:ssh-allow

     

    permissions, but I cannot figure out how to solve it....This is my exact issue!  And here - forces 1000 or 1001 UID which makes sense because that matches the user (not sure where "ssh-access" comes from) my /etc/passwd file.

    Solution attempt #1 - kinda fixes it - Tried adding "--user nobody" to Extra Parameters, and it at least installs and runs immediately..but with sonny:1000 vs. sonny:ssh-access...

     

    Every other docker I have doesn't do this and most use nobody:users - especially when I set PGID/PUID/UMASK variables.  I tried doing manually adding those specific variables, but no dice. 

     

    I've googled everywhere, and it *maybe* a recent sshd_config change since 6.9?  Anyway I can force the docker to run with specific permissions nobody:user?

     

    yes, I see a few people on the internet see the same problem. I wonder if adding 

    --user="nobody:users"

    to extra parameters would make a difference?.
    Otherwise you may have to chmod the data directory = 
    https://github.com/node-red/node-red-docker/wiki/Permissions-and-Persistence

  5. On 1/19/2022 at 10:06 PM, jeuser said:

    Hello,

    is this the right place for support for the "zigbee2mqtt"-docker?

     

    I tried to setup it and also edited the configuration.yaml but it won't start.

    What does "- frontend must be object" mean in the log?

     

    Thank you. 🙂

     

    homeassistant: false
    permit_join: true
    mqtt:
      base_topic: zigbee2mqtt
      server: mqtt://192.168.1.163
      user: loxberry
      password: PASSWORD
    serial:
      port: >-
        /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_3c97c5fcdac9eb1194998f4f1d69213e-if00-port0
    advanced:
      homeassistant_legacy_entity_attributes: false
      legacy_api: false
    device_options:
      legacy: false
    frontend:
    port: 9442

     

    Using '/app/data' as data directory
    
    
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    READ THIS CAREFULLY
    
    Refusing to start because configuration is not valid, found the following errors:
    - frontend must be object
    
    If you don't know how to solve this, read https://www.zigbee2mqtt.io/guide/configuration
    
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

     

     

     

    Its not my docker, but did you fix it? I use the zigbee2mqtt docker as well so I will try and help

    • Like 1
  6. On 1/24/2022 at 5:59 PM, Shrike said:

    Any chance of changing the underlying node-red image to 2.1.6-16 so it'd be possible to use addons that require NodeJs 16?

     

    2022-01-24T17:58:54.815Z [err]  Not compatible with your version of node/npm: [email protected]
    2022-01-24T17:58:54.815Z [err] npm ERR! notsup Required: {"node":">=16.6.0"}
    2022-01-24T17:58:54.815Z [err] npm ERR! 
    2022-01-24T17:58:54.815Z [err] notsup Actual:   {"npm":"6.14.15","node":"14.18.2"}

     

     

    You can change your own: chgange the repository field to  nodered/node-red:2.1.6-16

  7. 1 hour ago, Andiroo2 said:

     

    I just tried a fresh pull and still the same behaviour.  I can't get the GUI to load, but the system reports positive status:

    pihole status
    
      [✓] FTL is listening on port 53
         [✓] UDP (IPv4)
         [✓] TCP (IPv4)
         [✓] UDP (IPv6)
         [✓] TCP (IPv6)
    
      [✓] Pi-hole blocking is enabled

     

    ...and if I tail the log, I see activity:

    # pihole -t
      [i] Press Ctrl-C to exit
    08:09:17: forwarded 197.1.168.192.in-addr.arpa to 1.0.0.2
    08:09:17: forwarded 197.1.168.192.in-addr.arpa to 1.0.0.2
    08:09:19: query[AAAA] diag.meethue.com from 192.168.1.103
    08:09:19: forwarded diag.meethue.com to 1.1.1.2
    08:09:19: forwarded diag.meethue.com to 1.0.0.2
    08:09:19: forwarded diag.meethue.com to 1.0.0.2
    08:09:22: query[PTR] 197.1.168.192.in-addr.arpa from 127.0.0.1

     

    I just can't get the GUI to load to set it up fully.  Screenshot of the docker page is attached.  What am I missing?

     

     

    is this with a new blank appdata/pihole directory? try a different name name to make sure (I had issues with permissions from an old installation). Is 192.168.1.99 already in use elsewhere?
    ... thats all I can think of at the moment

    • Thanks 1
  8. 4 hours ago, Andiroo2 said:

    For those that are coming here to troubleshoot a new Pihole docker setup in 2022, the app marked "Official" in Community Apps doesn't yet work on Unraid out of the box.  The template being pulled from docker has changed and the Unraid template hasn't been updated to use the new/correct variables yet.  There are some changes listed in the thread here that may get it working for you, but for now, don't pull your hair out if it's not working out of the box.

     

    If I'm wrong, please delete this post or flag it...I'm not a spokesperson for this docker template...just someone that has pulled some hair out and now (I think?) understands where things stand.

     

    I updated it a few days ago - let me know if it doesnt work for you. I tested it on a new adddata directory to be sure.

    I have not added "env. variable 'DNSMASQ_USER' with value = 'root'" in a couple of posts up as this is a temporary docker issue.

  9. 14 hours ago, Gokux said:

    I can confirm that. After starting, the container runs for a few hours and then suddenly hangs in the reboot cycle.
    Funnily enough, if it was switched off for a few hours, I can start it again, but then it only runs again for a few hours.

     

    The template just uses the official PiHole docker - it seems that there is a discussion here that may help https://github.com/pi-hole/docker-pi-hole/issues/922 .

     

    You could also change the docker tag to load a specific version: see here https://hub.docker.com/r/pihole/pihole/tags

     

    I do not use PiHole now as I have adguard installed on my firewall so I cannot test.... But just to repeat - this is the offical docker image and not related to the template itself.

     

  10. On 10/16/2021 at 10:31 PM, CryPt00n said:

    Works for me, many many thanks! Was trying to get it to run with official docker but webcam didn´t worked in my tries. Now i can finally power off my pi. :)

     

    This actually uses the official container - I just updated the template and researched how to get the video drivers working. Glad it is working for you.
    If you use the CA backup application, make sure that it does not turn off the docker (adv settings) or you will lose a long print! 

    • Like 2
  11. On 10/13/2021 at 11:02 AM, Mizz141 said:

    I know of Mearman's docker, however it doesn't contain the mjpg streamer which I need for webcam control, I have tried manual set-up but bricked the container way too many times for it to work. (or I'm just an idiot who can't figure out what settings to use, which probably is the more accurate term to describe my issues)

    I also ran into the same issue when Backups shut-down the docker, you're not alone lol

     

    see here: 

     

  12. I have created a new docker template for Octoprint using the official docker images and supporting webcam streaming.

     

    • You need video drivers installed on unRaid for the kernel to see a camera.
      • (on Version: 6.10.0-rc1) - install DVB Drivers in Community Apps and select LibreELEC
      • This will need a reboot after installation
         
    • plug in your camera, you should see /dev/video0 appear in a terminal session on unRaid
       
    • Install OctoPrint-Spants
      • add the following:
        • variables: 
          • ENABLE_MJPG_STREAMER         true
          • CAMERA_DEV                            /dev/video0
          • MJPG_STREAMER_INPUT           -y -n -r 640x480 (can change to suit)

        • port:

          • webcam           container port 80      host port 5003

          • snapshot          container port 8080  host port 5004

             

    • In octoprint's webcam settings

      • set the stream url to     http://IPADDRESS:5003/webcam/?action=stream and test - it should work

      • set the snapshot url to       http://IPADDRESS:5004/?action=snapshot and test

      • IPADDRESS is your unraid server address if you used bridge networking

     

    octosettings.thumb.png.bbdf0a18012214934f908edb8a5854d1.png

    • Like 1
    • Thanks 2
  13. 14 hours ago, Mizz141 said:

    So I've been using the Octoprint-Docker for quite some time now, but the docker wasn't updated in a long time, when will new updates be pushed to it? Octoprint version 1.7.0 has just been released.

     

    I see that nunofgs hasnt updated his docker - I will try and use a different base docker - stay tuned!.
     

    (I stopped using the docker after a long print was ruined by the backup routine tuning off the docker after 8 hours of printing!. My fault - I should have excluded that docker from switching off. I will investigate a solution) 

     

    @Mizz141 *** I see that Mearman already has a template using the official docker - have you tried that? ***

  14. On 8/23/2021 at 11:08 PM, mrm said:

    Alternatively, I'd be happy to take over managing the template: there are several things I'd suggest changing. What's the friendly protocol for this sort of thing?

     

    (Also: I push :stable releases to :alpha and :beta tags to make sure people don't get left behind)

    Sure, no problem at all. All I did was a quick template as a favour... Happy if you want to release another and I can remove mine.

    • Thanks 2