plugin: [Bug]:T8210: No 2nd Ring notification at Homekit - restart needed .

What happened?

HomeKit doesn’t get notifications When someone presses the ring button on doorbell T8210 Other observations : -Motion sensor events are reported in Homekit - OK -Doorbell ring events work only on 1st trigger after restarting Homebridge

  • reinstall Homebridge , removing , re-adding camera , fresh install of Homebridge and /or plaguing doesn’t solve the issue
  • Conclusion is that the HomeKit notifications only arrive after restarting the HomeBridge

Device Type

Doorbell (Supported)

Plugin Version

v2.0.x (Supported)

HomeBridge Version

v1.6.x (Supported)

NodeJS Version

v18 (Supported)

Operating System

Raspbian 10+ (Supported)

Relevant log output

No log

config

"accessories": [],
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "platform": "config"
        },
        {
            "enableDetailedLogging": false,
            "CameraMaxLivestreamDuration": 230,
            "pollingIntervalMinutes": 1,
            "hkHome": 1,
            "hkAway": 0,
            "hkNight": 3,
            "hkOff": 63,
            "ignoreStations": [],
            "ignoreDevices": [],
            "country": "NL",
            "cameras": [
                {
                    "serialNumber": "T8210P6421440147",
                    "rtsp": false,
                    "enableCamera": true,
                    "videoConfig": {
                        "audio": true,
                        "maxWidth": 640,
                        "maxHeight": 480,
                        "maxFPS": 15,
                        "useSeparateProcesses": true
                    },
                    "talkback": true,
                    "enablePush": true,
                    "refreshSnapshotIntervalMinutes": 5,
                    "immediateRingNotificationWithoutSnapshot": true,
                    "useCachedLocalLivestream": false,
                    "snapshotHandlingMethod": 3
                }
            ],
            "cleanCache": true,
            "unbridge": true,
            "username": "xxxxxxx",
            "password": "xxxxxxx",
            "deviceName": "",
            "platform": "EufySecurity",
            "enablePush": true,
            "_bridge": {
                "username": "0E:A8:90:B4:E8:E4",
                "port": 49351
            }
        }
    ]

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Comments: 17 (6 by maintainers)

Commits related to this issue

Most upvoted comments

I know that this has been closed but the arbitrary timeout (15000) doesn’t sit well with me given that it could be affected by factors such as network congestion as well as any changes that Eufy make. Perhaps it would be worth making the timeout configurable?

@makis11111 would you mind re-opening it so that we can discuss?

I’ve done a bit of digging and think I’ve found a possible solution. In CameraAccessory.ts on line 412 the notificationTimeout is assigned the value of the timer but never reset which is simple enough to do by setting it to null in the callback. However, the default three second timeout is then too short to prevent the duplicate notifications. (I also tried ten seconds and that was too short, fifteen seems to work OK.) So line 412 now looks like:-

this.notificationTimeout = setTimeout(() => { this.notificationTimeout = null; }, 15000);

Hope that helps.