- Platform information:
- Hardware: Raspberry Pi 3B
- OS: Raspbian Buster
- Java Runtime Environment: Zulu (openjdk version “1.8.0_152”)
- openHAB version: 2.4.0 (Build)
I’m running a fresh repository installation of openHAB 2.4 on a Raspberry Pi 3B. Only two bindings have been installed (TCP/UDP and Systeminfo), some rules to extract the data from UDP are used.
I’m using a browser running on the PC to display the sitemaps (basicUI).
When adding charts with different visibility for different time periods the CPU load and RAM usage goes up quite a bit. Also, updating of the sitemap and response time to the switch is very slow.
The chart shows that
- around 10:00 the charts with selectable visibilities are added
- around 14:00 the visibility is changed by clicking the the button
- then these charts are deleted from the sitemap
- RAM usage remains high after deleting the charts from the sitemap
Note that the CPU chart is not the one with selectable visibility!
The switch item is active and included in the sitemap all the time.
The selector looks like this (sitemap):
Switch item= nWaterMeterChartPeriod label=“Zeitraum” icon=“time” mappings=[0=“Stunde”, 1=“Tag”, 2=“Woche”, 3=“Monat”]
The switch item has been declared in an .items file.
The part of the sitemap which is commented in and out:
Chart item= nWaterUsageToday period=h refresh=10 legend=true visibility=[nWaterMeterChartPeriod==0] Chart item= nWaterUsageToday period=D refresh=10 legend=true visibility=[nWaterMeterChartPeriod==1, nWaterMeterChartPeriod==NULL] Chart item= nWaterUsageToday period=W refresh=10 legend=true visibility=[nWaterMeterChartPeriod==2] Chart item= nWaterUsageToday period=M refresh=10 legend=true visibility=[nWaterMeterChartPeriod==3]
So my questions are:
- Have I missed some setting when adding chart visibility?
- How can the CPU load and RAM usage be reduced?
I hope to get some insights from the community.
Thank you very much!