Invalid Polling time interval ?

[Markoe 1]

I suddenly get this message to the Notification center. Does this mean device ID 21 or 21 devices.

 

What parameter should I chance?

 

 

Invalid polling time interval

It is highly recommended to increase devices polling time interval.
This notification will be discarded after you increase devices polling time interval.
Number of devices: 21. Recommended devices polling time interval: 300s.

[drboss 107]

You need change the on page "http://192.168.1.x/fibaro/en/configuration/zwave.html" Devices polling time interval. The proposition is calculated by HC2 depends of z-wave devices number registered in your network. Generally device send to HC2 state every time if changed or by interval set in property of device. After restart  HC2 prior 4.160  not check state of device and displayed last state before shutdown, it do it sequentially. It use too the pooling time to check state of any (relay, sensor ect) if they are out of range in the moment of changing or havn't good association to master controller.  From 4.160 the startup pooling work fine and if our device have good configuration of association group 0 (to HC2 controller) and individual polling time for most important device is set in detail configuration page of device you will set this to proposed time or disable (version 4.162).

Lowest polling time generate big and unnecessary traffic on the network and introduces delays in the operation of devices

[Bodyart 231]

IMHO Fibaro HC shoul'd automatically change the polling interval as recomended instead of notifying only.

 

this is my RFC @I.Srodka @T.Konopka

Edited March 21, 2018 by Bodyart

[drboss 107]

 

@Bodyart, @I.Srodka, @T.Konopka

I not sure if idea for auto change of polling time is good. I prefer to change this manually.

For ex. if you have big z-wave network with only small group of device with polling by global parameter set and other devices have time poll set to disable (use only association update) or to individual time you set this timer to other value that if you use global timer to all devices. This very good parameter to optimize z-wave network if you manage polling time in network individual or by groups of devices.

[Markoe 1]

Ok found the Place the parameter was 125 and I did set it to 300.

 

IMHO The error shoud point more clearly where and what to update.

 

Thanks for pointing me to the right direction ... I was after  device 21 parameter

Edited March 21, 2018 by Markoe

[I.Srodka 4]

21 hours ago, Bodyart said:

IMHO Fibaro HC shoul'd automatically change the polling interval as recomended instead of notifying only.

 

this is my RFC @I.Srodka @T.Konopka

FIBARO will not be changing that automatically.

 

It's hard to tell whether this change was done on purpose or what's the reason for that.

 

I know you will probably suggest "the option to disable automatic change" but that's basically an argument for every more or less necessary change. 

[jakub.jezek 370]

21 hours ago, Bodyart said:

IMHO Fibaro HC shoul'd automatically change the polling interval as recomended instead of notifying only.

 

this is my RFC @I.Srodka @T.Konopka

If so, then only increase polling interval. But i rather have manual change, since i teach Fibaro dealers, that come to Fibaro training, where to find polling interval and change it when it is neccessary.

 

I would personally add +100 seconds even if Fibaro increase number automatically. But it depends on Network.

[Bodyart 231]

Hi @jakub.jezek,

 

ofcourse everybody knows where to change polling interval , but ...

When HC notifies me, that i have a wrong polling interval, it requires me to change it, so why bother me, when i cn be done automatically???

Unless you have disabled the polling.

Edited March 22, 2018 by Bodyart

[petergebruers 1,268]

42 minutes ago, Bodyart said:

When HC notifies me, that i have a wrong polling interval, it requires me to change it, so why bother me, when i cn be done automatically???

 

This is highly academic, so forgive me if I sound pedantic. Some old, very old devices do NOT report status. It has to do with an old patent issue. If I user owns such devices, he might have set global polling to something rather low, let's say 2 minutes, to get a "fairly accurate" idea when a user used a local switch to change state. This user might not be happy if the system automatically changed that to polling to 5 minutes. In 2013 I accidentally bought such a device, I immediately sent it back

 

If you want some background on wake up and polling:

 

 

Edited March 22, 2018 by petergebruers