Z-Wave Diagnostics

[Momos 103]

Hi,

 

The new page with Z-Wave Diagnostics is nice.  While there is no map of the actual routing, at least one can see if there are any nodes with failed communications.

What i do not understand is the number of frames information. It is supposed to give information about incoming and outgoing number of frames from a certain node to the hub.

 

Sometimes i see a Fibaro Motion Sensor having something like 1548 incoming / 25 outgoing frames in an hour.  What kind of information would the hub (HC3) be sending this motion sensor ?! 1548 frames send from the hub to the FGMS-001 seems way too much.  Plus, i see no reason for the hub to send anything to a motion sensor except routing info.  There are no lost frames, sensor is in direct connection to the HC3.

 

Thank you.

[Momos 103]

I see all kind of stuff i don't know how to interpret.

 

Just looked at a Fibaro Wall Plug: 478 incoming frames, 0 outgoing frames.  It's a wall plug that does nothing, it's always on and just measures the energy of a TV.  No associations, no scenes , nothing turns it off.  

Then how can it have so many incoming frames and none outgoing ? There should be at least the outgoing frames for hourly power reports.

 

@A.Socha can you please shed some light on this new diagnostic page ?

 

Thank you !

 

[A.Socha 133]

Hi @Momos

 

Wallplug

incoming frames - it is when device report status to hub. In your case probably most of them or all are energy (power) where device can report 6 reports in 1 minutes, rest are probably status, energy used

Why outgoing are 0 probably in this 1h there was no control from Hub or scene. If you change status or parameter, then you will see outgoing

Motion

If device was not added then probably your parameters are wrong and device reports a lot of reports to hub (so battery drain fast), look on parameters related with temperature and lux because only them can report a lot of

[Momos 103]

Thank you !  So from the node perspective: Incoming frames = communication to the hub, outgoing frames = communication from the hub.  Make more sense now.

 

 

[Martin_N 154]

Oh yes, of course. But it would require a small note directly in the GUI (next update?)

Anyway, I won't get rid of my Zsniffer just yet.

[A.Socha 133]

When you got sniffer and knowledge how to use it, you have a better tool. Because you see all communication, not only from one hub. You see errors on checksums, You see broadcast frames and explore frames. But for others who don't have sniffer and knowledge this tool is great progress how to improve their home network

[m.roszak 763]

4 hours ago, Martin_N said:

Oh yes, of course. But it would require a small note directly in the GUI (next update?)

Just wanted to confirm, this explanation is not enough?

Please login or register to see this attachment.

[Martin_N 154]

@m.roszak

And precisely because it's confusing, the way Momos got confused.

Yes, I have Zniffer, I have knowledge, I can analyze packets, I can analyze traffic in Wireshark... but as my colleague Socha wrote,... it is a tool for those who do not have Zniffer, who do not have knowledge.

Therefore, I would welcome a small note like:

Outgoing communication: Hub -> Device

Incoming communication: Hub <- Device