There you see the most memory hungry threads.
Do you need them all? Are you sure you want to run MySQL on a Pi?
And what do you do with Python? Seems that Python took already lots of cpu time.
If you have a good backup you could consider reinstalling a new SD card and start over.
Then, only install what you really need. You'll see that it'll be lots faster and stable.
I have Domoticz running on an Acer T180 desktop machine running Ubuntu Server. It will shortly be moving to a Raspberry Pi3.
Hardware: (USB) => RFXComm, ZWave, CC128, LAN => 12 1Wire sensors on a network.
Feeding stuff into Domoticz and even controlling Domoticz using JSON URLS and MQTT messages is childsplay. I've have monit watching over Domoticz since the early days because there used to be a strange bug that caused the webserver part of Domoticz to crash (ie the interface would say offline), but the core program kept running - timers would still switch stuff on and off, you just had no interface.
As an example - at night I say "OK Google, Goodnight House" and IFTTT posts to my webserver, my webserver publishes an MQTT command which NodeRed intercepts and executes a specific PHP script (named in the MQTT message). The PHP script using nothing but MQTT messages performs the following:
Send a notification to ALL devices registered with JOIN. Switch on bedroom lights, Switch off Kitchen, Stop NOWTV from Streaming, Switch off AVR. Wait 15 seconds. Switch off Livingroom. Wait 60 seconds. Switch off Hall. Wait 60 seconds. Switch off ALL downstairs lights. Set the nightmode user variable to 1. Tell the Google Home device to speak "The house mode has now been set to night mode, Goodnight!". Send a notification to all devices registered with JOIN - to confirm night mode has been set.
Your belief that you are tied to specific hardware and software is flawed, for example - I've been using the CC128 for years which is not as of 3.5877 a natively supported device (for 3 phase). As I started with Tellstick, and still have some critical hardware relying on it - I've always had a workaround for the lack of support, and have just recently upgraded with the use of PiZeroW's being so low cost, MQTT messages now control the Tellstick on the remote PiZeroW - which controls the switching on and off of the attic fans.
Off the shelf systems are generally reliable, but they aren't as versatile and can be very costly to add to. Software like Domoticz doesn't tie you to any specific hardware, and because you can update it with JSON and MQTT messages - virtual sensors and switches can be used to cover any hardware that isn't natively supported.
(Also I would agree with others, there is absolutely no need to be sending the temperature more often than once every few minutes, the majority of my devices send every 5 minutes, though you will note that battery operated devices - like my OWL CM180 - changes how often it transmits based on the value it is transmitting, eg if the electricity use is 300w, it might only broadcast every few minutes, but if the use is 3.26kW it might broadcast every 30 seconds)
Sorry That i break in...
Only My board is using a lot of memory and then crash...
With the command : top -o %MEM
I see a lot op phyton.. used by root...
ScreenShot228.jpg (129.27 KiB) Viewed 2092 times
is this normal?
How can witch script is root using?
In my eyes i do use only 4-5 phyton scripts...
How can i stop this other scripts??
Xu4: Beta Extreme antenna RFXcomE,WU Fi Ping ip P1 Gen5 PVOutput Harmony HUE SolarmanPv OTG Winddelen Alive ESP Buienradar MySensors WOL Winddelen counting RPi: Beta SMAspot RFlinkTest Domoticz ...Different backups