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.
Official Z-Wave CommunityApp
Comments
wake up the device by clicking 3 times fast on the button . Neo Magic
If serious, how frequently should I do the triple click?
Does the NAS-WR01W work or will it be supported?
Patrick
Can anyone advise what might cause this and what the fix is?
I know they're detecting motion as I get the flash but it's always luminance failing in my flows with the reading values being far out of date...
Anyone else have this? All used to work fine so it's a recent thing
Found this as well. However, the "lamp" in flows is currently limited as trigger, as you cannot triggers flows based on power measured. So I can measure it in this way, but cannot use this information to trigger anything. Solved this by selecting a kettle instead of a lamp, then you have both the measurements and are able to use it as a trigger in flows.
One of these was not responding, so I excluded it successfully from Homey (=> z-wave setting | remove node) and re-included it. Strangely enough the node was still in the z-wave mesh *and* the re-included node was there too!
The 'old' node couldn't be deleted (several github issues that adres this problem).
So, I just moved that node to the Zone 'Delete" with other nodes that won't be deleted. Fair enough.
Now I have a non responding NEO Powernode again. I am sure that if I exclude and re-include it, I will end up with a orphan un-deletable node again...
It is 3 meters from Homey. Worked for ages and does not respond anymore.
The strange thing is, if I alter its settings, I get a confirmation:
So, Homey says it is not seen (NoAck) but I can change parameters...?
Also, it will not switch On/Off via browser nor App.
Is this a NEO bug?
I tried to remove the non responding Neo Powerplug, by deleting it from the Neo App. It returned an error "driver something". I deleted it via z-wave | settings and now it is unreachable ...
The Zone 'delete' is filling up rapidly.
I am not going to register a github issue. Too much z-wave issues reported and no progress on squashing these bugs.
Hello,
I have a problem with my NEO door-sensors:
When the door contact is open for more than several hours (variables durations) it changes itself back to closed.
I do not know if it is the NEO door-sensors itself, sending the closed signal to Homey,
OR that it is an issue with Z-Wave, OR an issue with my Homey.
Is this a know problem?
And is there a solution?
No, nothing of that kind.
I have 2 Velux windows, with 1 sensor on every window. The 2 sensors changes themselves back to “close” independently on my Homey.
Not together, not related to a wake-up, no magnet near the sensor, nothing, nada.