cross-posted from: https://lemmy.world/post/15144957

Can anyone help me figure out Frigate/go2rtc

I have two cameras in Frigate.

One is a Raspberry Pi 3 running Monocle server, and this stopped working in Frigate some time back (driveway). The second is a Galayou G7 (nursery). The nursery camera is the one I am concerned about with this post.

Problem: Up until a month or two ago (I must have ran an update but I don't know) the audio from the Galayou camera worked in Home Assistant. I'd like to get that working again. Some searching led me to try setting up go2rtc in my config.

Here is my config before making any changes:

mqtt:
  host: 192.168.1.10
cameras:
  nursery:
    ffmpeg:
      inputs:
        - path: rtsp://redacted:redacted@192.168.1.241:554/live/ch1
          roles:
            - detect
    detect:
      width: 1280
      height: 720
  driveway:
    ffmpeg:
      inputs:
        - path: rtsp://192.168.1.240:554/recording/7824851880350319106/replay?trackid=8836591
          roles:
            - detect
    detect:
      width: 1920
      height: 1080

This currently provides only jsmpeg video in Frigate. If I add something like this to the end:

go2rtc:
  streams:
    nursery:
      - rtsp://redacted:redacted@192.168.1.241:554/live/ch1

this adds mse and webrtc as options in Frigate. But, mse plays only video, no audio. And webrtc loads neither audio nor video. I have tried adding lines like - "ffmpeg:nursery#video=h264#audio=aac" and also with opus but to no avail.

Finally, if I ffplay rtsp://redacted:redacted@192.168.1.241:554/live/ch1 it loads audio/video without a problem. I'm also able to connect via ONVIF at onvif://192.168.1.241:8899 from onvif-gui.

So, something is wrong in my Frigate config, and I don't know what. I'm hoping someone here is a little more familiar and can give me a pointer or two here?

Update: Here is the fix, in case anyone comes across this later:

go2rtc:
  streams:
    nursery:
      - "ffmpeg:rtsp://redacted@192.168.1.241:554/live/ch1#video=copy#audio=copy#audio=opus"
  webrtc:
    candidates:
      - <server-ip>:8555

The webrtc section got webrtc to work in the Frigate and video back in HASS. The #audio=copy#audio=opus got audio working in webrtc.

I have two cameras in Frigate.

One is a Raspberry Pi 3 running Monocle server, and this stopped working in Frigate some time back (driveway). The second is a Galayou G7 (nursery). The nursery camera is the one I am concerned about with this post.

Problem: Up until a month or two ago (I must have ran an update but I don't know) the audio from the Galayou camera worked in Home Assistant. I'd like to get that working again. Some searching led me to try setting up go2rtc in my config.

Here is my config before making any changes:

mqtt:
  host: 192.168.1.10
cameras:
  nursery:
    ffmpeg:
      inputs:
        - path: rtsp://redacted:redacted@192.168.1.241:554/live/ch1
          roles:
            - detect
    detect:
      width: 1280
      height: 720
  driveway:
    ffmpeg:
      inputs:
        - path: rtsp://192.168.1.240:554/recording/7824851880350319106/replay?trackid=8836591
          roles:
            - detect
    detect:
      width: 1920
      height: 1080

This currently provides only jsmpeg video in Frigate. If I add something like this to the end:

go2rtc:
  streams:
    nursery:
      - rtsp://redacted:redacted@192.168.1.241:554/live/ch1

this adds mse and webrtc as options in Frigate. But, mse plays only video, no audio. And webrtc loads neither audio nor video. I have tried adding lines like - "ffmpeg:nursery#video=h264#audio=aac" and also with opus but to no avail.

Finally, if I ffplay rtsp://redacted:redacted@192.168.1.241:554/live/ch1 it loads audio/video without a problem. I'm also able to connect via ONVIF at onvif://192.168.1.241:8899 from onvif-gui.

So, something is wrong in my Frigate config, and I don't know what. I'm hoping someone here is a little more familiar and can give me a pointer or two here?

https://www.amazon.com/dp/B07RR9XBXJ?ref=ppx_yo2ov_dt_b_product_details&th=1

I ordered one of these a few months back.

Then I installed it.

Then I realized that this wasn't the same Zigbee Dimmer switch I was already using elsewhere, and that this wouldn't work for me :)

It's now past the return window for Amazon. I have zero use for this.

tl;dr - Me dumb. If you live in the continental US and want this, I will pay the couple bucks to ship it to you so I can get it off my table.

Here is my problem:

Our TV is connected to a SBC running a GNOME/Wayland desktop, where we watch Jellyfin and sometimes Netflix/Hulu through Firefox.

I'd like to be able to trigger pause/play (space button) from Home Assistant, which is running on my home server.

What I am thinking of would be a server/daemon running on the TV computer that my home server would be able to send keys to via a CLI tool (in this case the space key). I am surprised to find that I cannot locate any program like this.

Can anyone provide any suggestions here?

Other ideas:

• Jellyfin's HA integration doesn't let me pause/play from it, and that still doesn't handle Hulu/Netflix.
• I was able to get this working through SSH and there are tools like ydotool/wtype here that work, but I found waiting for SSH to be a bit slow to connect.

Update: I got frustrated and coded up a solution: https://gitlab.com/neilsimp1/kbsrv

Hi

As the title suggests, I want to set something up so that while trouble is_open(), I have a keyboard shortcut that cycles through the various modes listed at https://github.com/folke/trouble.nvim/tree/main#commands.

I see how I can assign shortcuts to jump directly to the different modes, but I want to remember only one shortcut.

Writing a bit of lua to do this is easy enough, but I can't find any way to see what mode it's currently in, in order to write some function that toggles to the next one.

Is there any way to accomplish this?

Bonus question: Is there any way to get trouble to display on screen what mode it's currently in? Such as at the top or bottom of the trouble panel.

This is probably a stupid question, since 2 > 1, but here goes...

I have a home server. It's a ComputerLINK 1U rack server I bought off eBay some years back. It has 2 CPUs, Intel Xeon E5645 2.4Ghz(https://ark.intel.com/content/www/us/en/ark/products/48768/intel-xeon-processor-e5645-12m-cache-2-40-ghz-5-86-gt-s-intel-qpi.html). It also has two 750W power supplies, but I have one unplugged. It also has RAM and 5 HDDs.

I also have the guts of my old desktop PC. The CPU is an AMD FX8350 4Ghz(https://www.amd.com/en/products/cpu/fx-8350). The motherboard is some ASUS model, I forget and don't want to check right now. A potential PSU would be 500-600W range.

My question: I am considering moving to use my old PC parts as a new home server. One benefit is to cut down on the noise (rack mount PC fans are LOUD). But the real gain I would want is on power savings. So, if RAM and the multiple HDDs all stay the same, but I moved them to the AMD/ASUS CPU/motherboard, can anyone definitively say this will be more power-efficient?

I am not very knowledgeable when it comes to electrics or power consumption, and am just looking for someone to confirm for me. I am aware that the AMD CPU still isn't an excellent choice for an always-on machine, but it could be an improvement.

I have a Scarlett Solo and I have found that with the linux-rt kernel, I get no noticeable latency recording audio, whereas there's a few ms delay on the main linux kernel.

I am able to run other applications and play games just fine on linux-rt. Is there any reason not to just make this my default?

We moved in to our house a couple years ago and were not told too much about a pipe that sticks out of our backyard.

We are on a septic system and this pipe is sticking out from our leech field. The other houses on our block all have similar setups yet none (that I know) have a pipe coming up like ours.

It was suggested to me that this may be safe to remove, or at least remove, cover the whole for a few weeks, and as long as there's no issues, then remove.

It's not attached to anything and I can pretty easily pull it out and put it back in, although I've tended not to touch it much.

Pipe: https://imgur.com/a/yrd6pYN Hole in the ground: https://imgur.com/a/NMXurUH

Can anyone provide any insight here please?

I have about this much left again still to pick too :)

The thing i said in the title