z-wave frame logging

[Comfortica 17]

In one of the systems we have installed, a rollershutter module v3 is misbehaving. It automatically turns up and down, completely at random. We have disabled all scenes, but the misbehavior keeps returning. We even replaced the module, which also did not solve the ghosting issue. There is no RGBW module (that can cause strange associations) included, and we have run out of ideas. Now, FIBARO support can check the log files and probably see that is was a z-wave frame that open or closed the shutter. But, is there any way we can this our self in the controller? Is there any API/Lua available to check that? (we probably could use z-sniffer in the system I guess?)

 

(yes, we have disabled all the alarm options for the problematic module). 

[petergebruers 1,268]

1 hour ago, Comfortica said:

There is no RGBW module (that can cause strange associations)

The Fibaro Wall Plug (1st gen) can also cause this issue

 

1 hour ago, Comfortica said:

Now, FIBARO support can check the log files

Yes

 

1 hour ago, Comfortica said:

and probably see that is was a z-wave frame that open or closed the shutter.

No, they cannot. The controller is not a "Zniffer", it is not "promiscuous" meaning it cannot detect traffic from module X to module Y. Only traffic from the controller to a device and from a device to the controller will make it into the log.

 

I assume you are 100% sure, no "scene" or VD causes this?

 

1 hour ago, Comfortica said:

But, is there any way we can this our self in the controller?

No, not in simple and legal way. If it is a HC2, this is a "linux" system and the data is on a USB stick, so if you have the knowledge and want to take the risks (Fibaro will refuse all responsibility if you remove the drive) then ... but the Z-Wave logs are verbose ...

 

1 hour ago, Comfortica said:

we probably could use z-sniffer in the system I guess?

You could buy a UZB3 stick, flash it with (free) Zniffer firmware and run the (free) Zniffer app. It would clearly show device X sending to device Y - if you are close enough to X and Y...

 

[Comfortica 17]

2 hours ago, petergebruers said:

The Fibaro Wall Plug (1st gen) can also cause this issue

 

Yes

 

No, they cannot. The controller is not a "Zniffer", it is not "promiscuous" meaning it cannot detect traffic from module X to module Y. Only traffic from the controller to a device and from a device to the controller will make it into the log.

 

I assume you are 100% sure, no "scene" or VD causes this?

 

No, not in simple and legal way. If it is a HC2, this is a "linux" system and the data is on a USB stick, so if you have the knowledge and want to take the risks (Fibaro will refuse all responsibility if you remove the drive) then ... but the Z-Wave logs are verbose ...

 

You could buy a UZB3 stick, flash it with (free) Zniffer firmware and run the (free) Zniffer app. It would clearly show device X sending to device Y - if you are close enough to X and Y...

 

Thanks for your (as usual) very informative post    We are aware of the less legal way to get the logfiles, but I did not realize that direct z-wave communication might not be logged at all. Best route would be the UZB3 stick, or the installer toolkit ? 

 

Does the old wallplug create ghost associations like the RGBW module? As in, only visible after a soft reconfiguration? 

[petergebruers 1,268]

15 minutes ago, Comfortica said:

Best route would be the UZB3 stick, or the installer toolkit ?

Don't know, I am not sure what is in the "installer toolkit".

15 minutes ago, Comfortica said:

Does the old wallplug create ghost associations like the RGBW module? As in, only visible after a soft reconfiguration? 

IMHO yes but it is been reported but it is rare. The only evidence I can find is "circumstantial" 

 

 

You need some context to understand that post. Before Fibaro introduced a firmware with a fix (2.7 for RGBW) the only option to make the "phantom" less annoying was to run a script. This script is still available and very academic but you do not need it to fix an RGBW, you should really run fw 2.7 instead of older version, and set a parameter to disable associations.

 

Anyway, when Jakub mentioned the first version of the script, it actually "scrubbed" the faulty associations on Wall Plugs, not RGBW. And that script came from Fibaro support iirc.

 

 

[Comfortica 17]

1 hour ago, petergebruers said:

Don't know, I am not sure what is in the "installer toolkit".

IMHO yes but it is been reported but it is rare. The only evidence I can find is "circumstantial" 

 

 

You need some context to understand that post. Before Fibaro introduced a firmware with a fix (2.7 for RGBW) the only option to make the "phantom" less annoying was to run a script. This script is still available and very academic but you do not need it to fix an RGBW, you should really run fw 2.7 instead of older version, and set a parameter to disable associations.

 

Anyway, when Jakub mentioned the first version of the script, it actually "scrubbed" the faulty associations on Wall Plugs, not RGBW. And that script came from Fibaro support iirc.

 

 

 I will investigate the wallplugs.... we have used the script for the RGBW before, but since the latest update on those units, it was indeed not needed anymore. thanks again!