Error: Public key is not valid for specified curve

[jvanderb]

Is there an existing issue for this?

• I have searched the existing issues

Describe The Bug

Very recently, the following message has been showing up occasionally in the logs. Everything still seems to function properly aside from this error.

Error: Public key is not valid for specified curve

To Reproduce

Unknown - nothing has been done to cause error that I am aware of.

Expected behavior

This error should ideally not show up.

Relevant log output

Error: Public key is not valid for specified curve
    at ECDH.dhComputeSecret [as computeSecret] (node:internal/crypto/diffiehellman:165:11)
    at extractDH (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:109:17)
    at extractSecretAndContext (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:127:14)
    at deriveKeyAndNonce (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:214:13)
    at Object.decrypt (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:371:13)
    at decrypt (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/utils/decrypt.ts:34:27)
    at PushReceiver.#handleDataMessage (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/client.ts:408:30)
    at PushReceiver.#handleMessage (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/client.ts:363:40)
    at /var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/client.ts:113:65
    at EventEmitter.handler (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/emitter.ts:13:25) {
  code: 'ERR_CRYPTO_ECDH_INVALID_PUBLIC_KEY'
}
Error: Public key is not valid for specified curve
    at ECDH.dhComputeSecret [as computeSecret] (node:internal/crypto/diffiehellman:165:11)
    at extractDH (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:109:17)
    at extractSecretAndContext (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:127:14)
    at deriveKeyAndNonce (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:214:13)
    at Object.decrypt (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:371:13)
    at decrypt (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/utils/decrypt.ts:34:27)
    at PushReceiver.#handleDataMessage (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/client.ts:408:30)
    at PushReceiver.#handleMessage (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/client.ts:363:40)
    at /var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/client.ts:113:65
    at EventEmitter.handler (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/emitter.ts:13:25) {
  code: 'ERR_CRYPTO_ECDH_INVALID_PUBLIC_KEY'
}

Screenshots

No response

Homebridge Ring Config

{
            "refreshToken": "[REDACTED]",
            "alarmOnEntryDelay": false,
            "hideLightGroups": false,
            "hideDoorbellSwitch": false,
            "hideCameraLight": false,
            "hideCameraMotionSensor": false,
            "hideCameraSirenSwitch": false,
            "hideInHomeDoorbellSwitch": false,
            "hideAlarmSirenSwitch": false,
            "showPanicButtons": false,
            "avoidSnapshotBatteryDrain": false,
            "debug": false,
            "disableLogs": false,
            "_bridge": {
                "username": "[REDACTED]",
                "port": 30020
            },
            "platform": "Ring"
        },

Additional context

No response

OS

Debian GNU/Linux 13 (trixie)

Node.js Version

v24.13.0

NPM Version

v11.6.2

Homebridge/HOOBs Version

v1.11.1

Homebridge Ring Plugin Version

v14.2.0

Operating System

Raspberry Pi OS (13.3/Trixie)

[tsightler]

The message is coming from a dependent library, if it's causing no apparent issues I'm not sure there is a lot that can be done. Since you did not provide full logs, it's difficult to really understand the full context, do you have cameras/intercom? If so, are you still receiving motion/ding notifications from these devices?

[jvanderb]

I'd be happy to provide additional logs, though I was hesitant to post them here as I did not go through them to redact any private info.

I have a doorbell, a camera and a couple of chime devices. Sometimes I get notifications, but not always. I've noticed a couple of times I'll get a notification from the Ring app on my phone, Homebridge does not receive it. I'm not 100% sure these are correlated, but I think they are.

What would be the best way to share logs here?

Thanks!

[ellieplz]

Hey hey! I have the same exact issue. Same "Error: Public key is not valid for specified curve" log line on boot, same unrealiability issues with notifications being sent to the Ring app but not to homebridge.

Last year system was working flawlessly, but in 2026 this issue started haunting my setup.

Log example from today:

[26/02/2026, 12:08:34] [Ring] Initializing Ring platform... [26/02/2026, 12:08:34] [Ring] Configuring cached accessory ******** [26/02/2026, 12:08:35] [Ring] Found the following locations: [26/02/2026, 12:08:35] [Ring] locationId: *********** [26/02/2026, 12:08:35] [Ring] Configuring 0 cameras and 1 devices for location "*********** Error: Public key is not valid for specified curve at ECDH.dhComputeSecret [as computeSecret] (node:internal/crypto/diffiehellman:165:11) at extractDH (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:109:17) at extractSecretAndContext (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:127:14) at deriveKeyAndNonce (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:214:13) at Object.decrypt (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:371:13) at decrypt (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/utils/decrypt.ts:34:27) at PushReceiver.#handleDataMessage (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/client.ts:408:30) at PushReceiver.#handleMessage (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/client.ts:363:40) at /var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/client.ts:113:65 at EventEmitter.handler (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/emitter.ts:13:25) { code: 'ERR_CRYPTO_ECDH_INVALID_PUBLIC_KEY' }

