Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Z-wave monitor 3.0

   (13 reviews)

7 Screenshots

About This File

This scene monitors and catches Z-wave commands traffic between controller and devices. The data displayed to user as a table which includes total commands and their properties per device, in addition same data displayed at graphical chart and shows system activities over the time. Since Z-wave protocol is not a fastest one  (in many case it's just freeze) this code helps to analyze the data and to take necessary actions to reduce overall Z-wave traffic and system load.

Scene functionality

1. This is not an auto started scene. You need to start it manually. While the scene is running, you can switch views  between table/chart and  monitor (follow instructions on screen).

2. User configurable parameters are:

gVar = true-- Create and use global predefined variable. The scene could work with local table as well, but by using global parameter you can keep history of the traffic. It very helpful when you're updating the system to new release, to compare Z-wave performance. In case you have decided to use global variable, copy the data to other variable to keep the history. To view data of saved variable please download and use Z-wave Viewer scene.  Z-wave Viewer could be executed in parallel to Z-wave Monitor as well (when using global variable only)

logRate = 5     -- Time rate in minutes to log Z-wave activity. Used as axis X scale in charts view. Reasonable value 5 to15 minutes for 24 hours of monitoring. In case to achieve better resolution the value could be decreased down to 1 minute.
time2monitor = 6   -- Time-slot in hours to monitor z-wave traffic, after that time, table and chart will be displayed on debug window and scene will stopped. Value of  0 hours disables auto ending. User needs to stop the monitoring. If less than hour monitoring required please use decimal fraction. For example to set monitor time to 15 minutes set, time2monitor = .25

 markId = "|0|0|", " Cyan" -- Devices (IDs) list and text color to display specific devices in defined color at monitor view for follow up purpose. In few cases you need to monitor specific device, so fill-in the device ID and it will be highlighted by different color from other devices.
deadOnTop = {true, "maroon"}  -- Display DEAD devices on top of the monitor view list in defined text color. Since we're not always looking on the screen, so in case the system will identify dead device it will continuously display the device (in red) on debug window.

 

All variables below are the same for Z-wave Monitor  and  Z-wave Viewer
chartHeight = 100        -- Chart height in percents (%). Chart's default height fits debug window.  The variable changes height of all charts (devices.scenes and events)
chartWidth = 100         -- Chart width in percents (%). Chart's default width expands according to number of samples.  User could expand the width  to get better detail view or to stretch to visualize the load on time axis or to take snap shot of entire time line. The variable changes width of all charts (devices.scenes and events)

 

topDev2disp = 6          -- Number of most active devices to display on devices chart.  If set to zero chart won't be displayed.
topScene2disp= 10        -- Number of most active scenes to display on scenes chart. If set to zero chart won't be displayed.

darkSkinMode = true      -- Charts display skin mode. Set false for light (white) skin.

dev2review={false,"|470|804"} -- Generate chart for every device in list of actual device readings over the monitoring time. For devices with two results (like power and energy) both reading will be displayed. On left and right sides of the chart  applicable scale displayed. Please note, no chart is generated for devices like motion, door and any other sensors, which provide values of true/false.
userDev={false,"|504|_531|"} -- User defined devices and scenes IDs to generate specific combined chart. Please write underscore before scene ID |_531| 

stackedChart=true        --  A stacked line chart is an line chart in which lines do not overlap because they are cumulative at each point. Set to false to view standard line char. All charts except ZKG chart (events,CPU and RAM) will be displayed according to this variable.

 

 

 

Brief explanation what is displayed:

1. Monitor view

Spoiler

Monitor.thumb.PNG.03a79c7e67f6ed17b938e4a6816358cc.PNG

This snap shot includes top and dead devices marked in different color from other devices.

Two main sections in this view:

Header

             1:08:07/ 6:00:00               1824 events/77 devices            event/2.3s               (Click Start for )

    Elapsed Time/Monitoring time             Number of Z-wave events/devices          Z-wave traffic rate        Click to switch to table/chart view

               

Devices list

Every device displayed at follow format -

 #2/34TV509@Salon(216.7 power

#2/34 -First number is number of events during logRate slot. Second number is total number for events so far.

TV509@Salon - device name, ID and room name

(216.7 power) - actual reading and reading property

 

 

2. Table view

Spoiler

Capture.thumb.PNG.b5997f3c8e4aa29e1831a47c8ede2f31.PNG

total # - number of total Z-wave events on device

total %  - Percentage of device's events of total system Z-wave events.

All yellow marked headers are received Z-wave properties, except two properties, dead and deadReason which are marked in red. For each device displayed the total number of this specific properties. Red marked ID, means that device was or is "dead" 

By hovering mouse over device IDs, device and room names will be display (tool-tip) at popup box.

At the end displayed few extra summaries 

Spoiler

Capture1.PNG.8065d5ab4803b5c68ddef7ddcf2a9871.PNG

 Elapsed time and Start-End timestamps

Sample log rate as defined by user. Total samples during monitoring time

Total Z-wave events and total number of active devices

Average Z-wave traffic rate

Z-traffic range. Shows the highest and lowest z-wave activities during monitoring time.

If dead devices have found, list of them is displayed

 

3. Most active devices chart

Spoiler

Capture.PNG.e90b7a56fa3058c789857fa0fb5ffdc1.PNG

Spoiler

Capture.thumb.PNG.f369d5fdde5948a8cabf0de9622d4d68.PNG

Example of stacked chart

This chart shows events number of most active devices ( up to number of all active devices allowed by setting topDevNum variable ) on monitoring time-line. On the right-upper corner displayed ID, name and room of the device. By hovering mouse on diagrams or legend, selected item will emphasized in bold to make the item more visible.

 

4. Most active scenes chart

Spoiler

Capture1.thumb.PNG.e38fafcb73177760815771169191cb2e.PNG

This chart shows triggers number of most active scenes ( up to number of all triggered scenes allowed by setting topDevNum variable ) on monitoring time-line. On the right-upper corner displayed ID, name and room of the scenes. By hovering mouse on diagrams or legend, selected item will emphasized in bold to make the item more visible.

5. Review device's actual readings - (dev2review)

Spoiler

Capture.thumb.PNG.f1fd2093d8d91a7f1dec7382596a7170.PNG

For devices with two results (like power and energy) both reading will be displayed. On left and right sides of the chart  applicable scale displayed.

This chart most useful to identify  if device configured to send reports interval at high rate and " differ in readings to send report" set to very low value.

By hovering mouse over the chart, will scale down the diagram to make visible entire range. In case the horizontal scrollbar is not in the middle of the chart , the diagram will flicker.

  

 

 

6. User defined combined chart

Spoiler

Capture.thumb.PNG.f2aa40a059c15f756bf6a3c7416ec0c9.PNG

In some cases we  need to inspect behavior of some devices and scene that triggered by the device. This chart shows user defined devices and scenes on monitoring time-line. On the right-upper corner displayed ID, name and room of the scenes and/or device. By hovering mouse on diagrams or legend, selected item will emphasized in bold to make the item more visible.

 

 

 

7. ZKG Chart View

Spoiler

Capture.thumb.PNG.70eb773105c5db8d90d4045e1c22b3a2.PNG

Chart view shows Z-wave traffic and system load on time line (based on logRate value). You actually could see your smart home beating heart (like EKG). I have named as ZKG (Z-wave cardiogram). Now it's possible to see the "rush" and "quiet" hours of the system.

Chart view includes 5 diagrams displayed over time-line of monitoring period. The diagrams are:

  1. Z-wave events
  2. Triggered scenes
  3. CPU1  percentage
  4. CPU2  percentage
  5. RAM  percentage

At top-right corner of the screen, displayed legend of the diagrams and colors.

Events total number in same color as a diagram line.

CPU1 min  > avg < max in same color as a diagram line.

CPU2 min  > avg < max in same color as a diagram line.

RAM min  > avg < max  in same color as a diagram line.

Triggered scenes total in same color as a diagram line.

Most triggered scene ID  and scene's name in same color as a triggered scenes

In case dead devices have found during the monitoring period, the time stamp where it happened will colored red and at the top of the screen, directly above the time stamp, dead device(s) ID displayed.

Axis Y has two scales. Left scale  represents occurrence numbers of Z-wave events and triggered scenes. Right scale is a percentage and it related to CPU1, CPU2 and RAM measured values.

By hovering mouse on diagrams or legend, selected item will emphasized in bold to make the item more visible.

I'm strongly advising to use global variable and to view the data using Z-wave Viewer in parallel to Z-wave Monitor

The idea behind, that you can change parameters to view different devices/scenes on the fly.

By changing user configurable parameters in Z-wave Monitor you'll need to start the scene all over again.

Note:

The debug text of these scenes is very big, so If you're using Clear Debug scene, please remove these scenes from the list.

 

Please let me know if extra info is required.

Please report if any bug occurred.


What's New in Version 3.0   See changelog

Released

Bug fix:

1. System reboot initializes Zwave global variable to blank.

 

New features:

Added monitoring of "hidden" communication for repeated,report and pooling Zwave traffic.

The data displayed as "rpt", new column in table

Repeated traffic, means that the user code sends same command over and over to device. In this case device broadcasts back with report status of all his logical endpoints and creates unnecessary load on Zwave traffic. ( Please see Reduce Ztraffic  file at download center https://forum.fibaro.com/files/file/246-reduce-ztraffic-fibaro_call/ ).

Added monitoring of failed communication packets between device and controller (Transfer failed). The data displayed on the table at " nack " new column. This data implies on bad communication to device due to range or something blocks the Zwave ( like walls).

 

Added at end of the table summary of prt and nack measurements



User Feedback

Recommended Comments



Corrupted because of the recalled FW update that happened about a year ago at Fibaro. I was one of the few who suffered data loss. I'm still missing a feature that Fibaro still could not find a way to reinstall... I posted all this on the forum in many topics. However, I'm using the latest stable version 4.570 and waiting for Fibaro to repair my system... Hope they will be able to do it.

Link to comment
Share on other sites

Sorry to hear it. But if your devices are working and react , Zwave monitor should work either.

Link to comment
Share on other sites

Nevermind... it's my bad luck.

This is the reason I'm struggling to find a way to locate the problems in my network, devices stuck, not responding, not syncing, etc. So I'm trying all possible detector codes, like your very useful Z-Wave monitor. I hope I can get it to work somehow :)

Thank you for your support!

Link to comment
Share on other sites

Probably most stupid question... you have tried to perform full recovery?  w/o loading the backup, but just to add few devices and to see if it works properly.

Any how hope Fibaro support will repair your system soon.

Link to comment
Share on other sites

I didn't think of that, it is a very good idea! I would like to try that.

But I'm a little afraid I won't be able to reload my backups if I start configuring from scratch... What if it won't recognise them, or some data conflict occurs... I have sad memories about my lost backup because of that recalled FW... Even Fibaro wasn't able to find it.

Link to comment
Share on other sites

If you can to exclude from current configuration,  let's say "not important" device for you and use it for test.

Later you can restore backup and to include device back into system.

Link to comment
Share on other sites

I could do that. I have many devices still not included.

If I restore to factory defaults (start from scratch), will it allow me to use the same user login ID and let me use backups from cloud or local? I've never done this before...

Link to comment
Share on other sites

Guest cag014

Posted (edited)

after recovery the login credentials are admin admin

when you will be on 4.570 version you can restore the latest backup and see if your problems gone. All your data should be the same as now

 

Edited by cag014
Link to comment
Share on other sites

Guest cag014

Posted (edited)

If you still have problems then try the second option.

  1. Copy your scene and export VDs.
  2. Perform full recovery again. 
  3. When you on 4.570 version do not restore backup.
  4. Add few new devices and see if it works properly.
  5. If everything works properly follow next steps, if not you need fibaro support.
  6. Paste your previously copied scenes and import VD.
  7. You need to re-include all your devices again. Painful process.
  8. Go trough all your code to set new IDs (devices, scenes and VDs)

 

Hope recovery and backup restore will work for you and you don't need the second option

 

 

Edited by cag014
Link to comment
Share on other sites

Thank you for the detailed advices! I will try them out today and run your monitor code to see if it will show any traffic.

Can I set it to run only for 10-20 minutes, instead of default 6 hours? I will wake all devices to force traffic.

Link to comment
Share on other sites

Guest cag014

Posted (edited)

Yes any time. for 20 minutes set to 0.3

By the way, it doesn't matter for how long you set Zwave monitor, you can stop it anytime and to review collected results so far.

Edited by cag014
Link to comment
Share on other sites

I have successfully reset my HC2 (2 times, to make sure...) and restored backup - now I'm back to normal. Thank you!

I am doing mesh reconfiguration, then restarting your Z-Wave monitor...

Link to comment
Share on other sites

On 1/25/2020 at 4:43 PM, cag014 said:

Great news.

So you don't see any previous "bad" behavior of the system?

Unfortunately there are still bad behaviours, so I have to dig deeper. But now I'm smarter :) thanks to you guys!

 

Do you know about any LUA scene which arms/disarms that  big slider on the alarm panel? ;)

 

