Duwi causing wakeup calls

[akatar 208]

I could not find a part of the forum where this fits best, so i throw my question overhere

 

I noticed some kind of anoying delay when starting some scenes.

I use  for starting these  scenes a duwi walltransmitter:

Please login or register to see this link.

And this module causing a lot off wakeup calls, flooding my zwave network (see picture)

Also is this module not supported by fibaro (see other picture) is this the reason for this effect?

 

I was promised quite some time ago that this will be added, but still waiting

@m.roszak can you check if this module will be supported in the (near) future?

Or if you or anybody has an idea if this is the reason for this? (or better, al sollution)

 

Please login or register to see this attachment.

Please login or register to see this attachment.

[akatar 208]

and to add another question, since i am running this beta i got several explorer calls, flooding my zwave network

Why is this happening?

 

Please login or register to see this attachment.

[m.roszak 763]

As for WakeUpBeams, is that Duwi a FLiRS?

As for "explorer frames" - this is something on protocol side, every device in network (including controller) may trigger it if destination node was not reachable via knows routing paths.
Looks like your Node 120 is not responding or it is out of range of the controller. 

[akatar 208]

33 minutes ago, m.roszak said:

As for WakeUpBeams, is that Duwi a FLiRS?

As for "explorer frames" - this is something on protocol side, every device in network (including controller) may trigger it if destination node was not reachable via knows routing paths.
Looks like your Node 120 is not responding or it is out of range of the controller. 

No it's not.

120 is a fibaro wallplug with direct connection to the hc3

But i must say, updating to this last beta makes everything feel a bit slow, with the last stable ths outside lights goes on almost direct ( 4 lights) now it's slower (a lot)

 

and node 110 = fibaro wallplug (new for xmas tree)

Edited December 27, 2021 by akatar

[m.roszak 763]

Maybe try to reconfigure mesh network for this wallplug.

There was no changes in the Z-Wave engine (engines) which would make any impact on the network performance.

It is possible that during update (when controller is down) some devices tried to rebuild a mesh network (trying to report for non-responsive controller) - if that is the case everything will go back to normal after some time (network should be able to reconfigure itself again if communication issues will occur).  

Regards,
Michał 

[akatar 208]

Thank you, we will wait for that