Krypto5

Members
  • Posts

    13
  • Joined

Krypto5's Achievements

Noob

Noob (1/14)

2

Reputation

  1. W with me has been the same problem , it has been more than 1 week that the server crashes every 2 or 3 days of use, and sometimes it still occurs that the dockers stop alone, right now it occurred that the dockers are all showing that they were active , but in fact they were all stopped, I tried to restart the dockers manually and presents error message: Execution Error: Error Code 403 In the error log here appeared this: Mar 19 17:38:11 ROGERSERVER kernel: BTRFS error (device loop2): block=21414051840 write time tree block corruption detected Mar 19 17:38:11 ROGERSERVER kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction) Mar 19 17:38:11 ROGERSERVER kernel: BTRFS info (device loop2: state E): forced readonly Mar 19 17:38:11 ROGERSERVER kernel: BTRFS warning (device loop2: state E): Skipping commit of aborted transaction. Mar 19 17:38:11 ROGERSERVER kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1992: errno=-5 IO failure Mar 19 17:40:30 ROGERSERVER kernel: docker0: port 3(vethed82632) entered disabled state Mar 19 17:40:30 ROGERSERVER kernel: docker0: port 8(veth41669a3) entered disabled state Mar 19 17:40:30 ROGERSERVER kernel: vethb24fb11: renamed from eth0 Mar 19 17:40:30 ROGERSERVER kernel: veth12a7133: renamed from eth0 From what I saw other people here in the forum with the same problem , referring to the CACHE this damaged, a friend of mine who also uses unraid had exactly the same problem, and he had to delete all content from the cache, format and recreate to solve the problem.
  2. Here I used this command: chmod +x /usr/local/bin/cpsumon/cpsumoncli He proceeded to read the information again. When I reset the computer right after updating to version 6.12 the card came without any source information, when executing the command in Terminal everything worked again. I use the Corsair AX1500i font. Thank you for your great work GIGANODE.
  3. As far as I know, this code tells Frigate to record the audio from the cameras in AAC format when the camera doesn't display that audio natively, in my case if I leave the COPY option which is to get the original audio from the camera simply recording no sound, so I have to use - aac so that it converts to that format and saves to the .mp4 file, this is what I understood, I could be wrong.
  4. Your camera is probably the same as mine: Hikvision, I don't know why Hikvision has difficulty enabling the audio of the cameras during recordings or streams, here I constantly end up having problems with crashes, stuttering or simply the audio is disabled for use. What I did to work around the situation was to try to add a few lines in the code for the restream of each camera, the most incredible thing is that I have more than 4 Hikvision camera models in my house and each one I have to use a different configuration so that the Frigate understand and enable the audio, however it turns out that sometimes it works only for recording but it doesn't work live, sometimes the reverse also happens. It's very complicated to be able to adjust the audio of the Hikvision cameras on the Frigate, it's even a question that I was thinking of posting here to see if more people have the same problem and how they solved it, it's probably some FFMPEG command that has to be included to improve compatibility or simply the syntax of the code that should have some more correct order to improve compatibility because I've already done several tests with audio trying to convert to AAC or just using COPY in some options and it works. An example I use here: streams: porteiro: - rtsp://user:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 porteiro_sub: - rtsp://user:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 porteiro: ffmpeg: inputs: - path: rtsp://127.0.0.1:8554/porteiro?video=copy&audio=copy input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/porteiro_sub input_args: preset-rtsp-restream roles: - detect output_args: record: preset-record-generic-audio-aac
  5. I would like to ask for some help, I would greatly appreciate it if you can shed some light on how to solve the problem, I am trying to implement the use of go2rtc in my new version of FRIGATE 0.12.0-DA3E197 PROBLEM: When I entered the information that I didn't have in the old versions to use GO2RTC, the camera image no longer appears in the FRIGATE UI and instead of the image it shows this message: No frames have been received, check error logs In the error log, it accuses the information in the attached photo: Connection refused Below is my config.yml , in this config I am trying to enable only 1 camera, because when I tried with all of them there was a greater chance of giving a problem, syntax, any other error, so I tried with some cameras and finally I am trying only with one to find the problem. All Cameras are Hikvision and to avoid any chance of being the video protocol I chose the camera: PORTEIRO which only uses h.264 in both streams, the other cameras have h.265 for recording and h.264 for detection. CODE FRIGATE.txt
  6. Ah ok thank you, wow what a shame they keep the hours incorrect, I believe it is not something so complex to correct. Thanks.
  7. I am having the same problem as you, at this moment it is 12:20h and the folders that are being generated contain the time of: 15:20h, in short the folders are being generated with an advance of 3 Hours and my UTC is -3:00 São Paulo Brazil , how did you fix this , changed in which part of the system or UNRAID to perform the correction of the time the folders are created, thanks in advance for the help.
  8. CLIPS no longer exist, they were removed from the code in the most current versions, now the clips are already integrated into RECORD See how I currently use RECORD so that it leaves the event recordings (CLIPS in the past) for certain days that I choose. The solution is to remove all that part of the CLIPS code Example: record: enabled: True retain: days: 5 mode: all events: retain: default: 5 mode: motion
  9. Did you manage to add this app to Home Assistant, if so, could you please explain how you did it? I'm new to home assistant and I have an AX1500i that already works correctly in UNRAID, but I wanted to create a CARD in my Home assistant with this information, thank you.
  10. Thank you immensely for your attempt to help, I managed to make the G. CORAL USB work on my server using the UNRAID system, what I did to correct it was to change information within the config.yml file that is located in the frigate/config folder. Basically the G. Coral USB is not identified as long as FRIGATE does not present ZERO ERRORS when the service is started, while the service cannot start google coral continues to appear as unidentified, as long as there is no longer any error in the configuration of the file config.yml the pendrive will be detected and will even change the HARDWARE ID of the pendrive without the need to make any changes to the system, the frigate itself will identify the PEN DRIVE google CORAL with the ID 18d1:9302, I saw several reports of people who were having problems with FRIGATE seeing only the HARDWARE ID as: 1a6e:089a Global Unichip Corp, this actually happens, but it only happens if the command lines in CONFIG.YML still have errors. At least that was my experience with the UNRAID system using the frigate via DOCKER, I don't know if this is replicated for other systems, but here, as soon as the configuration of the config.yml file was completely correct and I restarted the MQTT and FRIGATE service and both were in GREEN status constantly the google flash drive was detected correctly and started to work automatically changing to the ID and recognition form of the GOOGLE CORAL USB flash drive. The correct thing is to analyze all the lines of the FRIGATE LOG and excluding the lines that are showing errors to minimize as much as possible the amount of configurations necessary to load the frigate and start the system. One detail I noticed is that FRIGATE via DOCKER on UNRAID SERVER requires much less configuration in the config.yml because they are already available in DOCKER's EDIT via UNRAID, not being necessary to be declared and configured again in config.yml, below I will list how my CONFIG.YML is currently and now everything works perfectly loading GOOGLE CORAL and identifying all objects perfectly. The biggest problem I faced was to get the FRIGATE service on UNRAID (via DOCKER) to start, it started quickly, turning green in the status, after a few seconds the service was automatically turned off, because there were coding errors in its config.yml file, another detail that I realized that I needed to EDIT the FRIGATE Docker in UNRAID and change its connection type from Bridge to HOST , this way also made it easier for the system to stay online permanently. I'm going to change only the passwords and login part by putting generic values, only in the password I don't know if this is really necessary or mandatory but I followed a pattern that I saw in a documentation where it describes that the password must start with the syntax: FRIGATE_********* (**** enter your password here). I configured the MQTT service password by creating and editing the passwords.txt file inside the MQTT folder and put typeyourusernamehere:FRIGATE_yourpasswordhere , then save the file as passwords.txt and put on directory /MQTT the password will work from this moment on. Then use this same username and password in the config.yml file mqtt: host: 192.168.0.50 user: insert your username here password: FRIGATE_mypasswordhere stats_interval: 5 cameras: doorcam: #camera name ffmpeg: inputs: - path: rtsp://admin:[email protected]:554/Streaming/Channels/101/ snapshots: enabled: true bounding_box: true retain: default: 1 objects: track: - person - bird - cat - dog - motorcycle - bicycle - car zones: zone_0: coordinates: 1280,720,1280,280,0,281,0,720,289,720 detectors: coral: type: edgetpu device: usb Once again, thank you very much for your help, I just have one question left: the organization of the code in relation to the syntax structure must be all organized according to the text above or the config.yml can be edited without spaces and tabs? Is it necessary for each command line to have the exact position to start the text? Thanks and hugs, your software is amazing.
  11. Thank you very much in advance for your help and attention, the prints are below, if that is not what you want, please let me know where I am looking for the information you need, very grateful!
  12. I am not able to make the FRIGATE detect my GOOGLE CORAL USB, for all the attempts I made it always appears written: No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors. What I noticed in some forums was the detail referring to the HARDWARE ID of the pendrive is different from what FRIGATE looks for when it tries to locate a GOOGLE CORAL USB, the ID that is searched for would be the number: 18d1:9302 , since what is detected in my PC (I use UNRAID SERVER system) is the number : 1a6e:089a Global Unichip Corp. How can I make FRIGATE be able to locate the GOOGLE CORAL USB flash drive plugged into the machine? Version Current version: 3.1 Frigate config file mqtt: host: 192.168.0.213 port: 1883 topic_prefix: frigate client_id: frigate user: roger561 password: roger561 stats_interval: 60 detectors: coral: type: edgetpu device: usb database: path: /media/frigate/frigate.db cameras: back: ffmpeg: inputs: - path: rtsp://admin:[email protected]:554/Streaming/Channels/102/ roles: - detect