I bought a few weeks ago a Fibaro keyfob remote. Willing to use it for security panel status changes (driving alarm status) + garage door control (using an already mounted qubino relay).
For alarm mode change, I was willing to do this through the controller. A direct connection works from front of my home so no problem for this use-case.
For garage door control, I expected a direct association to work better: More distance, especially if still in car + the qubino is just behind the door, nearest z-wave module for this use-case.
Problem: Direct association mostly do not work. In fact, controlling the qubino from the controller (using a scene) works better (but mostly needs a few tries, so still not convenient) than direct association.
Looking a z-wave mesh topology, there may be a reason: Qubino relay does not show a direct route with Fibaro remote. But does with controller, because included nearby as usual.
So my question is: Why are such (always moving) modules not able to be routed by every pairs able to do so? This would IMO be the best option.
At least, depending on user use-case, is there a way to force a topology branch/relaying pairs in z-wave mesh? Well, could do a re-heal with remote near qubino, but as network may be healed sometimes I would prefer a way to enforce some topology branches for reliability: I'm not willing to keep the remote in front of my garage door to ensure a nightime heal will not break things depending on remote location at heal time...
In fact, I'm just wondering if z-wave meshed nature is really suited for such remotes and, generally speaking, all moving modules??? If not, why do some vendors sells some?
If someone with deep knowledge of z-wave internals have an answer/workaround, I would appreciate!
Regards.
