mqtt_vacuum_camera: PROXMOX: Memory shortage error -> Rendered image froze
Checklist
- I have updated the integration to the latest version available
- I have checked if the problem is already reported
The problem
I think the memory margin is miscalculated. I don’t get any rendered picture, but the following Error:
What version of an integration has described problem?
1.5.7.4
What was the last working version of an integration?
1.5.7
What vacuum model do you have problems with?
Roborock.S5
Please firmware installed on your Vacuum.
Valetudo 2023.12.0
What version of Home Assistant do you use?
core-2024.2.0
What type of installation are you running?
Home Assistant OS
Camera’s settings.
No response
Logs or Errors shown in the HA snapshots (please enable the Debug Mode)
2024-02-09 09:47:05.343 ERROR (rocky_camera_0) [custom_components.valetudo_vacuum_camera.valetudo.hypfer.image_handler] Memory shortage error: Not enough memory available (Margin: 1200.0 MiB)
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 36 (25 by maintainers)
@cdrfun and @N1c093 v1.5.8 is now available, hope you will enjoy it at your disposal for any future requirements or ideas.
Take your time, i dont really need the map, but i Just wanted to report 👍
Also, i am upgrading soon, so dont feel pressured
This might be semi-related: I run home assistant on a raspberry pi 3 with 1GB. So far everything worked fine, and usually not more than around 600 MB memory is used. When trying to run this custom component, I get OOM kills of python, resulting in a crash/restart loop of home assistant. But I guess my hardware is too limited. I just wanted to leave a note here for this information.
@sca075 Thank you for your work. I just installed v.1.5.8 and decreased my ram from 4GB back to 3 GB. Everything seems to work fine now 👍
Tested also the configuration that @cdrfun use since 5 years, with 2GB ram, of course proxmox (HA) will use use the swap area, and…
two vacuum at the same time running is still possible 😃 so V1.5.8 will go out as scheduled between today or tomorrow morning.
@sca075
When I noticed this error I just increased the ram from 3gb to 4gb of the virtual machine on Proxmox. I thought it was a miss configuration on my side. Should I install the newest update and decrease the ram to 3gb again? If anything is working fine you don’t need any log-files, right?
@cdrfun really good catch thanks a lot (grazie)! I will follow you advice and anyhow confirm the size of the array (this patch’s are coming out daily and as I work alone on this… well…) Thanks once again for pointing this.