Jump to content

abuhamsa

Members
 View Profile  See their activity

  • Posts

    6

  • Joined

  • Last visited

 Content Type 

Posts posted by abuhamsa

    Host OS Support for Bluetooth Devices

    in Feature Requests

    Posted · Edited by abuhamsa

    On 1/7/2022 at 2:33 PM, ensnare said:

    That worked, I adde the below to my /boot/config/go:

      

    sudo curl -L https://raw.githubusercontent.com/Realtek-OpenSource/android_hardware_realtek/rtk1395/bt/rtkbt/Firmware/BT/rtl8761b_config -o /tmp/rtl8761bu_config.bin
sudo mv /tmp/rtl8761bu_config.bin /lib/firmware/rtl_bt/rtl8761bu_config.bin
sudo curl -L https://raw.githubusercontent.com/Realtek-OpenSource/android_hardware_realtek/rtk1395/bt/rtkbt/Firmware/BT/rtl8761b_fw -o /tmp/rtl8761bu_fw.bin
sudo mv /tmp/rtl8761bu_fw.bin /lib/firmware/rtl_bt/rtl8761bu_fw.bin

     

    However, I have to manually unplug and plug-in the usb dongle so the module reloads. Any way to do this programmatically?

     

    Also, where does the device appear? Trying to pass this through to a Home Assistant container, but can't find it!

     

    This one was the solution for me. I upgraded from 6.9.x to 6.10.2 and my ruuvi collector stopped working.

    adding those drivers did the thing I needed. Have to look in to my flash-backup if I used this workaround before and just forgot about it or if it was something that changed with 6.10.x

     

    Later (if I'm not to busy) I'll make an example of a ruuvicollector container that works.

     

    Edit:

    so here is my solution to use a usb-bluetooth dongle in docker to read ruuvi tags:

    https://github.com/abuhamsa/RuuviCollector

    It is just https://github.com/Scrin/RuuviCollector with an extra start.sh script

     

    I also have an unraid-docker template you have to copy it to 

    /boot/config/plugins/dockerMan/templates-user

     

    The trick is run it with privileged rights and in host networkmode

    [Support] binhex - SABnzbd

    in Docker Containers

    Posted

    52 minutes ago, musicking said:

    I might sound stupid, but where is nzb-notify located in the image?

     

    install_path_nzbnotify="/usr/lib/nzbnotify"  (I'm stupid)

     

    Still get "Notification script returned exit code 1 and output "Traceback (most recent call last): File "/usr/lib/nzbnotify/Notify.py", line 174, in <module> from nzbget import SCRIPT_MODE ModuleNotFoundError: No module named 'nzbget' "

    yeah same here. 

    [Support] binhex - SABnzbd

    in Docker Containers

    Posted

    10 hours ago, keenkreations said:

    My apologies, I ran into this thread while looking for an answer with my dilemma; I think the container image needs to support the extra dependencies for the notification script to work, and I just realized that I am running the linuxserver.io container that they recently updated to allow the notify.py to work correctly.

    I came to the same conclusion.

    Even after i installed the requirements (https://github.com/caronc/nzb-notify/blob/master/requirements.txt) manually, it did not work over the Web-UI. The commandline test did work  

    python sabnzbd-notify.py complete 'Hello' 'World' xbmc://192.168.0.2


     @binhex could you add this feature to the images (normal+vpn)?

    Since sabnzbd is gonna drop support of it's own implementation of diffrent notification types. And they say the official way to get those back is to use said script.

     

    I've also created an issue over github. https://github.com/binhex/arch-sabnzbd/issues/5

     

    Here some links:
    - Sabnzbd Wiki:  https://sabnzbd.org/wiki/configuration/3.5/notifications#nscript

    - nzb-notify Github: https://github.com/caronc/nzb-notify/

    - MergeRequest from Linuxserver Image: https://github.com/linuxserver/docker-sabnzbd/commit/477b9125e102630c5f838dcd37e8b886837100d9

×
×
  • Create New...