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
But yes temperature, got it from the official website just like @TedTolboom said -> http://www.szneo.com/en/products/show.php?id=197
I just got a Neo NAS-PD02Z pir and it does not connect.
Asked for an EU 868 version, how can i chek if it is EU?
THX!!!
Afther resetting the pir and fiddeling arround it suddenly workt!
THX!
And if you look at pir 1 the picture says temp sensing and motion and no lux mentiond too, but the specs say motion and lux.
I have the same problem with the touch switch. When the standard branch v1.1.22 is installed, the switch is not responding at all. The only thing that works is changing a setting like the status light. I also installed branch v1.1.22 V1. Now the switch reacts when I control it in the Homey interface. Unfortunately the status is not updated in Homey when I control the switch itself. The z-wave log shows that Homey receives input when the switch is turned off and on.
Z-wave log:
[2017-06-22T15:13:14.840Z] Node[24]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d01002503ff
[2017-06-22T15:13:14.872Z] Node[24]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_SWITCH_BINARY, data 0x03ff
[2017-06-22T15:13:14.875Z] Node[24]: Received application command for COMMAND_CLASS_SWITCH_BINARY, data: 0x03ff
[2017-06-22T15:13:54.819Z] Command[253] start: getNetworkTopology
[2017-06-22T15:13:55.067Z] Command[253] end: getNetworkTopology
[2017-06-22T15:14:00.431Z] Node[24]: Received application command for COMMAND_CLASS_MULTI_CHANNEL, data: 0x0d0100250300
[2017-06-22T15:14:00.467Z] Node[24]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_SWITCH_BINARY, data 0x0300
[2017-06-22T15:14:00.469Z] Node[24]: Received application command for COMMAND_CLASS_SWITCH_BINARY, data: 0x0300
[2017-06-22T15:21:59.173Z] Node[12]: Received application command for COMMAND_CLASS_SENSOR_MULTILEVEL, data: 0x05030a0081
Is there any solution to get the switch working so I can use it to control flows?
However @TedTolboom made me a dedicated version, which might be a good solution for you too.
@TedTolboom: I received the dedicated version you made for Eternity (the version without the ability to choose the Touch version) and I can confirm that it's working now . He told me that there were several problems implementing the solution into the main build. Are you still working on this and are there any plans to implement a solution in future builds? I have the Touch working now but that means I can never update the app in the future. I am willing to help if any testing is needed.
@Wimstradamus indeed most likely a translation error.
@jeromes, so it is working for now?
I will need to look into why the version that is compatible with both version is not working; don't understand that one.
I will put it back on my worklist, but considering it is working so far, it will not be a top priority; agree?
Agree, maybe it's an idea to put this dedicated version also on GitHub? I guess there are more people with the same version of the Neo Touch I received only 1 week ago. If you need any help with testing in the future, let me know!
I propose that you first test this version; high likelihood that it will work...
thanks to @lubbertkramer and @michael-smits
But I want the three minute timer to start only after I left the kitchen. And now the timer starts after I enter the kitchen. So, when I 'm longer than three minutes in the kitchen, the kitchen goes dark. Very annoying.
So, in short, I want the light in the kitchen on as long as there is movement in the kitchen. I cannot find a way to do that. I altered all kind of settings in the NEO and in the flow but I doesn't help.
Please give me some kind of direction to solve this problem. Thanx.
So why not use the "motion stopped" trigger as activation of the timer?
Just make sure you stop the timer when motion starts again
Would you be so kind to show an example, please....
Thanks!
I tried to do the 2 things in one flow but that wasn't as smart as my house ;-)
So you have a card in the 'then' colom with 'switch off light' and a 1 minute delay in the actual switch; this way you do not need a count down timer.
That is smart!
I'm still trying to get better results with three wall sockets. I have replaced Homey a few times to see if I got better response. My conclusion is that one of the devices is going up to 9 meter and a different one slightly 2 meters. So there is some difference in range here.
But now I have found a place that the mostly work I still have these problems;
- None of the sockets report parameters like power usage etc. This difficults creating advanced flows.
- None of the sockets are connected with a line in my zwave graph. My fibaro pir is the only connected device.
I there anybody who would like to guide me through a good troubleshooting trajectory? I've spend very much time trying allmost everything I know (that's little compared to some of you ) but I'm wondering if I should dump the three and get me myself some Fibaro's in the hope they will perform out of the box.
Would be interesting to see a good test/compare of the NEO and Fibaro sockets. Since I only have NEO sockets and no Fibaro I'm not in the position to do this. I mean a real "field testing", not some kind of theoretical compare.
Seems to me this is also not very simple to accomplice since the z-wave network is dynamical and heals itself (sometimes?) The testing would take quite an extended timeframe I guess.