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
Can you use the updated version (4 hours ago) from https://github.com/TedTolboom/com.neo/tree/TouchSwitch_V1?
In this last update, functionally I didn't change anything, I enabled debugging and added additional logging which will help to understand why this solution is not working..
Homey stated the App is up and running in debubbing mode:
This time I left all windows open and changed the sliders in the web interface; noting is logged.
Same for manually changing settings; no log items...
Have to leave for 2 hours. So, no response till later this afternoon.
Hope the log explains the issue!
Good luck and thanks again :-)
C:\Users\Kantoor\Desktop\NEE>athom project --run
I pressed the button in the web interface, first left (2x) than richt (2x) and after hat the actual buttons on the Neo Touch (left 2x, ricght 2x).
Now I really have to leave :-)
Succes :-)
Tested the parsers on my power plugs (V2), can you confirm it on your Touch switch:
https://github.com/TedTolboom/com.neo/tree/TouchSwitch_V1
Installed and tested.
- using the web interface works! Sliding S1 and S2 operates the Neo Switch
- editing the settings and saving, works too
- using the buttons on the Neo itself, does not update in the webinterface
UPDATE
Later this afternoon I thought it could be handy to create a log. Somehow the App crashed, and the Neo interface stays 'faded'':
I than installed again (athom project --install) and the App crashed
Error: Cannot find module './lib/client'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (/node_modules/homey-log/index.js:3:18)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
Exit code: 1
Exit signal: null
I installed the dedicated App and that works like a charm.
Is it best to order the new version (NAS-PD02Z) or should I go for the old one? (NAS-PD01Z) ? Compatible with homey?
I noticed someone mentioned it in this thread but not a lot of info.
https://www.aliexpress.com/item/NEO-COOLCAM-Z-wave-PIR-Motion-Sensor-Detector-Home-Automation-Alarm-System-Motion-Alarm-Compatible-with/32789819896.html
vs
https://www.aliexpress.com/item/NEO-COOLCAM-NAS-PD02Z-New-Z-wave-PIR-Motion-Sensor-Detector-Home-Automation-Alarm-System-Motion/32796863408.html
As you can see in the above details there has been some confusion between the same switches that turn out to be different after all.
Maybe one of the developers can comment on already including the new PIR version?
As you can see in the above details there has been some confusion between the same switches that turn out to be different after all.
Maybe one of the developers can comment on already including the new PIR version? So far, I didn't see any differences between the two of them. I would expect also the second version will pair fine (and otherwise we'll add them to the app in no time).
the really new version; as announced with temperature sensor is only announced and not yet spotted in stores...
I expect this question had been asked already, but I could'nt find the anwser.
Currently i'm using both Fibaro and Neo Coolcam devices in my Z-wave network connected to Homey.
While browsing through the settings I noticed the Neo Coolcam devices are not Secured, the Fibaro devices appear as secured.
Fibaro:
Neo Coolcam:
Devices of both vendors are capable of secured inclusion, right? Did I somehow mess up the inclusion or is this a constraint in the Neo Coolcam app?
See the Z-Wave Protocol Implementation Conformance Statement:
So secured (read encrypted) inclusion will not be possible.
I did not see the certification report for the next generation of the Neo PIR; according to new guidelines from the Alliance, encrypted security should now be implemented and will be enforced
"Supports Z-Wave Network Security? Yes" and "Supports Z-Wave AES-128 Security S0? No"
So it's secure, but not secure enough.... please be aware that more Z-wave Plus products have this `feature` / `issue`
i have the Neo Coolcam PIR motion sensor. Ik heb de sensitivity aangepast naar High. Maar als ik 4-5 meter voor het apparaat op de bank ga zitten ziet hij al geen beweging meer.
Suggesties?
@TedTolboom did you found anything special in my log files you requested a bit ago? I'm still having range issues with some of the sockets.
Zojuist de nieuwe pir van Neo binnen gehad (NAS-PD02Z) aangemeld als de oude pir in de app.
Beweging, lux en batterij komen binnen, lijkt dus alleen om uiterlijke verandering te gaan niet intern.
Werkt perfect.
Edit: Forgot the forum was English
The new pir from Neo (NAS-PD02Z) works, added it as the old one, i think the just changed the outside.
So i'm curious where you got the info from and with temp you mean temperature right?
If you check the manufacturers own site, it shows on the official product pictures "temperature sensing"...
I am awaiting to receive the PD02 to check it myself... and adapt the driver if needed