Zwave problem after service restart

[C4rtm4N]

I have Monit set up to restart the Domoticz service if the system is sat on a high CPU for too long but have now started to notice that this causes the zwave hardware to fail within the app and all nodes show as red.

I haven't got the zwave hardware set up to restart if it loses signal for any length of time as this didn't work well in the past so the only way for me to get things working again is to reboot my pi. I could set monitor up to do this but is there another service that I could restart instead?

[Egregius]

Domoticz shouldn't be restarted, that means somethings wrong. I do think that a reboot of the Pi is almost as fast as just a restart of the service. And has other advantages as cleared memory, swap usage,...

Main thing to do is figure out why/when Domoticz is using high cpu.

[C4rtm4N]

Thanks Egregius

I think that there may be a faulty zwave module in my bathroom as often the high CPU comes after it either than fan or the lights attached to it are activated. When I installed things this one was always temperamental but it then got better for a long time.

I'll monitor for a while and will maybe replace it in a couple of weeks.

[C4rtm4N]

A very old thread I know but I'm still having high CPU problems and really have no idea where to look now so am after some advice. For the last year Monit has been restarting my Pi up to 3 times a day (average of once). Usual CPU load 3-4%, spikes to full CPU on occasions causing the reboot - if I disable Monit then the system locks up with high CPU anyway and I need to manually restart. Spikes seem to happen when a zwave event occurs (eg lights turn on either by switch or timer).

I've tried the following
* New Raspberry Pi (Domoticz restored from backup, everything else clean install)
* Replaced 3 x zwave modules (1 failed totally, 1 lost partial functionality, 1 I thought was faulty but seemingly wasn't)
* Hard reset of zwave stick
* Turned off all polling
* Added further zwave modules (13 in total) so that mesh network should be totally sound.

Does anyone else have problems like this or couls someone make suggestions where to look next?

zwave1.jpg (43.66 KiB) Viewed 574 times

zwave.jpg (98.06 KiB) Viewed 574 times