MothyTim

Members
  • Posts

    215
  • Joined

  • Last visited

Everything posted by MothyTim

  1. Hi, I'm also getting this error: Fatal error: Cannot redeclare _() (previously declared in /usr/local/emhttp/plugins/parity.check.tuning/Legacy.php:6) in /usr/local/emhttp/plugins/dynamix/include/Translations.php on line 20 But I have just upgraded my parity drive to a larger one! Everything seems to be working though and I've tried removing and reinstalling the plugin. I'm running Unraid 6.10.0rc1. Cheers, Tim
  2. Ok weird! Attached a new one! tower-diagnostics-20210901-1606.zip
  3. Server just crashed, don’t know why! It’s 10 at night and was watching something on Plex when it just stopped playing, I checked and nothing was reachable! So I went into the office and tried to shut down via command line using the monitor and keyboard but that was frozen too, so had to hit the oh shit button! Attached diagnostics so maybe you can see what happened? tower-diagnostics-20210831-2238.zip
  4. Hi, I'm using Authelia and everything works as it should. I have a problem with LMS, I only proxied it to use Alexa skill and wanted to use Authelia instead of basic auth, but it seems Alexa can't/won't use 2-factor auth for this skill! Can I set somewhere in the config to use single-factor just for this container? Thanks, Tim
  5. Hi, hoping for some help with my config! All seems to work, I have recording 24/7 and clips when it detects. Intel gpu is working and using cpu at the moment for object detection (Coral USB on order). I only want it to detect people which it does about half the time, which is disappointing and I get constant false positives! At night it doesn't detect anything at all, I can stand in front of the camera and wave, nothing! Will the Coral improve this? Camera is S3VC 5mp super HD. Here's my config, please let me know if anything could be changed? Thanks, Tim mqtt: # Required: host name host: 192.168.xxx.xxx # Optional: port (default: shown below) port: 1883 # Optional: topic prefix (default: shown below) # WARNING: must be unique if you are running multiple instances topic_prefix: frigate # Optional: client id (default: shown below) # WARNING: must be unique if you are running multiple instances client_id: frigate # Optional: user user: XXXXXXXXXX # Optional: password # NOTE: Environment variables that begin with 'FRIGATE_' may be referenced in {}. # eg. password: '{FRIGATE_MQTT_PASSWORD}' password: XXXXXXXXXX # Optional: interval in seconds for publishing stats (default: shown below) stats_interval: 60 cameras: # Required: name of the camera garden: # Required: ffmpeg settings for the camera ffmpeg: # Required: A list of input streams for the camera. See documentation for more information. inputs: # Required: the path to the stream # NOTE: Environment variables that begin with 'FRIGATE_' may be referenced in {} - path: rtsp://XXXXX:XXXXXXXX@192.168.xxx.xxx:554/stream1 # Required: list of roles for this stream. valid values are: detect,record,clips,rtmp # NOTICE: In addition to assigning the record, clips, and rtmp roles, # they must also be enabled in the camera config. roles: - detect - record - path: rtsp://XXXXX:XXXXXXXX@192.168.xxx.xxx:554/stream0 roles: - clips - rtmp # Required: width of the frame for the input with the detect role width: 704 # Required: height of the frame for the input with the detect role height: 576 # Optional: desired fps for your camera for the input with the detect role # NOTE: Recommended value of 5. Ideally, try and reduce your FPS on the camera. # Frigate will attempt to autodetect if not specified. fps: 5 # Optional: camera level motion config motion: # Optional: motion mask # NOTE: see docs for more detailed info on creating masks mask: 446,370,428,576,0,576,0,296,232,259,255,359 # Optional: timeout for highest scoring image before allowing it # to be replaced by a newer image. (default: shown below) best_image_timeout: 60 # Optional: zones for this camera zones: # Required: name of the zone # NOTE: This must be different than any camera names, but can match with another zone on another # camera. path: # Required: List of x,y coordinates to define the polygon of the zone. # NOTE: Coordinates can be generated at https://www.image-map.net/ coordinates: 545,1077,747,939,788,805 # Optional: Zone level object filters. # NOTE: The global and camera filters are applied upstream. filters: person: min_area: 5000 max_area: 100000 threshold: 0.7 # Optional: Camera level detect settings detect: # Optional: enables detection for the camera (default: True) # This value can be set via MQTT and will be updated in startup based on retained value enabled: True # Optional: Number of frames without a detection before frigate considers an object to be gone. (default: 5x the frame rate) max_disappeared: 25 # Optional: save clips configuration clips: # Required: enables clips for the camera (default: shown below) # This value can be set via MQTT and will be updated in startup based on retained value enabled: True # Optional: Number of seconds before the event to include in the clips (default: shown below) pre_capture: 10 # Optional: Number of seconds after the event to include in the clips (default: shown below) post_capture: 10 # Optional: Objects to save clips for. (default: all tracked objects) objects: - person # Optional: Restrict clips to objects that entered any of the listed zones (default: no required zones) required_zones: [] # Optional: Camera override for retention settings (default: global values) retain: # Required: Default retention days (default: shown below) default: 60 # Optional: Per object retention days objects: person: 90 # Optional: 24/7 recording configuration record: # Optional: Enable recording (default: global setting) enabled: True # Optional: Number of days to retain (default: global setting) retain_days: 30 # Optional: RTMP re-stream configuration rtmp: # Required: Enable the live stream (default: True) enabled: True # Optional: Configuration for the jpg snapshots written to the clips directory for each event snapshots: # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below) # This value can be set via MQTT and will be updated in startup based on retained value enabled: True # Optional: print a timestamp on the snapshots (default: shown below) timestamp: False # Optional: draw bounding box on the snapshots (default: shown below) bounding_box: False # Optional: crop the snapshot (default: shown below) crop: False # Optional: height to resize the snapshot to (default: original size) height: 175 # Optional: Restrict snapshots to objects that entered any of the listed zones (default: no required zones) required_zones: [] # Optional: Camera override for retention settings (default: global values) retain: # Required: Default retention days (default: shown below) default: 10 # Optional: Per object retention days objects: person: 15 # Optional: Configuration for the jpg snapshots published via MQTT mqtt: # Optional: Enable publishing snapshot via mqtt for camera (default: shown below) # NOTE: Only applies to publishing image data to MQTT via 'frigate/<camera_name>/<object_name>/snapshot'. # All other messages will still be published. enabled: True # Optional: print a timestamp on the snapshots (default: shown below) timestamp: True # Optional: draw bounding box on the snapshots (default: shown below) bounding_box: True # Optional: crop the snapshot (default: shown below) crop: True # Optional: height to resize the snapshot to (default: shown below) height: 270 # Optional: Restrict mqtt messages to objects that entered any of the listed zones (default: no required zones) required_zones: [] # Optional: Camera level object filters config. objects: track: - person # Optional: mask to prevent all object types from being detected in certain areas (default: no mask) # Checks based on the bottom center of the bounding box of the object. # NOTE: This mask is COMBINED with the object type specific mask below mask: 0,0,1000,0,1000,200,0,200 filters: person: min_area: 5000 max_area: 100000 min_score: 0.5 threshold: 0.7 # Optional: mask to prevent this object type from being detected in certain areas (default: no mask) # Checks based on the bottom center of the bounding box of the object mask: 0,295,234,258,251,359,454,373,434,576,0,576 detectors: cpu1: type: cpu cpu2: type: cpu clips: # Optional: Maximum length of time to retain video during long events. (default: shown below) # NOTE: If an object is being tracked for longer than this amount of time, the cache # will begin to expire and the resulting clip will be the last x seconds of the event. max_seconds: 600 # Optional: Retention settings for clips (default: shown below) retain: # Required: Default retention days (default: shown below) default: 60 # Optional: Per object retention days objects: person: 90 ffmpeg: # Optional: global ffmpeg args (default: shown below) global_args: -hide_banner -loglevel warning # Optional: global hwaccel args (default: shown below) # NOTE: See hardware acceleration docs for your specific device hwaccel_args: - -hwaccel - vaapi - -hwaccel_device - /dev/dri/renderD128 - -hwaccel_output_format - yuv420p # Optional: global input args (default: shown below) input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1 # Optional: global output args output_args: # Optional: output args for detect streams (default: shown below) detect: -f rawvideo -pix_fmt yuv420p # Optional: output args for record streams (default: shown below) record: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an # Optional: output args for clips streams (default: shown below) clips: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an # Optional: output args for rtmp streams (default: shown below) rtmp: -c copy -f flv objects: # Optional: list of objects to track from labelmap.txt (default: shown below) track: - person # Optional: filters to reduce false positives for specific object types filters: person: # Optional: minimum width*height of the bounding box for the detected object (default: 0) min_area: 5000 # Optional: maximum width*height of the bounding box for the detected object (default: 24000000) max_area: 100000 # Optional: minimum score for the object to initiate tracking (default: shown below) min_score: 0.5 # Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below) threshold: 0.7
  6. Oh ok, thanks for clarifying! Also thanks for all you do, providing these excellent containers!
  7. It’s also showing here? So a bit puzzled!
  8. Oh, strange because I’m seeing this in Lidarr settings?
  9. Is this docker going to be updated anymore? As I see there has been a new version of Lidarr available for a while now? Cheers, Tim
  10. Of course! Just it was a few pages back on the thread and didn't want it forgotten!
  11. Just bumping this hoping someones got an answer? Cheers, Tim
  12. Hi, autofan has stopped working after upgrading to 6.9.1 it was working fine in 6.9.0 and all the betas and RC's. Its annoying as finally my drives spin down and now something else is broken. Not sure what info is needed but I have this in syslinux: acpi_enforce_resources=lax and this in my GO file: modprobe it87 force_id=0x8628 Hopefully someone knows what has changed to stop this working? I have also asked in plugin's page! Cheers, Tim tower-diagnostics-20210312-1429.zip
  13. Hi, autofan has stopped working after upgrading to 6.9.1 it was working fine in 6.9.0 and all the betas and RC's. Its annoying as finally my drives spin down and now something else is broken. Not sure what info is needed but I have this in syslinux: acpi_enforce_resources=lax and this in my GO file: modprobe it87 force_id=0x8628 Hopefully someone knows what has changed to stop this working? Cheers, Tim
  14. Ok, which is exactly how mine was configured! How have you tested it? Have you used console in sonarr/radarr etc to check that they are actually going out through your VPN? If not then you don't actually know! Cheers, Tim
  15. Why is it not accurate?? Privoxy is not working and infact consantly restarts, quite a few others are reporting the same! As Jackett is working fine conected directly through DelugeVPN container not using the proxy, you don't need to use proxy for Radarr/Sonarr etc so have turned it off in both!(Hopefully that is correct?) I have tried turning it on to test privoxy but iplocation still reports as home so privoxy is not working there either! Ignored addresses is just to allow Radarr/Sonarr etc to connect to local network if you're using proxy so not relavant here, but is how it's set in Bazarr! Hoping for a fix soon. Cheers, Tim Forgot my docker run command in last post! root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='proxynet' --privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='********' -e 'VPN_PASS'='*********' -e 'VPN_PROV'='pia' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='10.19.64.0/24' -e 'NAME_SERVERS'='209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -e 'VPN_CLIENT'='wireguard' -e 'ADDITIONAL_PORTS'='9117' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -p '9117:9117/tcp' -v '/mnt/user/Downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 1098a4d6c1e7d3c8e349c7f554c30f3fa1bf4df4f26c3f392be20c23a47c9c0f A more complete log attached: delugevpnlog.rtf
  16. Hi, so a few hours of reading and trying things out leads me to think that privoxy is broken! I've changed Jackett to use the delugeVPN container network so I can switch off proxy in jackett and sonarr/radarr etc meaning they now connect to jackett for indexing ok! And Plex ok! The only container I'm trying to proxy is bazarr, but when I look up location through its console it reports as my home not Toronto like it should? Both DelugeVPN and Jackett report as Toronto! Also in ignored addresses wildcards don't work for me, I have to put the ip address of my server for Bazarr to be able to connect with Sonarr and Radarr! My log shows privoxy restarting all the time. I see others are reporting the same, any idea on the issue? Or is it a bug? Cheers. Tim 2021-03-02 20:48:44,275 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 2021-03-02 20:49:14,451 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2021-03-02 20:49:14,452 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-03-02 20:49:15,470 DEBG 'watchdog-script' stdout output: [info] Privoxy process started 2021-03-02 20:49:15,471 DEBG 'watchdog-script' stdout output: [info] Waiting for Privoxy process to start listening on port 8118... 2021-03-02 20:49:15,479 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 2021-03-02 20:49:45,610 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2021-03-02 20:49:45,611 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-03-02 20:49:46,615 DEBG 'watchdog-script' stdout output: [info] Privoxy process started 2021-03-02 20:49:46,616 DEBG 'watchdog-script' stdout output: [info] Waiting for Privoxy process to start listening on port 8118... 2021-03-02 20:49:46,618 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 2021-03-02 20:50:16,783 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2021-03-02 20:50:16,784 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-03-02 20:50:17,789 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2021-03-02 20:50:17,794 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118
  17. Thanks for that, I'd noticed that occasionally it would scroll but haddn't noticed it was when my finger was on the empty space!
  18. I can't see the rest of your config, have you mapped /var/run/dbus/ ??
  19. Have had very few problems with the beta's since 22, but drives not spinning down issue still not fixed for me! None of my drives have spun down since upgrading from beta 35 to rc1! Was hoping rc2 would fix this! Also Dashboard and Docker page still don't scroll on iPad in Chrome or Safari. But then docker page never has, keep hoping it'll be fixed though! Diagnostics attached. tower-diagnostics-20201221-1416.zip
  20. They say they'll be releasing config files for Wireguard soon! So perhaps thats the way to go?
  21. I would try the Tomato firmware first, freshtomato is currently still updated and gives you all the features that UniFi or pfsense do and won’t cost you any more! If you want better Wi-fi then ubiquity is hard to beat!
  22. Hi, with TP-Link easy smart switches you can’t remove any ports from main vlan, the first table in the screen shot is a bit of a red-herring as nether vlan is selected so the table isn’t showning anything, with vlan 50 only the trunk port and the port connected to server should be untagged the ports to the cameras should be tagged and pvid set to 50. The router with FreshTomato firmware supports vlans and multiple DHCP servers, it’s what I’ve been using for 5 years or so and works well.