This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Update dependency @types/chai to v4.3.19
• Update dependency @types/lodash to v4.17.7
• Update dependency axios to v1.7.7
• Update dependency @types/node to v20.16.5
• Update dependency eslint-plugin-import to v2.30.0
• Update dependency eslint-plugin-prettier to v5.2.1
• Update dependency mocha to v10.7.3 (mocha, @types/mocha)
• Update dependency pino to v9.4.0
• Update dependency typescript to v5.6.2
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency @types/ws to v8.5.12
• Update dependency inquirer to v9.3.6
• Update dependency prettier to v3.3.3
• Update dependency rimraf to v5.0.10
• Update dependency release-it to v17.6.0
• Update dependency eslint to v9
• Update dependency eslint-config-airbnb-typescript to v18
• Update dependency inquirer to v10
• Update dependency rimraf to v6
• Update typescript-eslint monorepo to v8 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Hello there,

Just figured out that homebridge-flexom, which relies on flexom-lib, sends/receives frequent pings/pongs from the Hemis WS endpoint. Currently the interval for both c2s and s2s are set to 5s.

Also, the reconnect delay is set to 100ms, which I'm afraid could trigger a flood of connection attempts if the WS server goes down for a few seconds. Which could lead to the target WS server implementing restrictive rate-limits if there are too many homebridge-flexom clients flooding when it goes back online.

Ref: https://github.com/rsauget/flexom-lib/blob/master/src/hemis/ws.ts#L36

Is that necessary? Could all intervals be made larger?

Here's what I'd suggest, based on working w/ WS servers in different networking environments (eg. w/ restrictive NATs killing long-running TCP connections that do not heartbeat frequently-enough):

    reconnectDelay: 1000,
    heartbeatIncoming: 20000,
    heartbeatOutgoing: 20000,

This changes reconnectDelay from 100ms to 1s, heartbeatOutgoing + heartbeatIncoming from 5s to 20s.