Same here. Not a parameter I'm familiar with.
Since last writing I've not had any glitches (I think my HE reads my posts here and is behaving as a result), so have not reverted as yet.
Cheers.
@gopher.ny , I awoke today (not morning) to find my Zigbee radio shut down again. I thought that all was well after changing to 11 for event and state history. It did take 4 days to happen this time. I’m at a loss, since there was no slowdown, no increased db size, no web ui slowness, nothing out of the ordinary except the Zigbee radio was off. My logs din’t show anything except Zigbee queue is full, which is due to the radio being off. I shut down and rebooted without issue and all is well again.
This happened to me on a C-4 but probably not your issue - anyway this is what @gopher.ny posted back then...
1 Like
Probably not it, not a lot was happening at the time.
1 Like
Its set to 10 now was 100
Its up and running perfectly now on V 2.2.5.131 no slowdowns or high CPU load warning fast responsive all good
You might see faster response if you set both parameters to 11. If set to 10 the cpu has to do gc after every event. If set to 11, it’s only done hourly.
2 Likes
So it goes to 11
2 Likes
Well, I got my next failure- same as a prior failure. An outlet and connected device turned on by timer/rule as expected. Mirrored light did not, and this was because the original unit, while on, had no record of turning on in the event log. It's quite intermittent, but I don't recall it happening prior to 2.2.7.XXX. So back on 2.2.6.140.
Interestingly, it seems that switching versions may have reset my "Enable debug logging" flags on my devices, so I had to reset.
Cheers.
