G410 Stream still unstable

Aqara Products
,
1

Using firmware 4.5.20_0026.0096 , Latest frigate , latest home assistant.

I purchased an AQARA G410 from RING, basically because i was under the impression it was all local and worked in Home Assistant. Also i wanted a notification on my AppleTV.
Since my purchase i have found increasing paywall activity by AQARA and in retrospect i should have gone with REOLINK.

The problem is the streaming to frigate/doubletake in home assistant, it works fine in AQARA app of the time. But the feed has been increasingly unstable, so useless to me since 4.5.20_0026.0096.

I see some posts that suggests “sun shining directly” on lens can cause it?? Ridiculous, its a doorbell, anyway I’m in the UK and its in a covered porch( so not much chance of the sun shining directly on lens, lol). The sky seems to be washed out, i have notice (needs better adjustment settings)

Asked for chatGPT help and claude for help reconfiguration of frigate, they help a little, then i get “no frames received” error message. So i think its the stream itself. Why offer the streaming, if its unusable.

I’m very disappointed with this device, as you can tell. Nearly had enough.

Anybody had any joy with REOLINK POE?

1 Like
2

Hi there, it looks like you’re experiencing a support-related issue. We’ve automatically created a support ticket for you and will reach out via the forum email within the next two business days.

If other members have any suggestions or insights on this topic, feel free to share!

3

Ok, many hours later.

It was getting worse, delayed doorbell notifications etc

  • I stopped frigate and doubletake. And stopped them starting on boot, turned off watchdog.
  • Removed the Generic Camera from the integration
  • Rebooted HA Host dedicated device

Generic Camera would not connect.

  • hard reset both the camera and ringer( although it might not have worked with the camera because its wired and has got batteries for backup in)
  • Checked the Stream was working in VLC – Yay!
  • Re-added the Generic Camera – Yay!
  • Started frigate and doubletake – Yay!

Many Moons ago, when i first set it up, i recall having some problems with the Generic Camera integration. The preview after the connection was just spinning. But i accepted anyway.

This time the preview appeared? So i can only assume the Generic Camera part was amiss in some way?? Sorry i cannot be more specific on the cause. I don’t know how long it will last? But at the moment its also a lot quicker in showing the stream. So sometimes it seems, nuke it and start again is the fix. Very frustrating.

1 Like
4

Stopped again.
Found that the Aqara app was intermittent at showing live stream as well. Also no memory card playback!! Set to “continuous loop”, also have NAS backup.

Reformatted the card, restarted the device. All working again???

Is it not continuous looping correctly?

Its wired in, can you use the batteries as well or should i take them out?

Just guessing at this point?

5

Im finding the RTSP stream to be very flaky too.

Ive tried VLC, Frigate and now trying scrypted which seems to be more forgiving to the stream errors.

Been in contact with support who said basically bear with due to the Chinese spring festival

6

Because at this point , i cannot seem to fix it, temporary fixes but then get errors. I ran the frigate logs through a Claude AI, results are:

Deeper Problem — RTSP Stream Timestamp Corruption

The situation got worse, not better. The new logs reveal a much more fundamental issue than I initially suggested. Let me break down what’s actually happening.

What the Logs Show

The key new errors are:

  1. bad cseq — The RTSP sequence numbers are jumping wildly (eb55 expected 69ca), meaning RTP packets are arriving completely out of order or the stream is resetting mid-session.
  2. Massive DTS jumps — DTS 2683461663, next:1749717000 — the timestamps jumped backwards by ~933 million ticks on stream 1 (audio). This is a stream-level reset/discontinuity.
  3. Every single audio frame is being dropped — All those invalid dropping st:1 lines are audio packets being discarded because their timestamps are from a completely different epoch.
  4. Corrupt recording segments — The timestamp chaos corrupted the cached .mp4 segment.

Root Cause

Your camera ([IP_address]) is resetting its RTSP stream internally — likely a firmware issue or the camera is renegotiating/restarting the stream without tearing down the RTSP session. The go2rtc relay at 127.0.0.1:8554 passes this corruption straight through.

It gives some fixes but i have tried them before. Use ffmpeg and tcp transport. Drop FPS in camera settings(i couldn’t see any setting in the Aqara app)

I have learned a few things, but still getting errors. Starts OK then reverts to errors. I think next i will remove the ‘Audio’ but we shouldn’t be debugging for Aqara. I may have to give up with this doorbell(thats not true, never give up, never surrender lol).

p.s # Hatton920 They are back from holiday now apparently

1 Like
7

Claude has given up now as well lol

Got rid of the audio settings in frigate, which cleaned the logs for a short while. I think stability is the issue, the network seems strong in app, -44 rssi, doorbell signal says medium-high. No direct sunlight(uk), i think we need to build an ark, its been raining so much.

8

Ok so seems to have stabilised a bit, these are just the camera settings from my frigate if it helps anyone:

go2rtc:
  streams:
    doorbell_camera:
      - rtsp://[username]:[password]@[IP_ address]:8554/ch2
cameras:
  doorbell_camera:
    enabled: true
    mqtt:
      timestamp: false
      bounding_box: false
      crop: true
      quality: 100
      height: 500
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/doorbell_camera
          input_args:
            - -avoid_negative_ts
            - make_zero
            - -fflags
            - +genpts+discardcorrupt
            - -rtsp_transport
            - tcp
            - -timeout
            - '5000000'
            - -analyzeduration
            - '20000000'
            - -probesize
            - '20000000'
            - -r
            - '7'
          roles:
            - record
            - detect
              #- audio


      hwaccel_args: preset-vaapi  # Add this for Intel hardware

also

detect:
  enabled: true
  fps: 7

How long it will be stabilised for??? I marked as the solution but…

1 Like
9

I think it’s a shame that this doorbell isn’t better integrated into Home Assistant, and I really should have known about Reolink sooner because I replaced my G3 with a Reolink and it works perfectly.

10

I agree @EricC . Its an expensive learning curve this hobby. But i’m slowly getting the hang of it :), Home Assistant and must be Local.