gonzilla

Thank you, I added that command, and from the logs I can see it being installed but I get the exact same error. I consoled in and entered the commands below to see if lidfdk-aac was enabled in ffmpeg ffmpeg -buildconf --enable-libfdk-aac I get "--enable-libfdk-aac: not found" After some reading I think the problem is ffmpeg needs to be compiled with libfdk-aac included, but I have no idea how to do that. https://github.com/dgreif/ring/wiki/FFmpeg#homebridge-audio-support https://github.com/nicholasrobinson/ffmpeg-homebridge Any suggestions? Not sure how difficult it is to incorporate that into your docker. Thanks!

I can't get it to work. How do I do that?

Hi @Siwat2545, I'm using the Ring plugin with your HomeBridge docker, video works but I have no audio, I'm seeing the message below in the logs. [Ring] Streaming video only - found ffmpeg, but libfdk_aac is not installed. Do you know if there's a way to get libfdk_aac installed/enabled with your docker? Thanks!

Thank you, trying it now.

Don't I have to be in maintenance mode first to run a filesystem check? How do I do that without access to the GUI?

Last week I performed what seemed to be a routing upgrade to 6.2.3 from (I think 6.2.2), after the restart I was unable to access the GUI and none of my disk/shares are mounting. I ran a memtest (checked ok), booted to safe mode, downgraded to an older version, upgraded to 6.2.4, nothing seems to work. I did manage to see some errors related to disk 4, I checked the cables, replaced them, and finally completely disconnected the drive. However I still can't get to the GUI or get any shares visible besides the flash drive itself. I've attached my diagnostics log, could someone please take a look and help shed some light as to the root cause? Thanks! tower-diagnostics-20161107-1537.zip

Trying to use this with SmartThings, I managed to get this running. From the logs I can see that it loads my SmartThings accessories and says it's running on port 51826, however on my iOS device it doesn't find any accessories from homebridge. Is there a step I'm missing so that devices can be discovered properly (port/variables/path, etc)?

Electric, were you able to get this working?

Thanks for the suggestion. I would consider that option, however with each camera requiring it's own unique share, dedicating a physical drive for every camera is a showstopper unfortunately.

Exact same issue here also with Hikvision cameras, would be really nice if we had the ability to either have user quotas or the ability to customize a user share reported volume size (regardless of the physical disk size used).

Well that was fun (not!)...I managed to solve it. After intensive googling, I found some obscure reference to a bug describing my problem exactly (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/128315). So I dug up my mobo manual and changed the jumpers for my USB ports from S1 (default) to S3 wakeup mode...and voila, my server sleeps and resumes from a magic packet perfectly! If anyone runs into this issue, this is probably the culprit if everything else has been done correctly.

The BIOS is set to wake on PCI events only, in fact even if I disable that...it's still resumes from sleep immediately. Does the syslog I attached indicate the reason from resuming? I can't make any sense of the event that triggered it.

root@Tower:~# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pg Wake-on: g Current message level: 0x00000037 (55) Link detected: yes

I don't remember doing that, but I've managed to get ACPI enabled by entering ACPI=ON in my syslinux.cfg and now I can enter S3 sleep, but only for a few seconds. The server almost immediately resumes from sleeping! Any ideas what could be causing it? I've tried just about every setting in the BIOS. I've attached a new log, I can't figure this out...sooo frustrating. syslog-2011-02-02.zip