Well, you are correct in some regard. Something in 0.117.x is causing the problem. Perhaps a way it is logging, or there is a new library it is using or there’s a loop in some code somewhere that wasn’t there before when it interacts with something.
I’m just trying to find more specifically what the problem is with my set-up, sharing it here, and then hopefully they can fix whatever it is when we find it.
Something in 0.117.x is interacting with our current Integrations in a way that it wasn’t before.
They’ll find it and fix it. I’m confident in the developers and their abilities. The main thing is not losing any data, and so far I have not.
The onvif integration had a memory leak, so if you have onvif camera’s that might be an explanation.
Another memory leak is coming from the Brother integration, probably only if you have the integration and your printer is turned of, more information and a solution to test can be found in the following bug reports:
I’ve seen a memory leak in 0.117.x as well and do have the Brother printer integration. Interestingly my printer had been turned off after a power outage and was such unreachable. Looks like a fix may go into 0.117.4 (https://github.com/home-assistant/core/pull/42833).
Dropped by to say I think I’ve narrowed mine down to the brother integration, looks like I’m 4 hours late to the party! Great work guys, installing 0.117.4 as we speak
It happened exactly when you restart Home Assistant with the printer off. If you turn it off after Home Assistant is on, and you don’t restart it, all is good.
In the Home Assistant issue, there are links to a modified code of the new Profiler that is expected for version 0.118.0 but you can install as custom_component and can profile the memory. Maybe it does not show nothing, but maybe can help. Here is the link with the information: https://github.com/home-assistant/core/issues/42752#issuecomment-721153813
Is very easy to use. Configure it to execute for 1, 2 or 3 hours (it depends how fast it grows in your system) and post the file that it produces.
just to confirm, I see an issue with DSMR as well.
after deleting the dsmr integration from UI I see this. black line indicates the momemt I did that and rebooted some times… (after reboot the integration is back again… )
What changed in 0.117 for DSMR is that force_update property is set True for the entities. This means that every time data is received from the meter, it generates an event even when data does not change. This was changed because integrations like influxdb listen to state changed events. Without the property set, it can take hours for some data to change and nothing is reported to influxdb even though data is reported.
The downside is that smart meters connected through DSMR report data fast (every 5 seconds or so). There are 30 entities in this integration, so HA needs to handle 30 events per 5 seconds. Apparently it’s very hardware dependent whether this amount can be handled.
I’ve added a kind of rate limiter in this PR:
You can copy-paste the code in custom_components folder to see if it makes a difference. It’s set by default there to not report faster than 30 seconds.
I am not able to find the correct path where to put the sensor.py file.
The file I got by doing these steps, clicking:
your link > on the bottom of the page click ‘Fix pylint’ aeaa98a > homeassistant/components/dsmr/sensor.py > 3dots > view file > Raw > copy all > past in new txt file. rename new txt file to sensor.py
I have put this sensor.py file directly in config/custom_components, I dont see a dsmr folder in there.
I see there only my other integrations, just hacs/smart_sensor/unifigatway/wiz_light/xiaomi_map_extractor
I have put back dsmr sensor info in configuration.yaml, and added the integration again.
Result after 5 minutes it took to write this, still 9% cpu usage, where it was just befor that 2%.
My first guess I am either taking the wrong file, or putting it somewhere incorrectly.
