Z-Wave Network struggling when two FGMS are trigger of a same scene

[J3R3M 12]

Hi all,

 

I have a short issue when I try to use more than one FGMS to trigg a single scene on HC2.

Everything's working well with only one FGMS, no matter which one. But when two or more FGMS are used as trigger in my room scenes, the Z-Wave Network struggles and often becomes slow.

When it's happening, the HC2 interface is undefinitely loading and I cant access to anything... Until the scene is triggered.

Sometimes, this slow-down lasts one or two minutes, before all others actions which was waiting finally execute.

 

There are my FGMS parameters :

- 1 - Motion detection - sentivity : 22

- 2 - Motion dection - blind time : 14

- 3 - Motion detection - pulse counter : 1-2 pulses

- 4 - Motion detection - window time : 2-12 seconds

- 6 - Motion detection - alarm cancellation delay : 1s

- 8 - Motion detection - operating mode : 0 PIR sensor always active

- 9 - Motion detection - night/day : 200lux

- 12  - BASIC command classe configuration : 1 - only the BASIC ON

- 14 - BASIC ON command frame value :  255

- 16 - BASIC OFF command frame value : 0

- 18 - Associations in Z-Wave network Security Mode - All group sent as secure

- 20 - Tamper - sensitivity : 0

- 22 - Tamper - alarm cancellation delay : 1s

- 25 - Tamper - alarm cancellation : 0 - Do not send tamper cancellation report

- 28 - Tamper - broadcast mode : 0 - tamper alarm sent to 3rd association group

- 29 - Tamper - backward compatible broadcast mode : 0 - backward compatible tamper alarm sent to 5th association group

- 40 - Illuminance report - threshold : 10lux

- 42 - Illuminance report - interval : 5min

- 60 - Temperature report - threshold : 0,5°C

- 62 - Temperature measuring - interval : 5min

- 64 - Temperature report - interval : 0 - periodical reports are not sent

- 66 - Temperature offset : 0°C

- 80 - Visual LED indicator - signalling mode : 0 - LED inactive

- 81 - Visual LED indicator - brightness : 1%

- 82 - Visual LED indicator - illuminance for low indicator brightness : 0lux

- 83 - Visual LED indicator - illuminance for high indicator brightness : 1lux

- 86 - Visual LED indicator - temperature for blue colour : 0°C

- 87 - Visual LED indicator - temperature for red colour : 30°C

- 89 - Visual LED indicator - tamper alarm : 0 - tamper alarm is not indicated

 

There is my LUA scene :

Please login or register to see this code.

 

Has anyone any idea ?

Thanks ?

 

[J3R3M 12]

Hi, am I the only one who meet this issue ? ?

[petergebruers 1,268]

11 minutes ago, J3R3M said:

Hi, am I the only one who meet this issue ? ?

Probably...

 

You did a very good job posting all that information. Yet no answer indeed............ I think the reason for that is that it is difficult to replicate your problem.

 

1) Reduce your scene to the bare minimum to reproduce the problem. There is *no way* anyone could test such a complicated scene, other users do not have your devices and setup, it would take quite some effort and might not exactly replicate anyway.

 

2) Try to avoid "killOtherInstances", it might be related. I am not sure it is stil valid on recent HC2 firmwares (posts below are from 2020), I run my scenes on HC3 and it implements scene triggers in a different way and does not have this issue.