Link to comment
Share on other sites

You need to arm needed sensors one by one  using steamed or forearm commands.

To disarm use setArmed, 0.

Link to comment
Share on other sites

14 hours ago, cag014 said:

You need to arm needed sensors one by one  using steamed or forearm commands.

To disarm use setArmed, 0.

Thank you. This way, I suppose, if there is any change in sensor IDs, I have to edit the scenes.

 

Unfortunately I'm not into LUA yet, but disamring seems straightforward :) Thx!

 

I don't know why, but I was sure there is some workaround or script, to handle all available sensors together, like the alarm panel slider does... :(

 

 

 

Edited by johndeere
Link to comment
Share on other sites

There is another way to do it, to use fibaro:callGroupAction(action, filters).  You can find how to use in follow link

https://manuals.fibaro.com/content/other/FIBARO_System_Lua_API.pdf

Since you need to define fillers to identify devices that could be armed, to   my opinion is the same as you doing one by one.

By the way take a look at All-in-One Scene (in downloads) it could make your life easier. Need to set device ID in one place only. See an example

 

 

Link to comment
Share on other sites

On 1/31/2020 at 12:04 AM, cag014 said:

There is another way to do it, to use fibaro:callGroupAction(action, filters).  You can find how to use in follow link

https://manuals.fibaro.com/content/other/FIBARO_System_Lua_API.pdf

