This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
I now understand I'll have to build out a mesh network to be able to properly bridge the ranges required in my home to support zwave. While I do understand the basics around the mesh, but would like to know some experiences on what devices would be best to bridge the gaps. Do I need to stick to one brand, or will anything zwave+ blend mesh . Wonder if there are recommendations from Homey's perspective (different brand requires new apps etc) , do you guys normally stick with 1 brand? any recommendations?
thanks,
Pat
I tried to set it up in a way it should work, but with not a lor of success. Downstairs everything works reasonably ok. Sometimes there is a delay between motion and for instance turning on the HUE lights via a Flow, but anyway: When I want to use Z-Wave devices on the first floor, issues appear.
So I bought a extender (AEOTEC Range Extender 6), which I placed in the hall near the stairs to the first floor.
But the Motion Sensor if have on the first floor is not able to send information to Homey.
It seems the only way to get a proper Meshed network is by pressing the "Heal" button next to the nodes in the developer environment for Z-Wave, correct? Sometimes a new path is defined, where the signal is using a Fibaro wall plug (#20) to reach my Fibaro motion sensor ( #36) on the first floor and not the repeater (#22). Actually the repeater doesn't seem to help a lot of other devices, besides one Motion Sensor (#21)
My 2 questions;
1) it seems to be more logic that if Homey cannot reach the Motion sensor (#36), it uses the Repeater (#22), but it doesn't. Is there a way to define (and lock) this your self? The Mesh networks seems to be managed and maintained by Homey but that causes unsuccessful results.
2) The extender is not really showing any positive behaviour in my Zwave network. Anyone have experience, tips/tricks for this?
Attached a screenshot of the developer page for Z-Wave. The "Unknown Nodes" are devices that are included, but I lost a box when I moved in the house, So I couldn't remove them properly:
EDIT 5 minutes later:
Currently the path is again different and it's showing that it's using node #8 to reach my motion sensor. But as far as I know this node is not connected anymore, in any way it's a battery driven device (door sensor) which the battery probably died a year a go. So I guess a third question: Does this mean that this overview is incorrect?
Hi,
First post. Sorry for hi-jacking the thread but it is related. :-)
Before updating to fw 1.5.8 I could find a z-wave diagram in the Settings meny (Geek stuff). Now there is a link to a developer site but I cannot find the very informative diagram there...
Where is the z-wave diagram now?
Or is it not possible to get this overview anymore? I think it was of great assistance while building your mesh. :-)
BR, Fredrik
Ok, then I can stop looking for it at least.
Thanks for the info sossienl! I will have a further look at the developer page. :-)
BR, Fredrik
The exclamation mark on the flowcard shows 'TRANSMIT_COMPLETE_NO_ACK' With version 1.5.3 i did not have these kind of problems. The distance to Homey is only few meters
When i try to do a heal, most of the time i get a 'NETWORK_FAILED' error.
So, if this is not a range problem, what else can it be??
At first not a lot changed, as Homey didn't use the new nodes for routing to my sensor, it was just a simple 1 > 41 and 1 > 44.
I then removed on of the wallplugs I already had (20) and healed the Fibaro sensor (36). It now used one of the new wall plugs (44). This was my desired path, looking at my house layout, it made the most sense.
When I triggered the motion alarm, the HUE lights turn on within a seconds. Not instant, but acceptable.
Unfortunately, 2-3 hours later the Z-wave path has changed again from a single node route (1 > 44 > 36) , to multi step route (1 > 25 > 44 > 36). This again delivers a huge delay in motion alert and switching on my HUE lights.
It's been there for over 12hours now....
So besides investing additional € in a possible solution that was never an issue with my previous Zwave gateway (Mios Vera 3), I'm still facing this problem and there is no way I can define this myself?
Please advice.
is there any solution?
One sensor works fine (range 1 meter), three other motion senors don't send de motion to the homey the range is about 5 to 7 meter.