L0rdRaiden
-
Posts
568 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by L0rdRaiden
-
-
-
Could you please include libxml2 and libxslt python?
It's required to use ONVIF in home assistant
-
18 minutes ago, Ghostman_132 said:
What products (dongle manufacturers) use this chip?
I would say any usb bluetooth 5.0 in aliexpress
-
On 1/2/2021 at 11:45 AM, L0rdRaiden said:
Hello, could you please add the firmware of this Bluetooth chip
https://linuxreviews.org/Realtek_RTL8761B
https://aur.archlinux.org/packages/rtl8761b-fw/
It is probably the most (if not the only one) bluetooth chip used in usb dongles that supports bluetooth 5.0
Could you please include this binary? Is the most common chip for usb dongles with bluetooth 5
Jan 22 13:28:51 Unraid kernel: usbcore: registered new interface driver btusb
Jan 22 13:28:51 Unraid kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
Jan 22 13:28:51 Unraid kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1
Jan 22 13:28:51 Unraid kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761b_fw.bin
Jan 22 13:28:51 Unraid kernel: bluetooth hci0: Direct firmware load for rtl_bt/rtl8761b_fw.bin failed with error -2Jan 22 13:28:51 Unraid kernel: Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8761b_fw.bin not found
-
7 minutes ago, GuildDarts said:
Update
- Added: preview icon-basic
- Fixed: long folder names
- Fixed: docker/vm renaming
@L0rdRaiden Sorry that i took a bit over 2 weeks to fix, and thanks for figuring out that it was renaming that caused the issueThanks to you for the plugin, you fixed it quickly actually
-
same problem here, any idea why or how to fix it?
Jan 15 04:05:31 Unraid kernel: veth4887b23: renamed from eth0
Jan 15 04:05:31 Unraid Docker Auto Update: Stopping Jackett
Jan 15 04:05:34 Unraid kernel: vetha26d5ab: renamed from eth0
Jan 15 04:05:34 Unraid Docker Auto Update: Stopping Netdata
Jan 15 04:05:35 Unraid kernel: traps: PLUGIN[cgroups][29812] general protection fault ip:14cf812a1786 sp:14cf804eb5a0 error:0 in ld-musl-x86_64.so.1[14cf8129a000+47000]
Jan 15 04:05:35 Unraid kernel: veth6a26d45: renamed from eth0
Jan 15 04:05:35 Unraid Docker Auto Update: Installing Updates for ruTorrent Sonarr Jackett Netdata
Jan 15 04:06:12 Unraid Docker Auto Update: Restarting ruTorrent
Jan 15 04:06:13 Unraid kernel: eth0: renamed from vethbdec3b7
Jan 15 04:06:13 Unraid Docker Auto Update: Restarting Sonarr -
On 1/4/2021 at 1:47 AM, GuildDarts said:
Try and edit /boot/config/plugins/docker.folder/folders.json then find the tools folder and under children remove the one thats not showing.
you could also remake the folder. The bug that makes this happen should be fixed so should not happen again
a small heads up it might be a bit before i can fix the two issues as my laptop is currently broken so i cant really edit the plugin
I think the error happens when you change the name of a docker already in the folder, the plugin keeps both names.
-
How can I make mine looks like this one
Mine is like this I still have the label tab view on the dockers
On the other hand with the label tab view when the name of the folder is "large" it mess up everything, there could be an option to change the size of the text to have a perfect fit
And there is a bug it shows 4/10 but I only have 9 dockers in this folder
-
On 12/24/2020 at 4:48 PM, Barny said:
I was having the same issues as mentioned in this post - I know its a bit old now but I've only recently become a user of UnRAID.
I re-packaged the sorccu container with a script which will connect to the androidtv/firetv devices automatically and attempt to keep them connected. Its nothing fancy but it works for me.
Its here if it will help anyone else with these issues: https://hub.docker.com/r/barnybbb/adb-hass-androidtv
Thanks,
Barny.
Thanks a lot Barny for sharing this.
You should make a template and publish it in unraid community apps so more people will find it
-
On 5/27/2020 at 7:07 PM, SpaceInvaderOne said:
This container needs a ConbeeII usb zigbee stick to work
This container is for the deCONZ software from Dresden Elektronik. It is used to control a conbee zigbee usb stick and can be used with home assistant.
Setup.
1. Without conbee usb stick plugged into the server run the following command in a terminal window
ls /dev/
2. Plug your conbee usb stick into the unraid server. Then run the above again. You will now see an extra device here. This is your conbee zigbee stick.
Most likely ttyACM0 (unless you have maybe a zwave stick plugged in aswell then it might not be)
3. Now add the name of the stick to the template. (default is already ttyACM0)
Add it to both usb conbee: and usb device name:
4. I think it best to set a static ip for the container. You can then access the container from http://xxx.xxx.xxx.xxx (the ip you set)
5. Now you can add your zigbee devices in the webui and connect deconz to home assistant for it to be able to access you zigbee devices.
Does the conbee II work with home assistant docker and ZHA? without deconz?
Or deconz docker has some kind of drivers or something to make conbee work?
-
Hello, I was wondering if I will have any problem using Conbee on unraid with home assistant docker using ZHA instead of DeCONZ.
Does unraid has the drivers to make Conbee work? or will only work with DeCONZ docker because the docker itself has the drivers?
What if I use zigbee2mqtt docker instead ZHA in Home Assistant?
Thanks in advance
-
On 5/29/2020 at 5:24 AM, dedi said:
I have a CSR Bluetooth dongle (Cambridge Silicon Radio Bluetooth Dongle) that I want to pass trough to a Home Assistant VM, I can select it in the VM config but hassos does not find the device there,
Is that because firmware for CSR BT dongles are missing?On 9/9/2020 at 4:31 AM, David Puziol Prata said:I have the same problem. Have you found a solution? I was reading about fake CSR and that it was necessary to recompile the Linux source code module. I can't give an UP on hci0 and it just stays on DOWN with the error Can't init device hci0: Operation not supported (95)
The problem is hassio, it doesn't support bluetooh usb stick, the only bluetooth that supports is the on in raspberry pi.
-
Hello, could you please add the firmware of this Bluetooth chip
https://linuxreviews.org/Realtek_RTL8761B
https://aur.archlinux.org/packages/rtl8761b-fw/
It is probably the most (if not the only one) bluetooth chip used in usb dongles that supports bluetooth 5.0
-
look at the cpu when your run it, it's max out?
-
-
14 minutes ago, pras1011 said:
Thanks. But I cant find it. Please can you tell me where it is?
Sent from my SM-G977B using Tapatalk
-
2 minutes ago, pras1011 said:
Does this error cause an issue with the server?
Not that I notice, but i didn't like it xD.
If you know how in 30 mins you can do a fresh install by just keeping some config file from the flash. In the wiki there is an explanation for all the config files.
-
4 minutes ago, pras1011 said:
I am having the same error on my syslog. Is this a problem? Can it be ignored? Did you fix it?
I did an almost fresh install to solve it
-
Any news?
-
Can someone please help me here? it shouln't be that hard for someone with a little bit of knowledge around linux. I have spent hours googling I have tried everything but still can not solve this issue
-
For some reason when I reboot unraid move the time 2 hours forward.
Look at the date command, it resolves ok, the others are wrong? how can I fix this?
I have removed the drift file from the flash but might not be related, and for some reason NTP is not re-creating the file
Aug 3 20:55:56 Unraid root: Stopping NTP daemon... Aug 3 20:55:57 Unraid ntpd[18975]: ntpd [email protected] Tue Jun 23 18:44:10 UTC 2020 (1): Starting Aug 3 20:55:57 Unraid ntpd[18975]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Aug 3 20:55:57 Unraid ntpd[18975]: ---------------------------------------------------- Aug 3 20:55:57 Unraid ntpd[18975]: ntp-4 is maintained by Network Time Foundation, Aug 3 20:55:57 Unraid ntpd[18975]: Inc. (NTF), a non-profit 501(c)(3) public-benefit Aug 3 20:55:57 Unraid ntpd[18975]: corporation. Support and training for ntp-4 are Aug 3 20:55:57 Unraid ntpd[18975]: available at https://www.nwtime.org/support Aug 3 20:55:57 Unraid ntpd[18975]: ---------------------------------------------------- Aug 3 20:55:57 Unraid ntpd[18977]: proto: precision = 0.080 usec (-23) Aug 3 20:55:57 Unraid ntpd[18977]: basedate set to 2020-06-11 Aug 3 20:55:57 Unraid ntpd[18977]: gps base set to 2020-06-14 (week 2110) Aug 3 20:55:57 Unraid ntpd[18977]: Listen normally on 0 lo 127.0.0.1:123 Aug 3 20:55:57 Unraid ntpd[18977]: Listen normally on 1 br0 192.168.1.200:123 Aug 3 20:55:57 Unraid ntpd[18977]: Listen normally on 2 lo [::1]:123 Aug 3 20:55:57 Unraid ntpd[18977]: Listening on routing socket on fd #19 for interface updates Aug 3 20:55:57 Unraid ntpd[18977]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Aug 3 20:55:57 Unraid ntpd[18977]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Aug 3 20:55:57 Unraid root: Starting NTP daemon: /usr/sbin/ntpd -g -u ntp:ntp Aug 3 20:56:00 Unraid crond[2106]: time disparity of -119 minutes detected
-
Some more info
NTP conf file
# Sample /etc/ntp.conf: Configuration file for ntpd. # # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. The # default stratum is usually 3, but in this case we elect to use stratum # 0. Since the server line does not have the prefer keyword, this driver # is never used for synchronization, unless no other other # synchronization source is available. In case the local host is # controlled by some external source, such as an external oscillator or # another protocol, the prefer keyword would cause the local host to # disregard all other synchronization sources, unless the kernel # modifications are in use and declare an unsynchronized condition. # server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 10 # # NTP server (list one or more) to synchronize with: #server 0.pool.ntp.org iburst #server 1.pool.ntp.org iburst #server 2.pool.ntp.org iburst #server 3.pool.ntp.org iburst # # Full path of a directory where statistics files should be created # statsdir /var/lib/ntp/stats # # Location of an alternate log file to be used instead of the default system syslog(3) facility # #logfile /var/log/ntp # # Drift file. Put this in a directory which the daemon can write to. # No symbolic links allowed, either, since the daemon updates the file # by creating a temporary in the same directory and then rename()'ing # it to the file. # driftfile /var/lib/ntp/drift # # Location of PID file # pidfile /var/run/ntpd.pid # # Uncomment to use a multicast NTP server on the local subnet: #multicastclient 224.0.1.1 # listen on default 224.0.1.1 # Set an optional compensation for broadcast packet delay: #broadcastdelay 0.008 # # Keys file. If you want to diddle your server at run time, make a # keys file (mode 640 owned by root:ntp) and define the key number to # be used for making requests. # PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote # systems might be able to reset your clock at will. # #keysdir /etc #keys /etc/ntp.keys #trustedkey 65535 #requestkey 65535 #controlkey 65535 # # Don't serve time or stats to anyone else by default (more secure) restrict default limited kod nomodify notrap nopeer noquery restrict -6 default limited kod nomodify notrap nopeer noquery # # Use these lines instead if you do want to serve time and stats to # other machines on the network: #restrict default limited kod nomodify notrap nopeer #restrict -6 default limited kod nomodify notrap nopeer # # Trust ourselves. :-) restrict 127.0.0.1 restrict ::1 # Generated entries follow: interface ignore wildcard interface listen br0 server time1.google.com iburst server time2.google.com iburst server time3.google.com iburst
-
I was getting NTP related errors and when I update NTS settings I get this, can someone please help me to find a solution?
It happend after a hard shutdown (electricity went off) but I don't know if it's related.
Jul 28 18:44:14 Unraid ntpd[2010]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Jul 28 18:44:15 Unraid ntpd[2010]: frequency error 2004 PPM exceeds tolerance 500 PPM Jul 28 18:46:03 Unraid emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jul 28 18:46:45 Unraid root: Fix Common Problems: Other Warning: Could not perform docker application port tests
Jul 29 17:39:20 Unraid nginx: 2020/07/29 17:39:20 [error] 8729#8729: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. Jul 29 17:39:20 Unraid nginx: 2020/07/29 17:39:20 [error] 8729#8729: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen.
Jul 29 17:44:01 Unraid emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jul 29 17:44:47 Unraid emhttpd: shcmd (96): ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime-copied-from Jul 29 17:44:47 Unraid emhttpd: shcmd (97): cp /etc/localtime-copied-from /etc/localtime Jul 29 17:44:47 Unraid emhttpd: shcmd (98): /usr/local/emhttp/webGui/scripts/update_access Jul 29 17:44:47 Unraid root: sshd: no process found Jul 29 17:44:48 Unraid emhttpd: shcmd (99): /etc/rc.d/rc.ntpd restart Jul 29 17:44:48 Unraid ntpd[21257]: ntpd exiting on signal 1 (Hangup) Jul 29 17:44:48 Unraid ntpd[21257]: 127.127.1.0 local addr 127.0.0.1 -> <null> Jul 29 17:44:48 Unraid root: Stopping NTP daemon... Jul 29 17:44:49 Unraid ntpd[22061]: ntpd [email protected] Tue Jun 23 18:44:10 UTC 2020 (1): Starting Jul 29 17:44:49 Unraid ntpd[22061]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Jul 29 17:44:49 Unraid ntpd[22061]: ---------------------------------------------------- Jul 29 17:44:49 Unraid ntpd[22061]: ntp-4 is maintained by Network Time Foundation, Jul 29 17:44:49 Unraid ntpd[22061]: Inc. (NTF), a non-profit 501(c)(3) public-benefit Jul 29 17:44:49 Unraid ntpd[22061]: corporation. Support and training for ntp-4 are Jul 29 17:44:49 Unraid ntpd[22061]: available at https://www.nwtime.org/support Jul 29 17:44:49 Unraid ntpd[22061]: ---------------------------------------------------- Jul 29 17:44:49 Unraid ntpd[22063]: proto: precision = 0.050 usec (-24) Jul 29 17:44:49 Unraid ntpd[22063]: line 86 column 14 syntax error, unexpected T_String, expecting T_EOC Jul 29 17:44:49 Unraid ntpd[22063]: syntax error in /etc/ntp.conf line 86, column 14 Jul 29 17:44:49 Unraid ntpd[22063]: line 87 column 14 syntax error, unexpected T_String, expecting T_EOC Jul 29 17:44:49 Unraid ntpd[22063]: syntax error in /etc/ntp.conf line 87, column 14 Jul 29 17:44:49 Unraid ntpd[22063]: line 88 column 14 syntax error, unexpected T_String, expecting T_EOC Jul 29 17:44:49 Unraid ntpd[22063]: syntax error in /etc/ntp.conf line 88, column 14 Jul 29 17:44:49 Unraid ntpd[22063]: line 89 column 14 syntax error, unexpected T_String, expecting T_EOC Jul 29 17:44:49 Unraid ntpd[22063]: syntax error in /etc/ntp.conf line 89, column 14 Jul 29 17:44:49 Unraid ntpd[22063]: basedate set to 2020-06-11 Jul 29 17:44:49 Unraid ntpd[22063]: gps base set to 2020-06-14 (week 2110) Jul 29 17:44:49 Unraid ntpd[22063]: Listen normally on 0 lo 127.0.0.1:123 Jul 29 17:44:49 Unraid ntpd[22063]: Listen normally on 1 br0 192.168.1.200:123 Jul 29 17:44:49 Unraid ntpd[22063]: Listen normally on 2 lo [::1]:123 Jul 29 17:44:49 Unraid ntpd[22063]: Listening on routing socket on fd #19 for interface updates Jul 29 17:44:49 Unraid ntpd[22063]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Jul 29 17:44:49 Unraid ntpd[22063]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Jul 29 17:44:49 Unraid root: Starting NTP daemon: /usr/sbin/ntpd -g -u ntp:ntp
Jul 29 17:54:21 Unraid smbd[25083]: [2020/07/29 17:54:21.267529, 0] ../../lib/param/loadparm.c:415(lp_bool) Jul 29 17:54:21 Unraid smbd[25083]: lp_bool(no): value is not boolean! Jul 29 17:54:24 Unraid smbd[25083]: [2020/07/29 17:54:24.237445, 0] ../../lib/param/loadparm.c:415(lp_bool) Jul 29 17:54:24 Unraid smbd[25083]: lp_bool(no): value is not boolean! Jul 29 17:54:24 Unraid smbd[25083]: [2020/07/29 17:54:24.253927, 0] ../../lib/param/loadparm.c:415(lp_bool) Jul 29 17:54:24 Unraid smbd[25083]: lp_bool(no): value is not boolean! Jul 29 17:54:24 Unraid smbd[25083]: [2020/07/29 17:54:24.272429, 0] ../../lib/param/loadparm.c:415(lp_bool) Jul 29 17:54:24 Unraid smbd[25083]: lp_bool(no): value is not boolean! Jul 29 17:54:25 Unraid smbd[25083]: [2020/07/29 17:54:25.691188, 0] ../../lib/param/loadparm.c:415(lp_bool) Jul 29 17:54:25 Unraid smbd[25083]: lp_bool(no): value is not boolean! Jul 29 18:00:41 Unraid kernel: kvm: already loaded the other module
-
See this please
I am using Version: 6.9.0-beta25
I
unRAID 6 NerdPack - CLI tools (iftop, iotop, screen, kbd, etc.)
in Plugin Support
Posted · Edited by L0rdRaiden
Not 100%, but in home assistant you dont have a package manager to install anything and home assistant always run on docker, no matter which version you use, core, HA OS, etc.
So I guess if the documentation says this:
It must be a requirement of the host OS, not the docker.
To have all the functionality it will also require ffmpeg binary
https://www.home-assistant.io/integrations/ffmpeg/
This? https://packages.slackware.com/?r=slackware-current&p=ffmpeg-4.3.1-i586-2.txz
For example here you have someone trying to install similar packages in the host OS to get other integrations to work
https://community.home-assistant.io/t/installation-of-fritz-box-net-monitor-does-not-work/90775
https://community.home-assistant.io/t/honeywell-total-connect-in-docker/146898