Since you need to define fillers to identify devices that could be armed, to   my opinion is the same as you doing one by one.

By the way take a look at All-in-One Scene (in downloads) it could make your life easier. Need to set device ID in one place only. See an example

OK, I will try to find some more time to dig deeper in the All-in-One scene. Thanks for suggesting it as a possible solution for my question :)

 

 

Link to comment
Share on other sites

By the way, after struggling some more days with reconfigurations, I still have this window:

 

image.png.c7354b9be9b4cf93123be750fc738016.png

 

And seems that the number of dead routes hasn't grown after some more reconfigs...

 

image.png.ea87240bbc6695a6e8c91909ce47d951.png

 

I'm getting more and more tired of this hassle, but I'm not giving up yet. Thanks for every help!

Link to comment
Share on other sites

Guest cag014

Posted (edited)

It's not "real"... looks like no Zwave activities at all.

Could you please restart Zwave monitor?

Could you please post Z-Range table? One of the columns shows Zwave activity of each device.

Edited by cag014
Link to comment
Share on other sites

12 minutes ago, cag014 said:

It's not "real"... looks like no Zwave activities at all.

Could you please restart Zwave monitor?

Could you please post Z-Range table? One of the columns shows Zwave activity of each device.

I restarted HC2 several times yesterday during reconfigs... Is that enough for the Zwave monitor to restart?

 

