Z wave monitor to prevent freeze

[cag014 628]

Hi all,

I see that some users have downloaded

Please login or register to see this link.

script and I think it could be a good idea to share our data and know-how to optimize our Z-wave performance.

In my case I have manage to reduce Z-wave traffic from average of event per 1.7 sec. to 4.8 sec (24 hours monitoring, 78 physical devices, 382 IDs), but I don't know if this is a good number. It will be interesting if anyone could share  an average of his system. That way we can compare and might be to achieve the right number and stable performance which may be could prevent Z-wave freeze in the future.

I think average of Z-wave traffic somehow depends on number of the devices in the system and again I believe we need team work to find correct formula for that.

Few users have shared with me that they have found devices, which "bombarding" the traffic with unnecessary reports and they fixed the issue.

It could be very helpful to all of us to share our solutions and fixes...  we all can learn from others

If you think it could violate your privacy,   please ignore this message...

Thank you

 

 

[twannieguitar 6]

 

I meant including graph, like the data from cag014

 

 

 

1 hour ago, petergebruers said:

You mean output of Lua script? Save as text file on your computer then click on "choose files" at the bottom of your new post to upload and insert that file.

 

I meant including graph with the format like shown in the debug windows of the z-wave monitor scene.

[cag014 628]

To post here the data from Z-wave monitor, you need to take a snapshot of the debug window...

You can use Windows' built-in Snipping Tool for that...

Edited February 27, 2019 by cag014

[twannieguitar 6]

okay, thank you

[twannieguitar 6]

On 12/27/2018 at 12:15 AM, cag014 said:

Hi all,

I see that some users have downloaded

Please login or register to see this link.

script and I think it could be a good idea to share our data and know-how to optimize our Z-wave performance.

In my case I have manage to reduce Z-wave traffic from average of event per 1.7 sec. to 4.8 sec (24 hours monitoring, 78 physical devices, 382 IDs), but I don't know if this is a good number. It will be interesting if anyone could share  an average of his system. That way we can compare and might be to achieve the right number and stable performance which may be could prevent Z-wave freeze in the future.

I think average of Z-wave traffic somehow depends on number of the devices in the system and again I believe we need team work to find correct formula for that.

Few users have shared with me that they have found devices, which "bombarding" the traffic with unnecessary reports and they fixed the issue.

It could be very helpful to all of us to share our solutions and fixes...  we all can learn from others

If you think it could violate your privacy,   please ignore this message...

Thank you

 

Hi

Hi

I am not sure, do I need to change the following in the monitor? You mention to use an "_" but i see that only before "531" in the code... and what do these scene/device numbers represent in the result?

dev2review={false,"|470|804"}.
userDev={false,"|504|_531|"}

Edited February 27, 2019 by twannieguitar

[cag014 628]

You need to change all ID numbers to your IDs. It's just an example.

Use underscore "_" if it is scene ID. In the system scene and device could have same ID number, so assign underscore to distinguish between them.

This numbers used to review the Z-wave of specific IDs.

