fireplex

Members
  • Posts

    160
  • Joined

  • Last visited

Everything posted by fireplex

  1. I am getting "malformed password" in the logs, trying to use DNS-O-Matic, this is my config file: { "settings": [ { "provider": "dnsomatic", "domain": "updates.dnsomatic.com", "host": "@", "username": "something", "password": "something", "ip_version": "ipv4" } ] } Probably something obvious I've done wrong? EDIT: Figured it out, checked your github code for password validation and changed password appropriately. DNS-O-Matic now uses opendns.com login creds and my password was valid for that but not your code
  2. The wiki states "As such, users must either disable this feature on their router or set their router to allow DNS rebinding for the unraid.net domain" However, I notice in my router's logs when unRAID runs the test its trying myunraid.net and NOT unraid.net: Mon May 23 11:12:50 2022 daemon.warn dnsmasq[3712]: possible DNS-rebind attack detected: rebindtest4.myunraid.net So, why is it testing myunraid.net ? Do I need to allow both unraid.net and myunraid.net in my router? Seems a bit unclear to me - can you please improve the docs?
  3. Yes, bizarrely it appears that missing the MQTT username and password in the config.yml caused the problem - once I entered that it started to work again. Why it had previously worked for several weeks before without those entries I do not know...
  4. Yes those icons, I forgot to also post a picture of them. Sorry, which port number? My config file: mqtt: host: 192.168.1.37 # homeassistant #logger: # default: debug detectors: cpu1: type: cpu cpu2: type: cpu # cpu3: # type: cpu # cpu4: # type: cpu cameras: low_drive: ffmpeg: inputs: - path: rtsp://192.168.1.43:554/12 roles: - detect - rtmp - path: rtsp://192.168.1.43:554/11 roles: - record motion: mask: - 0,0,389,0,345,153,0,179 detect: width: 640 height: 352 high_drive: ffmpeg: inputs: - path: rtsp://user:vvv123@192.168.1.44:554/stream2 roles: - detect - rtmp - path: rtsp://user:vvv123@192.168.1.44:554/stream1 roles: - record motion: mask: - 714,720,1280,720,1280,0,1101,0,916,0,911,124,810,169,717,275 detect: width: 640 height: 480 garden: ffmpeg: inputs: - path: rtsp://guest:guest1234@192.168.1.45:554/h264Preview_01_sub roles: - detect - rtmp - path: rtsp://guest:guest1234@192.168.1.45:554/h264Preview_01_main roles: - record motion: mask: - 1280,0,275,0,542,720,1280,720 detect: width: 640 height: 480 shed: ffmpeg: inputs: - path: rtsp://guest:guest@192.168.1.41:80/ch0_1.264 roles: - detect - rtmp - path: rtsp://guest:guest@192.168.1.41:80/ch0_0.264 roles: - record detect: width: 640 height: 360 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 record: # Optional: Enable recording enabled: True # Optional: Number of days to retain retain_days: 7 # # Intel Quick Sync ffmpeg GPU acceleration # ffmpeg: hwaccel_args: - -hwaccel # - qsv # - -qsv_device # - /dev/dri/renderD128 - vaapi - -hwaccel_device - /dev/dri/renderD128 - -hwaccel_output_format - yuv420p
  5. OK thanks, I thought because the toggles on the Web GUI no longer worked it may be an issue with the docker... I have also tried deleting everything on HA, ie removing the integration from HA AND HACS, re-downloading etc and the issue remains. Should I open a new Issue against the HASS integration on github https://github.com/blakeblackshear/frigate-hass-integration ?
  6. For some reason my config has stopped working properly. In the Web GUI provided by the docker I can no longer toggle detect, snapshot or recordings on or off - clicking the icons simply hightlights the buttons and that's it. Also, in Home Assistant multiple entities now report as Unavailable or greyed out: I have tried deleting all my recordings and the appdata, deleting the container and re-downloading and starting from fresh but the problem strangely remains. Any ideas ? The frigate logs seem OK, from a fresh start: 022-01-11 19:58:52] frigate.app INFO : Starting Frigate (0.9.4-26ae608) [2022-01-11 19:58:52] frigate.app INFO : Creating directory: /media/frigate/recordings [2022-01-11 19:58:52] frigate.app INFO : Creating directory: /media/frigate/clips Starting migrations [2022-01-11 19:58:52] peewee_migrate INFO : Starting migrations Migrate "001_create_events_table" [2022-01-11 19:58:52] peewee_migrate INFO : Migrate "001_create_events_table" sql ('CREATE TABLE IF NOT EXISTS "event" ("id" VARCHAR(30) NOT NULL PRIMARY KEY, "label" VARCHAR(20) NOT NULL, "camera" VARCHAR(20) NOT NULL, "start_time" DATETIME NOT NULL, "end_time" DATETIME NOT NULL, "top_score" REAL NOT NULL, "false_positive" INTEGER NOT NULL, "zones" JSON NOT NULL, "thumbnail" TEXT NOT NULL)',) [2022-01-11 19:58:52] peewee_migrate INFO : sql ('CREATE TABLE IF NOT EXISTS "event" ("id" VARCHAR(30) NOT NULL PRIMARY KEY, "label" VARCHAR(20) NOT NULL, "camera" VARCHAR(20) NOT NULL, "start_time" DATETIME NOT NULL, "end_time" DATETIME NOT NULL, "top_score" REAL NOT NULL, "false_positive" INTEGER NOT NULL, "zones" JSON NOT NULL, "thumbnail" TEXT NOT NULL)',) sql ('CREATE INDEX IF NOT EXISTS "event_label" ON "event" ("label")',) [2022-01-11 19:58:52] peewee_migrate INFO : sql ('CREATE INDEX IF NOT EXISTS "event_label" ON "event" ("label")',) sql ('CREATE INDEX IF NOT EXISTS "event_camera" ON "event" ("camera")',) [2022-01-11 19:58:52] peewee_migrate INFO : sql ('CREATE INDEX IF NOT EXISTS "event_camera" ON "event" ("camera")',) Done 001_create_events_table [2022-01-11 19:58:52] peewee_migrate INFO : Done 001_create_events_table Migrate "002_add_clip_snapshot" [2022-01-11 19:58:52] peewee_migrate INFO : Migrate "002_add_clip_snapshot" add_column ('event', 'has_clip', <BooleanField: Event.has_clip>) [2022-01-11 19:58:52] peewee_migrate INFO : add_column ('event', 'has_clip', <BooleanField: Event.has_clip>) add_column ('event', 'has_snapshot', <BooleanField: Event.has_snapshot>) [2022-01-11 19:58:52] peewee_migrate INFO : add_column ('event', 'has_snapshot', <BooleanField: Event.has_snapshot>) Done 002_add_clip_snapshot [2022-01-11 19:58:52] peewee_migrate INFO : Done 002_add_clip_snapshot Migrate "003_create_recordings_table" [2022-01-11 19:58:52] peewee_migrate INFO : Migrate "003_create_recordings_table" Done 003_create_recordings_table [2022-01-11 19:58:52] peewee_migrate INFO : Done 003_create_recordings_table Migrate "004_add_bbox_region_area" [2022-01-11 19:58:52] peewee_migrate INFO : Migrate "004_add_bbox_region_area" add_column ('event', 'region', <JSONField: Event.region>) [2022-01-11 19:58:52] peewee_migrate INFO : add_column ('event', 'region', <JSONField: Event.region>) add_column ('event', 'box', <JSONField: Event.box>) [2022-01-11 19:58:52] peewee_migrate INFO : add_column ('event', 'box', <JSONField: Event.box>) add_column ('event', 'area', <IntegerField: Event.area>) [2022-01-11 19:58:52] peewee_migrate INFO : add_column ('event', 'area', <IntegerField: Event.area>) Done 004_add_bbox_region_area [2022-01-11 19:58:52] peewee_migrate INFO : Done 004_add_bbox_region_area [2022-01-11 19:58:52] frigate.mqtt INFO : MQTT connected [2022-01-11 19:58:52] detector.cpu1 INFO : Starting detection process: 216 [2022-01-11 19:58:52] frigate.edgetpu WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes. [2022-01-11 19:58:52] frigate.app INFO : Output process started: 220 [2022-01-11 19:58:52] frigate.app INFO : Camera processor started for low_drive: 223 [2022-01-11 19:58:52] frigate.app INFO : Camera processor started for high_drive: 225 [2022-01-11 19:58:52] detector.cpu2 INFO : Starting detection process: 218 [2022-01-11 19:58:52] frigate.edgetpu WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes. [2022-01-11 19:58:52] ws4py INFO : Using epoll [2022-01-11 19:58:52] frigate.app INFO : Camera processor started for garden: 226 [2022-01-11 19:58:52] frigate.app INFO : Camera processor started for shed: 228 [2022-01-11 19:58:52] frigate.app INFO : Capture process started for low_drive: 229 [2022-01-11 19:58:52] frigate.app INFO : Capture process started for high_drive: 231 [2022-01-11 19:58:52] frigate.app INFO : Capture process started for garden: 235 [2022-01-11 19:58:52] frigate.app INFO : Capture process started for shed: 239 [2022-01-11 19:58:52] ws4py INFO : Using epoll [2022-01-11 19:58:57] frigate.record WARNING : Discarding a corrupt recording segment: high_drive-20220111194745.mp4 [2022-01-11 19:58:57] frigate.record WARNING : Discarding a corrupt recording segment: shed-20220111194745.mp4 [2022-01-11 19:58:57] frigate.record WARNING : Discarding a corrupt recording segment: garden-20220111194745.mp4 [2022-01-11 19:58:57] frigate.record WARNING : Discarding a corrupt recording segment: low_drive-20220111194745.mp4 [2022-01-11 19:59:51] ws4py INFO : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:50020] [2022-01-11 20:00:51] ws4py INFO : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:50020] [2022-01-11 20:00:57] ws4py INFO : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:40060] [2022-01-11 20:01:03] ws4py INFO : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:40060] [2022-01-11 20:01:42] ws4py INFO : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:51260] [2022-01-11 20:01:43] ws4py INFO : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:41224] [2022-01-11 20:01:46] ws4py INFO : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:41224] [2022-01-11 20:03:48] ws4py INFO : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:51260] Any ideas ?
  7. Just needed to wait a number of hours I think before it started to log data - give it a day then check again.
  8. I have the same issue with i915 driver and Plex HW transcoding causing a complete system hang, the only way I can get the system going again is the HW reset button. I have a Core i5 2390T which supports Quick Sync and I've tried the various methods mentioned previously to try and resolve the issue. For me I can play only a few seconds with Plex reporting HW transcoding then the system freezes, nothing displayed in any logs. I have an i5 2400 so will try that also just to rule out any issue with the CPU. Has anyone on this thread had any more joy with this issue ?
  9. Hi, I installed the system stats plugin a few days ago and the real time function works fine, but if I select last day or any other selection in the drop down I don't get anything displayed. Do I need to carry out some additional work to get this historical data to show ? Thanks!! edit: I don't have a /var/log/sa folder, do I need to manually create that ?
  10. Just to add I've spent a considerable time today trying to figure out why Plex could no longer communicate with tvhproxy, turns out this bug is the reason. I did a reboot of unRAID and all started working again. This should have a priority of Minor at least, not Annoyance as functionality is affected.
  11. Thanks, all working fine now. Love the new look, well done !
  12. Here you go below. Perhaps https://developer.android.com/training/articles/security-config#CleartextTrafficPermitted ? I am running Android 11 on Pixel 3A.
  13. Hi, this is the log as I click the Add button on the app and receive the error message: root@Tower:/var/log# killall controlr root@Tower:/var/log# root@Tower:/var/log# /usr/local/emhttp/plugins/controlr/controlr -port 2378 -certdir /boot/config/ssl/certs -showups I: 2021/07/18 21:01:43 app.go:59: controlr v2021.07.11a|2.23.2 starting ... I: 2021/07/18 21:01:43 app.go:67: No config file specified. Using app defaults ... I: 2021/07/18 21:01:43 app.go:269: cert: found Tower_unraid_bundle.pem I: 2021/07/18 21:01:43 app.go:77: state(&{Name:Tower Timezone:Europe/London Version:6.9.0 CsrfToken:57DC2E997527AA2C Host:http://192.168.1.25:80 Origin:{Protocol:http Host:Tower.local Port:80 Address:192.168.1.25} Secure:false Cert:Tower_unraid_bundle.pem UseSelfCerts:false}) I: 2021/07/18 21:01:43 core.go:81: starting service Core ... I: 2021/07/18 21:01:43 core.go:320: Created system sensor ... I: 2021/07/18 21:01:43 core.go:350: No ups detected ... I: 2021/07/18 21:01:43 server.go:92: Starting service Server ... I: 2021/07/18 21:01:43 server.go:111: Serving files from /usr/local/emhttp/plugins/controlr I: 2021/07/18 21:01:43 server.go:168: Server started listening http on :2378 I: 2021/07/18 21:01:43 api.go:46: Starting service Api ... I: 2021/07/18 21:01:43 api.go:95: Api started listening https on :2382 I: 2021/07/18 21:01:43 app.go:87: Press Ctrl+C to stop ... ⇨ http server started on [::]:2378 ⇨ https server started on [::]:2382 I: 2021/07/18 21:02:13 api.go:167: received /origin {"time":"2021-07-18T21:02:13.817266726+01:00","id":"","remote_ip":"192.168.1.180","host":"192.168.1.25:2382","method":"GET","uri":"/origin","user_agent":"okhttp/3.12.12","status":200,"error":"","latency":135920,"latency_human":"135.92µs","bytes_in":0,"bytes_out":78} I: 2021/07/18 21:02:29 api.go:129: received /info I: 2021/07/18 21:02:29 api.go:137: info({Version:2 Wake:{Mac:70:85:c2:f0:72:99 Broadcast:255.255.255.255} Prefs:{Number:., Unit:C} Samples:[{Key:FAN Value:2795 Unit:rpm Condition:neutral} {Key:BOARD Value:45 Unit:C Condition:neutral} {Key:CPU Value:46 Unit:C Condition:neutral}] Features:map[sleep:false]}) {"time":"2021-07-18T21:02:29.885895642+01:00","id":"","remote_ip":"192.168.1.180","host":"192.168.1.25:2382","method":"GET","uri":"/api/v1/info","user_agent":"okhttp/3.12.12","status":200,"error":"","latency":13157670,"latency_human":"13.15767ms","bytes_in":0,"bytes_out":339}
  14. root@Tower:/var/log# cat /var/local/emhttp/network.ini | grep IPADDR IPADDR:0="192.168.1.25" IPADDR6:0="" root@Tower:/var/log#
  15. root@Tower:~# cat /var/run/nginx.origin http://Tower.local:80 root@Tower:~#
  16. Hi, I've tried a restart and a reinstall of the plugin but still the same issue. I don't use SSL and use port 80 (I'm running 6.9.0) On the GUI I don't see any dockers or VMs:
  17. I can't add my server, keep seeing a weird error as per screenshot.
  18. Just had this same issue with "guest has not initialized the display (yet)", deleting the VM (keeping the image) and re-creating fixed it. Thanks.
  19. Thanks for all your work on this, completely understand. It's been great to use. [emoji106][emoji106][emoji106] Sent from my Pixel 3a using Tapatalk
  20. Excellent thanks. So I presume the 5G just sets the highest amount of memory it can allocate from my total of 32GB, to stop it overwhelming the whole system.
  21. Thanks, the ES is working again for me. I have never adjusted shared memory before so will have to read about that, currently it reports 16% with the 5G default from the template, my server has total 32GB installed.
  22. I did use swag to access zoneminder remotely without use of my VPN for a while, worked ok. Sent from my Pixel 3a using Tapatalk
  23. Thanks, appreciated! Sent from my Pixel 3a using Tapatalk
  24. Well, just gone through this all again several times with complete cleans installs and still get this error: root@ea33b3d5e334:/var/lib/zmeventnotification/bin# sudo -u www-data ./zm_event_start.sh 1 1 Traceback (most recent call last): File "/var/lib/zmeventnotification/bin/zm_detect.py", line 27, in <module> import zmes_hook_helpers.utils as utils ModuleNotFoundError: No module named 'zmes_hook_helpers' Anyone recently done a fresh install of this docker in last few days and got ES working ?