There must be traffic, because sensors send triggers (at least most of the time...)

 

image.png.556caa53958ad750b98b8f12f3e52bbe.png

 

Sorry, I don't know which column is that. I might be on the wrong place, I'm afraid...

 

image.png.fedcc0f09ee4c373fa4d17df26e1f5c8.png

Link to comment
Share on other sites

Guest cag014

Posted (edited)

13 minutes ago, johndeere said:

I restarted HC2 several times yesterday during reconfigs... Is that enough for the Zwave monitor to restart?

By default Zwave monitor doesn't start automatically.. unless you have changed the configuration. According to your post it runs 241 hours!

Looking on your events panel, an average of Z-traffic is 69 seconds, which means your traffic is extremely slow and takes a long time to collect Zwave data.

13 minutes ago, johndeere said:

 

Sorry, I don't know which column is that. I might be on the wrong place, I'm afraid...

 24History column.

Edited by cag014
Link to comment
Share on other sites

4 minutes ago, cag014 said:

By default Zwave monitor doesn't start automatically.. unless you have changed the configuration. According to your post it runs 241 hours!

I used the Stop then Start buttons, but as long as it says variable in use, I thought it runs fine...

image.png.8ad396c449038ef4685ee878a416cf2f.png

4 minutes ago, cag014 said:

 

24History column.

image.png.c8e07c937fad3cba2fd18b60fc406040.png

Link to comment
Share on other sites

As you can see your Zwave traffic is very slow. The purpose of Z-wave monitor is to track down high traffic that crashes/freezes the system, which is not the case in your system.

I'll try to change Zwave monitor to track slow traffic and will post the code for you to see what happens.

Just out of curiosity, could you post the the highest active device in 24History column.

 

Link to comment
Share on other sites

20 minutes ago, cag014 said:

As you can see your Zwave traffic is very slow. The purpose of Z-wave monitor is to track down high traffic that crashes/freezes the system, which is not the case in your system.

I'll try to change Zwave monitor to track slow traffic and will post the code for you to see what happens.

Just out of curiosity, could you post the the highest active device in 24History column.

 

Please find below the highest values. Only 2 devices are red in colour:

image.png.7d0eb1a7178242881f39b0ebf1b127c5.png

 

I don't know how much work does this modfiication need, and I wouldn't really want you to spend too much of your time on it... :)  However I am grateful for the help and thank you very much!

Link to comment
Share on other sites


Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...