Only device I am using is an intercom.

What helped (briefly) was cleaning cached devices, removing the plugin, removing the token from the account, etc and adding it again, but after few days issue returned. Any ideas?

[jvanderb]

Still happening for me too - the whole plugin is basically worthless for me right now as I am not getting most push notifications anymore. Unfortunately it doesn't seem like anyone is very interested in looking into the issue - it's been dismissed as being with an underlying library, and the developer is not responding to this issue any more.

[marcelgood]

Just noticed this as well. Seems to have started today for me. Some key must have expired. So far haven't noticed anything not working. I'm not using push notifications, but I have a Ring Alarm system. Even though the error occurs right after controlling the alarm system, it still seems to work and arm/disarms the system. So, not sure what functionality this affects.

[2/26/2026, 10:55:16 AM] [Ring] Disarming Alarm
Error: Public key is not valid for specified curve
    at ECDH.dhComputeSecret [as computeSecret] (node:internal/crypto/diffiehellman:165:11)
    at extractDH (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:109:17)
    at extractSecretAndContext (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:127:14)
    at deriveKeyAndNonce (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:214:13)
    at Object.decrypt (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/http_ece/ece.js:371:13)
    at decrypt (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/utils/decrypt.ts:34:27)
    at PushReceiver.#handleDataMessage (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/client.ts:408:30)
    at PushReceiver.#handleMessage (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/client.ts:363:40)
    at /var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/client.ts:113:65
    at EventEmitter.handler (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/@eneris/push-receiver/src/emitter.ts:13:25) {
  code: 'ERR_CRYPTO_ECDH_INVALID_PUBLIC_KEY'
}

[tsightler]

I believe a PR has been submitted to the upstream package that should address this, but it's not yet been merged and a new release issued.

[marcelgood]

I think I found the PR. It's been merged.

Eneris/push-receiver#33

[tsightler]

Still happening for me too - the whole plugin is basically worthless for me right now as I am not getting most push notifications anymore. Unfortunately it doesn't seem like anyone is very interested in looking into the issue - it's been dismissed as being with an underlying library, and the developer is not responding to this issue any more.

@jvanderb I don't really think this is a fair characterization. I mean, for one, the problem was not "dismissed as being with an underlying library" it simply is a fact that the problem is with an underlying library. In your OP you stated specifically: "Everything still seems to function properly aside from this error", so it was not really clear that the log messages were critical, even though it seemed it might be a problem.

This project is just a community project, something someone put together and was crazy enough to share on the internet for free, there is no SLA to resolve reported issues with this project. We who maintain the project all have day jobs and lives beyond this small side project and, when problems are not directly in the code we control (i.e. a dependent project), and we have no direct way to reproduce them, it can take time to understand what is happening, work with those other projects, which are likely also community projects with single developers with limited personal time, etc, get fixes upstream, and push out new versions that use these project.

If you are unhappy with this, you should probably not use community projects and rather purchase products that have native support for Homekit. At least then you are paying for someone to support you. I'm not really sure your experience will be any better, but that's the best suggestion I can give you if you expect every issue to be acted upon in some way that meets your expected timeframe.

The great thing about a communitiy project is that anyone can contribute to it, so if someone else is able to figure out a fix when we as maintainers are perhaps limited in time or information, they can submit it, and, in this case, it appears someones else has already submitted the fix upstream. While it appears that fix has been merged, I've yet to see a new version of push-receiver appear in NPM. Once that happens, it's possible to push a new version of this project with the upstream fixes.

[ellieplz]

Hey hey!
Correct me if I'm wrong but I think new release of that push receiver was dropped in npm 4 days ago:
https://www.npmjs.com/package/@eneris/push-receiver?activeTab=versions

Chances are you looked up the original project which didn't get any updates in ages and its last release was in 2020:
https://www.npmjs.com/package/push-receiver?activeTab=versions

[tsightler]

@ellieplz It was pushed just about 12 hours after I posted that (I'm quite aware of which push-receiver is used here as I've submitted several PRs and issues there as well), but I just haven't had time to follow up. We'll try to get something pushed soon.