Method ... of app/device... ran for ...ms

[Jost]

Lately I'm getting this error message several times a day. (BTW: I have not changed any app or device codes.)

I also notice that saving changes to device settings sometimes takes a veeery long time (e.g. a minute instead of the usual 2 seconds).

What can be the reason, how can I eliminate these problems?
(I already rebooted... no success!)

[kkossev]

Are you seeing these error logs for different devices, or for specific ones only?

Is the delay observed for Zwave or Zigbee devices? Mains or battery powered?

[Jost]

@kkossev

Are you seeing these error logs for different devices, or for specific ones only?

Different devices and apps.

@kkossev

Is the delay observed for Zwave or Zigbee devices? Mains or battery powered?

All types.

=> It's while saving something (code, changed settings)... but not every time.

[thebearmay]

The only time I see these is if something has the hub tied up when a process is trying to run (for me usually a reboot). So a couple of things you could look at:

• Is there a pattern - time of day, or when another known process is running
• Check for a device or app that seems to have increased it’s % of total lately

[Jost]

@thebearmay

Check for a device or app that seems to have increased it’s % of total lately

OK, there is one device (Chromecast Audio) that has much more % than normally (7% instead of 0.5%). The device is currently often without power (it's powered by an off-grid solar system). But there was no such problem last winter...

[thebearmay]

Is it logging events?

[gopher.ny]

Can you PM me your hub's id? I can check the engineering logs for obvious errors.

[Jost]

@thebearmay

Is it logging events?

Today there were no events (and BTW no "it takes forever to save" problems) - but yesterday:

I'Ve never seen before timeouts that take more than 10 minutes!?!

BTW: It's a pitty that I cannot check the source code of Chromecast Audio...

@gopher.ny

I can check the engineering logs for obvious errors.

That would be nice!
But today there were no (big) problems... Shall I wait till the "it takes forever to save" problem occurs again?

[gopher.ny]

@Jost

Shall I wait till the "it takes forever to save" problem occurs again?

Not necessarily, if the issue left some clues in the logs, they would still be there. If not, it probably won't next time, either.

[Jost]

@gopher.ny

Can you PM me your hub's id?

Done.

BTW: Those Chromecast Audio error/warn events arised again (2 minutes after I shut down again the power in the garden shed):

But after that I have not noticed any saving problems...