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
I've updated the version on: https://github.com/TedTolboom/com.neo/tree/TouchSwitch_V1
This update should recognise (by itself) the difference between the V2 (default) and V1 version...
For the V2 version it should work 'out of the box'.
For V1 it only requires a switch on (or off) on the touch switch...
Status is shown in a new dropdown option in the device settings: by default on 'Switch Binary V2'
@Eternity Can you test this update with the V1 version (install via CLI, no need to remove the device)?
- in the settings of the touch switch, check that drop down is set to 'Switch Binary V2'
- try switching on / off via the Homey interface > should not work
- switch on the device manually on the Touch switch itself > should update the state at Homey
- check in settings, drop down should now indicate 'Switch Binary V1'
- try switching on / off via the Homey interface > should work now
@CliffBroeren Can you test this update with the V2 version (install via CLI, no need to remove the device)?
- in the settings of the touch switch, check that drop down is set to 'Switch Binary V2'
- try switching on / off via the Homey interface > should work
- try switching on / off via the touch switch > should update the state at Homey
- change in the device settings the dropdown 'Switch Binary V1' (deliberately wrong)
- try switching on / off via the Homey interface > should no longer work
- switch on the device manually on the Touch switch itself
- check in settings, drop down should now indicate 'Switch Binary V2'
- try switching on / off via the Homey interface > should work now again
My findings:
- installing without removing went smoothly
- in 'settings' I found the option to set the switch to v1 or v2
- setting it to 'Switch binary V2' won't save and eventually crashes the App:
- I could not test the v2 state
Restarted the App and using v1 state:
- switching via Homey interface does switch the Neo
- manually switching the Neo does *NOT* update in the Homey interface
Installed the 'non v1/v2' version
- switching via Homey works
- manually switching works
Just a 'bump' :-)
Already received feedback from @CliffBroeren via Slack..
Unfortunately, the approach I had in mind does not work.. will need to implement a more complex approach in the next two weeks... with the V1 version you are able to proceed with your Touch Switch @Eternity for now
I am happily using the dedicated solution you made. Great work!
So, no hurry on my side :-)
The one thing I cannot get right are the readings. For all three sockets the information stays blank. They were all three added with the 'nothing' attached option.
http://www.szneo.com/en/products/show.php?id=195
Also, be aware that the homey app has to be updated to support this device.
I didn't find an option to order them yet...
but as soon as they will become available we'll update the app and drivers..
Let's see (troubleshooting time):
Do the sockets respond (instantly) 15-20 minutes after rebooting Homey, and is it degrading over time?
Can you check what the settings of your power plug are for "Meter report interval [s]" and "Power change [%]"?
And also the interval and threshold settings of your motion sensor?
Are there flows that can result in continuous Z-wave commands being send?
Can you go to Z-wave > stuff for geeks, keep the Z-wave log open for 30 minutes and copy the log into a txt file and add it here?
lets ask the proper question here @TedTolboom , did you include the socket as socket with a light attached? that has no power reading in the mobile card yet, will come in homey version 1.3
It could explain the missing energy reports, but not the degradation over time...
What changed? I added 5 new Z-wave roller shutter modules. Which brings me to the conclusion that your are probably facing signal loss due to a critical range. Sometimes it works, sometimes it doesn't.
Right now I'm using 16 z-wave devices, of which 9x 240V powered. How many non-battery devices do you have installed?
BUT, I also bumped into a similar issue with a different device which might be the cause of this.
Can you do the following:
Add the following to the 'Send RAW data' field in Z-wave > Stuff for geeks, and replace NodeID with the number (!) of the NodeID of your Touch switch (e.g. 47):
And press 'Send'.
In the Z-wave log, a similar log statement will be visible:
I'm curious if it now will show 0x142502 (pointing to an issue during inclusion).
Can you post the Z-wave log (unfiltered) around this statement?
PS. Please check the PM that I also send in parallel.
Will need to build the solution I have in mind.
I will happily do more testing and logging :-)
@CliffBroeren can you test the V2 version again?
No, the zwave is not degrading over time. Not so that I can mention. Sometimes everything works, sometimes only one socket.
Here are my settings, a logfile and a flow regarding to the lights.
No, doesn't work :-(
I initially received an error, whilst installing. "Homey unreachable".
Other z-wave stuff is active and works (so, mesh seems up).
- Switching the switch manually does not update Homey
- switching via Homey does not have an effect on the Neo Touch
Tested again this morning; the version provided a couple of posts up doesn't work with my Neo Touch Switch.
I reinstalled the dedicated version again, and that works properly again.
Sure, but need some help...this is new to me :-)
I reinstalled the version you made. It installed and it didn't work.
So, I opened a command prompt with node.js run als administrator
Type in athom project --run
This happened:
? Select active Homey: Homey @ 192.168.1.210:80
=> here I typed CTRL+C as I thought it would create a log file
Is the log here shown in Homey | z-wave | Stuff for geeks | the box with data at the bottom?
The debug logging will show in the command prompt (you have to manually copy it)..
so repeat the steps taken, after showing com.neo running, it will show a list of command classes... after that it will show the log of actions, please try to use / control the switch from within Homey and on the switch itself..
after that, Ctrl-c to abort, copy the loggings in the command prompt and reinstall the working version with the --install option...
much appreciated!
In Homey I see a yellow symbol in the Neo App that states it is running in debug mode!