dev2review={false,"|470|804|"}.  - first variable is true or false (display or not the data chart). After that all numbers are device IDs to review actual readings of the devices (like power, energy, Lux, temperature. Devices with results of true/false won't be displayed). You can define devices only (no scenes allowed)

userDev={false,"|504|_531|"}  - same, first variable is true or false (display or not the data chart). After that all numbers of device or scene ID to review number of Z wave events of each ID. Here you need to use "_" for scene IDs.

 

For example:

Let's assume that you have wall plug with ID=600, temperature sensor ID=670. Scene ID=600 and another scene ID=200

Now to review actual results of wall plug and temperature sensor define as follow:

dev2review={true,"|600|670|"} You will see two charts for each device of actual results on timeline.

userDev={true,"|600|_600|"}  you will see one chart with two diagrams (device ID=600 and scene ID=600) of Z wave event numbers on timeline

 

See below example of Greenwave power node actual readings... this device is bombarding the Z wave traffic..

Please login or register to see this spoiler.

Looks much better, isn't?

This is a real example of my system. Without Zwave monitor I didn't have any tool to identify this heavy traffic.

 

 

 

 

[twannieguitar 6]

Quite happy with the results so far, moved from 0.9S to 5.2S by changing some energy measurement values

 

[DEBUG] 06:22:25: Z-wave Viewer v2.2

Please login or register to see this code.

id	total #	total %	value	power	batteryLevel	energy	targetLevel	color	mode	sceneActivation	unit	Device description
771	1603	34.5%		401		401					801	Netwerk & Domotica @ Hal
70	1152	24.8%		668		47		437				Mediahoek @ Woonkamer
475	405	8.7%	162						243			Verw Vloer presets @ Vloer Badkamer
772	398	8.6%	398									Netspanning @ Hal
241	234	5.1%		219		7		8				Laptop @ Woonkamer
76	93	2%		83		6		4				Verwarmingsketel @ Voorzolder
131	81	1.8%		57		7		17				Vriezer @ Bijkeuken
594	79	1.7%		79								Centrale Afzuiging @ Voorzolder
584	75	1.7%		75								Stopcontact A-deur @ Bijkeuken
74	62	1.4%		62								Wasmachine @ Bijkeuken
224	59	1.3%	59									Temp Schuur @ Schuur
623	50	1.1%	48		2							Lux Voor @ Voortuin
62	34	0.8%		22		4		8				Koelkast @ Keuken
498	31	0.7%	31									Temp 1 Keuken @ Keuken
322	30	0.7%	30									Temp Hal plafond @ Hal
32	27	0.6%	27									Temp Slaapkamer @ Slaapkamer
244	25	0.6%	8	16		1						Lamp Salontafel @ Woonkamer
613	18	0.4%	6	12								Spots Keuken @ Keuken
105	18	0.4%	18									Temp Werkbank @ Bijkeuken
447	16	0.4%	16									Sensor 2 Keuken @ Keuken
100	16	0.4%	8	8								Lamp Hal @ Hal
476	13	0.3%	13									Temp Vloer Badkamer @ Vloer Badkamer
518	12	0.3%	6	6								Lamp Nis @ Keuken
565	12	0.3%	4	8								Spots Badamer @ Badkamer
622	11	0.3%	9		2							Temp Voorraam @ Voortuin
789	9	0.2%		3		3		3				Waterkoker @ Keuken
86	9	0.2%								9		Minimote Zwart @ Controllers
497	8	0.2%	8									Sensor 1 Keuken @ Keuken
321	8	0.2%	8									Sensor Hal @ Hal
53	6	0.2%	2	4								Lamp Slaapkamer @ Slaapkamer
449	6	0.2%	6									Lux 2 Keuken @ Keuken
323	6	0.2%	6									Lux Hal @ Hal
114	5	0.2%	5									Temp Bijkeuken @ Bijkeuken
499	5	0.2%	5									Lux 1 Keuken @ Keuken
168	5	0.2%	5									Temp Plafond Keuken @ Keuken
124	4	0.1%	4									Sensor Badkamer @ Badkamer
126	4	0.1%	4									Lux Badkamer @ Badkamer
298	3	0.1%	3									Temp Zolder @ Zolderkamer
621	2	0.1%			2							Sensor Voor @ Voortuin
33	2	0.1%	2									Lux Slaapkamer @ Slaapkamer
294	2	0.1%	1				1					Thermostaat Badkamer @ Badkamer
641	2	0.1%	1	1								Lamp Afzuigkap @ Keuken
423	2	0.1%	1				1					Thermostaat Bijkeuke @ Bijkeuken
327	2	0.1%	2									Temp Achtertuin 2mtr @ Achtertuin
134	2	0.1%	2									Temp Afdak @ Afdak
50	2	0.1%			2							WS Eettafel @ Controllers
31	2	0.1%	2									Sensor Slaapkamer @ Slaapkamer
125	2	0.1%	2									Temp Badkamer @ Badkamer
329	1	0.1%	1									325.0.3 @ Achtertuin
500	1	0.1%	1									496.0.3 @ Keuken
217	1	0.1%	1									Temp Hal @ Hal
60	1	0.1%				1						Droger @ Bijkeuken
448	1	0.1%	1									Temp 2 Keuken @ Keuken
267	1	0.1%	1									Temp Vloer Keuken @ Keuken
34	1	0.1%	1									30.0.3 @ Slaapkamer

Please login or register to see this code.

 

[twannieguitar 6]

Thanks for the info cag04... great tool to identify!!

Edited March 1, 2019 by twannieguitar

[twannieguitar 6]

Hi cag04

 

I suddenly get this error when running the scene after restoring a backup

 

[DEBUG] 04:20:05: 2019-03-02 04:20:05.042977 [ fatal] Unknown exception: /usr/share/lua/5.2/json/decode/util.lua:35: unexpected character @ character: 1 0:1 [] line:
[DEBUG] 04:20:05:

 

any idea what is happening?

[cag014 628]

Yes, your global variable is corrupted or blank/empty (usually happens when the system is restarted/rebooted)

Please delete the global variable and run Zwave Monitor, it will create again correct global variable.

The global variable name is zwave_your_scene_ID

I've fixed this in next release....

Edited March 2, 2019 by cag014

[twannieguitar 6]

done.... thanks!!

[Cafun 13]

Thank you cag014!

 

My results are not bad at all. I was expecting worse

Of course I'm going to look at a few devices which are reporting to many times (in my opinion).

 

Elapsed time = 24:00:14 [ Apr 14 20:40 - Apr 15 20:41 ]

Sample log rate = 1 minutes. Total samples 1441
Z-wave events = 8144 on 118 devices.
Average traffic = 10.7 sec.
Z-traffic range = 1.4 - 90 sec.
Repeat / Report = 3596^(44.1%) on 105 devices.

 

id	total #	total %	rpt	value	timestamp	targetLevel	batteryLevel	dead	deadReason	power	energy	currentProgram	currentProgramID	color	lastColorSet	brightness	mode	tamper	sceneActivation	Device description
67	1504	18.5%	1438														66			Actuator @ Attic
230	996	12.3%	18							975	3									Smartwatch C @ Master bedroom
167	605	7.5%	55	11						539										Spots Badkamer @ Bathroom
319	226	2.8%		226																6in1 @ Kitchen
201	202	2.5%	3	199																Lux Badkamer @ Bathroom
318	201	2.5%		201																6in1 @ Kitchen
317	189	2.4%		189																6in1 @ Kitchen
91	180	2.3%	5	174			1													Licht Gang @ Hallway
64	176	2.2%	6	170																Beweging Lux @ Living
372	174	2.2%								172	2									Wasmachine @ Attic
132	173	2.2%	24	24						74	1	4	4	16	10	16				LED Keuken @ Kitchen
374	166	2.1%		166																Wasmachine @ Attic
96	161	2%	6	155																Beweging Overloop @ Overloop
73	139	1.8%	63	57			19													Temp Woonkamer @ Living
18	135	1.7%	12	2						119	2									TV @ Living
50	111	1.4%	85	2						23	1									Smartphone A @ Master bedroom
62	108	1.4%	7	101																Beweging Woonkamer @ Living
177	96	1.2%	37	59																Luchtvochtigheid @ Bathroom
72	95	1.2%	64	4	4	4	19													Thermostaat @ Living
89	89	1.1%	5	81			1											2		Motion hallway @ Hallway
176	82	1.1%	37	45																Temp Badkamer @ Bathroom
94	82	1.1%	6	76																Beweging Overloop @ Overloop
350	79	1%	79																	KerstRaam @ Living
223	78	1%	39	39																Temp Slaapkamer1 @ Nursery
52	77	1%	77																	Deken A @ Master bedroom
191	76	1%	29	15								2	2	12	6	10				Led Meterkast @ Meterkast
54	74	1%	74																	LaptopC @ Living
82	67	0.9%	31	13										10	5	8				Led Slaapkamer @ Master bedroom
158	64	0.8%	64																	CO Zolder @ Attic
168	55	0.7%	55																	160.1 @ unassigned
169	55	0.7%	55																	160.2 @ unassigned
199	53	0.7%	3	48														2		Beweging Badkamer @ Bathroom
231	44	0.6%	18	2						23	1									Smartphone C @ Master bedroom
209	43	0.6%	34	4						5										Dressoir Lamp @ Living
316	43	0.6%		43																6in1 @ Kitchen
17	42	0.6%	12							21	9									Horizon @ Living
228	40	0.5%	18							11	11									Wekker C @ Master bedroom
139	39	0.5%	30	9																Lamp Gang @ Hallway
222	38	0.5%	38																	220.1 @ unassigned
221	38	0.5%	38																	Dakterrasdeur @ Nursery
178	37	0.5%	37																	Everspring @ Bathroom
179	37	0.5%	37																	Everspring @ Bathroom
335	35	0.5%	4	31																Rookmelder Baby Temp @ Nursery
16	35	0.5%	12							7	16									Home Cinema @ Living
83	31	0.4%	31																	81.1 @ unassigned
84	31	0.4%	31																	81.2 @ unassigned
87	31	0.4%	31																	81.5 @ unassigned
86	31	0.4%	31																	81.4 @ unassigned
85	31	0.4%	31																	81.3 @ unassigned
141	30	0.4%	30																	Buitenlamp voor @ Driveway
140	30	0.4%	30																	138.1 @ unassigned
294	29	0.4%	29																	292.1 @ unassigned
194	29	0.4%	29																	118.3 @ unassigned
192	29	0.4%	29																	118.1 @ unassigned
196	29	0.4%	29																	118.5 @ unassigned
195	29	0.4%	29																	118.4 @ unassigned
295	29	0.4%	29																	BelGong @ Hallway
193	29	0.4%	29																	118.2 @ unassigned
293	29	0.4%	29																	Doorbell @ Driveway
233	28	0.4%	18							2	8									Bed Corné @ Master bedroom
40	28	0.4%	28																	Beschikbaar @ unassigned
135	24	0.3%	24																	LED Keuken @ Kitchen
133	24	0.3%	24																	LED Keuken @ Kitchen
76	24	0.3%		24																RM Temp @ Hallway
136	24	0.3%	24																	LED Keuken @ Kitchen
134	24	0.3%	24																	LED Keuken @ Kitchen
137	24	0.3%	24																	LED Keuken @ Kitchen
19	20	0.3%	12	2						4	2									Subwoofer @ Living
171	20	0.3%	16	4																Ventilation @ Bathroom
373	20	0.3%		20																Wasmachine @ Attic
232	18	0.3%	18																	Deken C @ Master bedroom
229	18	0.3%	18																	Lamp C @ Master bedroom
227	18	0.3%	18																	226.0 @ unassigned
200	17	0.3%	3	14																Beweging Temp @ Bathroom
361	17	0.3%	1	16																Rookmelder temp @ Overloop
63	17	0.3%	6	11																Beweging Temp @ Living
172	16	0.2%	16																	170.1 @ unassigned
173	16	0.2%	16																	170.2 @ unassigned
57	15	0.2%	7	8																RM Temp Woonkamer @ Living
30	14	0.2%	14																	Balkondeur @ Master bedroom
12	13	0.2%	7	6																Frontdoor @ Hallway
20	12	0.2%	12																	Greenwave6 @ Living
14	12	0.2%	12																	Greenwave @ Living
127	12	0.2%	5	7																Temp Slaapkamer CA @ Master bedroom
15	12	0.2%	12																	Raspberry Pi @ Living
26	11	0.2%	11																	Raam Woonkamer @ Living
95	10	0.2%	6	4																Temp Overloop @ Overloop
225	10	0.2%	10																	Raam MB @ Master bedroom
28	9	0.2%	9																	Tuindeuren @ Living
339	9	0.2%	4	5																Rookmelder MB Temp @ Master bedroom
125	9	0.2%	6	3																Slaapkamerdeur MB @ Master bedroom
299	8	0.1%	3	5																Rookmelder Temp @ Attic
90	8	0.1%	5	2			1													Temp gang @ Hallway
97	7	0.1%	7																	93.0.3 @ unassigned
56	7	0.1%	7																	Rookmelder Woonkamer @ Living
58	7	0.1%	7																	Rookmelder Woonkamer @ Living
65	6	0.1%	6																	61.0.3 @ unassigned
126	5	0.1%	5																	114.1 @ unassigned
92	5	0.1%	4				1													88.0.3 @ unassigned
338	4	0.1%	4																	Rookmelder MB @ Master bedroom
343	4	0.1%						2	2											Dakraam @ Attic
380	4	0.1%	4																	Keukendeur @ Kitchen
333	4	0.1%	4																	Rookmelder Babykamer @ Nursery
346	4	0.1%	4																	Lekkage Zolder @ Attic
334	4	0.1%	4																	Rookmelder Babykamer @ Nursery
381	4	0.1%	4																	Keukendeur @ Kitchen
347	4	0.1%						2	2											Dakraam @ Attic
342	4	0.1%						2	2											Dakraam @ Attic
337	4	0.1%	4																	Rookmelder MB @ Master bedroom
345	4	0.1%	4																	Lekkage zolder @ Attic
202	3	0.1%	3																	198.0.3 @ unassigned
298	3	0.1%	3																	Rookmelder Zolder @ Attic
297	3	0.1%	3																	Rookmelder Zolder @ Attic
366	2	0.1%		2																Belknop Keypad @ Meterkast
24	2	0.1%	2																	Sirene @ Meterkast
79	1	0.1%																	1	Minimote @ Master bedroom
359	1	0.1%	1																	Rookmelder overloop @ Overloop
360	1	0.1%	1																	Rookmelder overloop @ Overloop

 

Edited April 16, 2019 by Cafun

[cag014 628]

The result of

Repeat / Report = 3596^(44.1%) on 105 devices.

is extremely high (should be less  than 10%).

 

Please check deviceID 67,looks like you send to many same commands. For example if the device is ON, your code continue to send turnOn command.

It could be that you're using block scene to activate this device, in this case I suggest to use LUA code and to verify the device state before sending command.

My guess that some motion sensor triggering your scene to control this device.

[Cafun 13]

Thanks for your reply.

Wel no actually. deviceID 67 is my heating (Horstmann SSR303 & SRT321). It indeed turns on/off a lot. Next week my house will be isolated, so then it should be less

 

In all my code I check if something is on already and it should not send the turnOn command again. But I'm gonna double check my code (I only use lua).

 

Thanks again.

[Aleksandr Meinson 2]

Please login or register to see this image.

/monthly_2019_05/Untitled1.png.5bb2c755b6d1841e29ca93544c7530f3.png" alt="Untitled1.png.5bb2c755b6d1841e29ca93544c7530f3.png" />An example of how the patient's heart stopped

Please login or register to see this attachment.

Please login or register to see this attachment.

Instant death.

[Aleksandr Meinson 2]

Hello. In order to reduce the load on the HC2, I added NSL, transferred to it energy counters and temperature sensors from the heat pump.
In your scanner, these data are combined, the data from the HC2 and NSL. But this does not mean that it is a load on one Z -Wave chip?

NSL = HCL

translator 

[Phantome46 0]

I have run Z wave monitor on my system, and here are the results. I am a real novice so don't know if the issues or crashing is related this this performance 

 

I look forward to feedback

 

 

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

[cag014 628]

Looks like you Z-traffic is not overloaded... but you have Repeated/Reported Z-traffic over 50%!!!

Looks like you send too many same commands to devices...

Please check status of the device before sending command.

 

Interesting, how many Z-wave crashes you have ? I mean what is the crashes frequency ( once per day, week, month...)

[Phantome46 0]

1 hour ago, cag014 said:

Looks like you Z-traffic is not overloaded... but you have Repeated/Reported Z-traffic over 50%!!!

Looks like you send too many same commands to devices...

Please check status of the device before sending command.

 

Interesting, how many Z-wave crashes you have ? I mean what is the crashes frequency ( once per day, week, month...)

The system seems to crash about every 2 weeks. Sometimes once or twice within a couple of days and then it settles down again. 

 

Can this be avoided? Reduce all this traffic? 

[cag014 628]

Are you using block scenes?

 

[Phantome46 0]

6 hours ago, cag014 said:

Are you using block scenes?

 

I will be honest to say that I did not write my system I paid a professional to do it, but due to having problems for over a year I decided to try and take matters into my own hands.

 

I don't know what a block scene is and also how to use them?