[Bug]: High and increasing CPU usage over time about node-red-contrib-homekit-bridged HOT 20 OPEN

Hey, behaviour is unknown to me. Running node for years and have never seen it.

Can you tell me more about the setup?

from node-red-contrib-homekit-bridged.

Yes
I have 4 bridges.
One is used by 4 humidity sensor accessories
One is used by 7 light bulb accessories
One is used by 4 thermostat accessories
One is used by 31 various accessories (thermostats, heater coolers, light bulbs, water valve, fans)
All of them have CIAO advertising. This setup is running as-is for about 1.5 years without edits. Until like 1 month ago when i updated NRCHKB and Node-RED
Tried disabling them one by one, but didn't seem to make a difference, until i disabled all 4.

Just thought, could it be iOS devices and HomePods pinging the bridges for some reason? But i feel like that wouldn't explain why the usage keeps increasing every day
Could it also be a Node-RED 3 issue?

Here i attach a screenshot of the usage when disabling the bridges one by one. The peaks are the deployments

I also have 5 billiond nodes, but as you can see, without HK conf. nodes activated the usage goes to 0, so those are not the root cause i think.
Could you check on your instances if the usage goes drasticly down when disabling all HK conf. nodes?

IDK what other info to provide, let me know

Thanks

from node-red-contrib-homekit-bridged.

What about machine specs?

from node-red-contrib-homekit-bridged.

Pi 4B 4GB, running Node-RED under docker
Always 2/2.5GB of free ram, machine cpu usage normally is at ~4%, with HK activated it's 25% base, and increasing

from node-red-contrib-homekit-bridged.

Running on docker compose (pi4 4gb)

Running as a process (pi4 8gb)

from node-red-contrib-homekit-bridged.

HK enabled

HK disabled

don't really know what else to say

from node-red-contrib-homekit-bridged.

To me sounds like an infinity loop.
Do you have a backup before you added nrchkb to your setup?
If so maybe restore that and then try some of our example flows and see if it behaves the same?

from node-red-contrib-homekit-bridged.

no i can guarantee that is not the case, because as i said, i manually checked every input and output of the nrchkb nodes, and there is nothing wrong, no spam or looping messages.
also as i said, i’ve been running this setup without any modifications for 1.5 years. this is a new thing after i updated nrchkb to 1.4.3 and Node-RED to 3.0.2. so i think it’s either one, or the other, or the combination of both.

from node-red-contrib-homekit-bridged.

Did you do a clean install of both NR & nrchkb?
If not, that would be my next step to make sure some old config or cache isn’t causing issues.
How long did you need to run NR to see the cpu/ram spike?

I’m running same the versions but not in docker, on a pi4.

from node-red-contrib-homekit-bridged.

Tried creating a new fresh container, and i found out that

Node-RED 3.0.2:


same thing as the other instance, when deploying the usage goes and stays up, when removing and re-deploying, the usage goes back to 0

So i tried creating a new container with instead Node-RED 2.2.2:


The two peaks are the 2 deployments, and between them when nrchkb was active, there is 0 usage

So i think, as i said initially, that the cause could be NR 3.0
So, in your setups, are you running 3.x or 2.x?

from node-red-contrib-homekit-bridged.

I am on version 3. Do you mind to share your flow?

from node-red-contrib-homekit-bridged.

[ { "id": "bd3b068d9f32d7cc", "type": "homekit-service", "z": "d9a7a19c.5d00e", "isParent": true, "hostType": "0", "bridge": "a746d8b451ae08ea", "accessoryId": "", "parentService": "", "name": "jhjhkj", "serviceName": "AirQualitySensor", "topic": "", "filter": false, "manufacturer": "NRCHKB", "model": "1.4.3", "serialNo": "Default Serial Number", "firmwareRev": "1.4.3", "hardwareRev": "1.4.3", "softwareRev": "1.4.3", "cameraConfigVideoProcessor": "ffmpeg", "cameraConfigSource": "", "cameraConfigStillImageSource": "", "cameraConfigMaxStreams": 2, "cameraConfigMaxWidth": 1280, "cameraConfigMaxHeight": 720, "cameraConfigMaxFPS": 10, "cameraConfigMaxBitrate": 300, "cameraConfigVideoCodec": "libx264", "cameraConfigAudioCodec": "libfdk_aac", "cameraConfigAudio": false, "cameraConfigPacketSize": 1316, "cameraConfigVerticalFlip": false, "cameraConfigHorizontalFlip": false, "cameraConfigMapVideo": "0:0", "cameraConfigMapAudio": "0:1", "cameraConfigVideoFilter": "scale=1280:720", "cameraConfigAdditionalCommandLine": "-tune zerolatency", "cameraConfigDebug": false, "cameraConfigSnapshotOutput": "disabled", "cameraConfigInterfaceName": "", "characteristicProperties": "{}", "waitForSetupMsg": false, "outputs": 2, "x": 370, "y": 700, "wires": [ [], [] ] }, { "id": "a746d8b451ae08ea", "type": "homekit-bridge", "bridgeName": "lklk", "pinCode": "876-03-943", "port": "", "advertiser": "ciao", "allowInsecureRequest": false, "manufacturer": "NRCHKB", "model": "1.4.3", "serialNo": "Default Serial Number", "firmwareRev": "1.4.3", "hardwareRev": "1.4.3", "softwareRev": "1.4.3", "customMdnsConfig": false, "mdnsMulticast": true, "mdnsInterface": "", "mdnsPort": "", "mdnsIp": "", "mdnsTtl": "", "mdnsLoopback": true, "mdnsReuseAddr": true, "allowMessagePassthrough": true } ]

from node-red-contrib-homekit-bridged.

NR 3.0.2
NRCHKB: 1.4.3
But I don’t run in docker. It’s a Pi4, has 1 job to run NR 🤷‍♂️

from node-red-contrib-homekit-bridged.

little update
i completely re-did the setup, i also istalled raspberry pi os 64bit (i was on 32 bit before)
aaand, still the same exact issue.
still node-red 3.0.2, 8 days of runtime

and still, if i disable nrchkb, the usage goes to absolute 0.

from node-red-contrib-homekit-bridged.

here's a container restart

from node-red-contrib-homekit-bridged.

same problem after updating 1.4.x -> 1.5.0, no new scripts or changes

NR 3.0.2, intel nuc, 8gb ram, but NR is almost dead after 2-3 days, high cpu load

only restart nodered.service can help for a few days

how to debug this?

from node-red-contrib-homekit-bridged.

First of all, you can run nodered with debug mode. DEBUG=*
We should have some time stamps and action logs which we can correlate.

from node-red-contrib-homekit-bridged.

OK, reverted to 1.4.3 but still have a problem.

And it looks like a different problem. Sometimes pressing a button in a home.app (on any device, even ATV in local wifi) causes a 3-10 sec hanging before a "signal" is caught by NR node.

Direct inject/debug works immediately, but home.app (and all it automations of course) clicks makes it hangs sometimes.

https://idiod.video/v14knh.mp4 — you can notice a circle sometimes after clicking

Rebooting, restarting and so on, no idea even how to start to debug this. No trails in NR logs, looks like it just delaying commands sometimes.

from node-red-contrib-homekit-bridged.

I don’t use Docker so might be unrelated.
But what Advertiser are you using on your NRCHKB config node(s)?
Is docker networking in Host mode?
And check that the Advertiser’s port is open/not shared by another service.

from node-red-contrib-homekit-bridged.

@ptath where did you get with this?

from node-red-contrib-homekit-bridged.