ZWave Debugging (check the mesh, routing and signal quality)

[Guest jeromefr28]

Hi,

I need to extend the Z-Wave signal to cover the whole house (3 floors x 100m² with reinforced concrete floors).

Currently I have dead node problems , and windows contacts detectors (hsm02 and SM103 everspring) that transmit their opening statement at random.

By installing the HC2 in the middle of the house it works, but since the equipment room of the basement , the problems appear.

Can I replace the HC2 antenna by:

Cable 50 ohms with SMA connector ?

Please login or register to see this link.

Antenna omnidirectional 868 Mhz ?

Please login or register to see this link.

The Z-Wave mesh networks with the HC2 V1.036 does it really work?

I have :

9 Fibaro roller shutter FGR221

2 Fibaro relay switch FGS221 V1.7

1 Fibaro universal sensor 25/06/2012

1 EZmotion in routing mode

1 Aeon Labs Smart Energy Illuminator

3 AN157 Everspring

1 siren Fortrezz SSA

1 EZmotion

9 everspring hsm02

2 everspring SM103

2 everspring sp814

1 Z-Wave.Me ITEMP (KO)

thanks for your help,

[Guest jrkalf]

Somehow the trolls derailed this topic again. can somebody remove those trolling messages?

I too have noticed issues with location of zwave hardware and routing within the network. What's the status of Fibaro (please let a dev comment with details) on implementing the explorer frames which are ment to fix the routing table in a network?

[specimen 0]

I found this on the Fibaro advanced user documentation :

A controller will always try first to transmit its message directly to the destination. If this is not possible it will use its routing table to find the next best way to the destination. The controller can select up to three alternative routes and will try to send the message via these routes. Only if all three routes fail (the controller does not receive an acknowledgement from the destination) the controller will report a failure.

If it's true I guess that mean there is no routing table at all. And no way to provide a graphical view of the mesh... Each time the box have to reach a module, it try first to adress directly, then try to contact a neibourgh. The path to reach a specific module could be different each time.

If it's the case, it should probably better to store the best path and try it first...