You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Govee, http shows the proces. Quite often as Top process.
I noticed, when I am running the Govee plug-in, that the temperature of the RaspiZero2 is about 6-8 degree Celsius higher then without the plug-in.
Maybe someone can have a look if polling is too often or maybe that the polling process it self consumes too much cpu-power? Looks like throttling the cpu down is not as effective when running the plug-in.
To Reproduce:
Activate plug-in for some time, look at the cpu temperature then disable it and look again at the cpu temperature
Expected behavior:
Would expect the plug-in to behave cpu friendly and m"bye let me configure now often to poll the devices.
Logs:
Show the Homebridge logs here, remove any sensitive information.
Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.
Screenshots:
Environment:
Plugin Version: 1.1.2
Homebridge Version: 1.3.6
Node.js Version: 16.13.0
NPM Version: 8.1.0
Operating System: Raspbian
The text was updated successfully, but these errors were encountered:
Did a debugging.
In 8:15 Minutes the 3 devices (one of them is not mine, wherever that is but I cannot exclude it from checks) have been check 143 times.
Just checked again. Enabling Govee Plugin brings the RaspiZero2 pretty fast from 54 to 61 degree celsius (standard case).
Turning it off, brings it back to 54.
Hey @MrFly72, just tried this on my RPi 4B and have the same results. I think I saw a file where you can state how many times the data is polled from the RPi. I'll post if I can find info.
Describe The Bug:
When using Govee, http shows the proces. Quite often as Top process.
I noticed, when I am running the Govee plug-in, that the temperature of the RaspiZero2 is about 6-8 degree Celsius higher then without the plug-in.
Maybe someone can have a look if polling is too often or maybe that the polling process it self consumes too much cpu-power? Looks like throttling the cpu down is not as effective when running the plug-in.
To Reproduce:
Activate plug-in for some time, look at the cpu temperature then disable it and look again at the cpu temperature
Expected behavior:
Would expect the plug-in to behave cpu friendly and m"bye let me configure now often to poll the devices.
Logs:
Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.
Screenshots:
Environment:
The text was updated successfully, but these errors were encountered: