Multiple Z-wave errors and slow respons, going crazy here

One more thing, could it be that my hardware (Mac mini 2010) is getting slow even if the CPU load is low? I have big problems w/ the HTTPd 2 plugin with timeouts, roundtrip to the HTTPd-servers is about 4+ seconds w/ digest auth, this can not be right. I do have other stuff running on the same computer, MAMP and postgres, with no issues. Where to start investigate this if it's only Indigo that is slow on my hardware?

//L

[matt (support)]

30362092 2021-09-08 19:25:40.899 FALSE 7 Z-Wave Debug queueing power / energy request of "158 - Ljus garage - ytter S" (activity detected)

Example when turning on "Ljus garage - ytter S" when I have turned off pulling in the device settings. Indigo still "queueing power / energy request of "158 - Ljus garage - ytter S" (activity detected)", why is that? There is alot of activity from this query and I gues my node is sending the energy report anyway so why ask for it?

For that device uncheck the Enable polling of this device checkbox in the device settings dialog. That checkbox causes Indigo to poll out the energy / power usage and status whenever it detects a message or state change from the module. That is needed by some modules, but most newer ones are good about broadcasting out changes so the polling likely isn't needed. And the polling definitely increases the odds of collisions and congestion, so by disabling that option for all/most of your device you might see some improvements. Note the UI checkbox won't be visible for all devices – there are some where we hide (and turn it off) when we know it isn't useful.

Thanx for the clarification!

But the device already had pulling disabled and it looks like Indigo is still pulling it due to a change in state :/ Do I need to do something else to make it work?

[matt (support)]

Is that module a dimmer or relay? Indigo always polls out power/energy when those modules broadcast back a state reply. Presuming that is the case I'm going to look into adding UI to disable this for you.

Yes, it is a dimmer (FGD212).
I guess active pulling is not needed due to the dimmer/relay sending energy reports according to their settings (watt % up or down trigger a report)(?)
Would be great to be able to optimize network traffic but I'm not sure this is the biggest problem for me at this point.

Update on my instability issues:
Yesterday I copied the network from my UZB to my Z-stick Gen5 and I think it is more stable, I get fewer error reports and ZEAL-error reports anyway, but I still get them. Mostly from energy meter updates initiated from Indigo (thats why I ask about disabling them).

I still have massive problems w/ updates from local on/off from my FGS223. Works most of the time but far from always, strange. When it fails I don't get scene commands either. My next step on this issue is to exclude/reinclude (reset) and use only scenes to see if it is more reliable than the "multi endpoint fix".

To be continued...

PS, more on energy report pulling:

Turning off a Fibaro wallplug (with pulling disabled):

30483425 2021-09-09 20:55:46.766 FALSE 7 Z-Wave Debug . . requestMeterLevel: 0.0 W (float: 0.000000) same value as the wallplug sent before pulling
30483424 2021-09-09 20:55:46.766 FALSE 7 Z-Wave Debug . . requestMeterLevel: node 026, endpoint None, meterType 01, raw value 3200...
30483423 2021-09-09 20:55:46.764 FALSE 7 Z-Wave Debug RCVD requestMeterLevel: 01 0E 00 04 00 1A 08 32 02 21 32 00 00 00 00 C4
30483422 2021-09-09 20:55:46.743 FALSE 7 Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
30483421 2021-09-09 20:55:46.742 FALSE 7 Z-Wave Debug RCVD requestMeterLevel: 01 07 00 13 D9 00 00 02 30 (node ACK)
30483420 2021-09-09 20:55:46.717 FALSE 7 Z-Wave Debug SENT requestMeterLevel: 01 0A 00 13 1A 03 32 01 10 25 D9 20
30483419 2021-09-09 20:55:46.716 FALSE 7 Z-Wave Debug . . requestMeterLevel: 0.41 kWh (float: 0.410000) kWh is not sent from wallplug if not over trigger level for energy usage, but if not over we maybe don't need it
30483418 2021-09-09 20:55:46.716 FALSE 7 Z-Wave Debug . . requestMeterLevel: node 026, endpoint None, meterType 01, raw value 4400...
30483417 2021-09-09 20:55:46.714 FALSE 7 Z-Wave Debug RCVD requestMeterLevel: 01 10 00 04 00 1A 0A 32 02 21 44 00 00 00 29 00 00 87
30483416 2021-09-09 20:55:46.704 FALSE 7 Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
30483415 2021-09-09 20:55:46.703 FALSE 7 Z-Wave Debug RCVD requestMeterLevel: 01 07 00 13 D8 00 00 02 31 (node ACK)
30483414 2021-09-09 20:55:46.671 FALSE 7 Z-Wave Debug SENT requestMeterLevel: 01 0A 00 13 1A 03 32 01 00 25 D8 31
30483413 2021-09-09 20:55:46.663 FALSE 7 Z-Wave Debug polling status of node "026 - Lödkolv - Wallplug" (post-activity power / energy request)
30483412 2021-09-09 20:55:41.654 FALSE 7 Z-Wave Debug received "Lödkolv - Wallplug" power load to 0.0 W This one is sent from wallplug regardless of pulling I guess
30483411 2021-09-09 20:55:41.654 FALSE 7 Z-Wave Debug . . requestVarSensorStatus: 0.0 W (float: 0.000000)
30483410 2021-09-09 20:55:41.654 FALSE 7 Z-Wave Debug . . requestVarSensorStatus: node 026, endpoint None, type 4, raw value 2200...
30483409 2021-09-09 20:55:41.652 FALSE 7 Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 1A 06 31 05 04 22 00 00 F9
30483407 2021-09-09 20:55:40.902 FALSE 7 Z-Wave Debug queueing power / energy request of "026 - Lödkolv - Wallplug" (activity detected)
30483406 2021-09-09 20:55:40.9 FALSE 8 Z-Wave sent "Lödkolv - Wallplug" off

Alot of messages on the network and the process takes about 6 seconds, w/o active pulling the process would have been about half a second.

[matt (support)]

Indigo 2021.2.0 is now available and includes a new device setting option (checkbox), Poll energy/power after device state changes. By default is should be disabled and will hopefully reduce some of the Z-Wave traffic / congestion for your setup.

Great!!