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
They can be found in the settings of your device, when you added it.
Do you maybe hevt a link to what device it is in:
http://www.pepper1.net/zwavedb/device/
or
http://products.z-wavealliance.org/products/
@MarcvZ
@kasteleman
Did one of you try the WALL controller? does it work? Because I want to rebuild this driver to a remote I have <span></span>
http://www.pepper1.net/zwavedb/device/36
Never used it since I bought it 2 years ago :P
My wall controller doesnt work, but its a different one (2 button)
As stated above.
Doesnt work single, nor when already associated to a physical switch.
I also cant findout the ID because it doesnt get added at all in homey, it just says, something went wrong
Tonight I can test it again, something I can do?
Run the zwave app in debug mode through cli?
When it comes to functionality, and therefor driver, they will probably be the same.
When it comes to the app, they have different ID's and are therefor recognized as different devices.
But here comes the bad news....
Neither of them is implemented in the app yet.
So it wont bring you anything installing it with CLI.
If you find a simular device in an App form another manufacturer, then please provide a link, copy pasting makes adding the device a lot easyer :P
@Icarus
I see you have both 05433 and ZME_05468 in the app again.
They are identical, both app ID's as driver as options, so you can take one out, but it might mean some people have to reinstall theirs. I do think it is better to have only one of them in the app though.
Because smartwares had a few battery operated switches:
SH5-TSW-B
Which are available in the app, but they are 433mhz so no pairing I believe.
Or (Zwave)
Fibaro FGPB-101, Push Button (In app)
TKB TZ65-D, Wall Switch (Not yet in app)
Or (Devolo)
Link with all possible battery wall controllers.
http://www.vesternet.com/smart-home/lighting/switches-dimmers
So my hope lies in the pushbutton, or the devolo switch
Do you know what is different from the wall switches, compared to build in switches?
reset your device from homey's settings -> z-wave -> [ remove device ], or the manual reset way specified in the device's manual (it doesn't matter that it is not shown in homey (yet))
Its the battery switch that's giving me a hard time, because it isnt supported
Any update on the stuck on MULTICHANNEL Issue while including a wall switch
Is someone still having the (github) version released in november 2016. With this version my dimmer was working so I hope I can go back to that version and hopefully it will work again.
If you have please send me a PM and I will give you my emailadres so you can send it alink is also fine ofcourse.
Because now my homey is now NOT my homie (snik)
lesson learned: if it ain't broke don't fix it
Can you let us know if it's working after using to older version again?
I'm having exactly the same issue as @CoenRoos mentioned on january 20th.
Wireless wall switch
All i get in the new logging is:
[2017-02-16T21:02:44.848Z] Command start: addNode
[2017-02-16T21:02:44.915Z] command status: addNode, status: ADD_NODE_STATUS_LEARN_READY
[2017-02-16T21:02:46.662Z] command status: addNode, status: ADD_NODE_STATUS_NODE_FOUND
[2017-02-16T21:02:49.528Z] command status: addNode, status: ADD_NODE_STATUS_FAILED
[2017-02-16T21:02:49.528Z] ProcessAddNode[10]: Error: ADD_NODE_STATUS_FAILED
[2017-02-16T21:02:49.551Z] Command end: addNode
[2017-02-16T21:02:50.959Z] Command start: addNodeAbort
[2017-02-16T21:02:50.967Z] Command end: addNodeAbort
So nothing usefull there, and the window only says: Something went wrong.
Still the still "Multi Channels Nodes worden opgehaald" error/timeout here. Is there already a solution?
We found the cause of this issue, it will be fixed in an upcoming Homey firmware update!
The devices that keep hanging on retrieving multichannel nodes seem to use COMMAND_CLASS_MULTI_CHANNEL V1 which is not used/supported anymore.
Everytime I asked if this problem could be firmware related I heard NO, NO ,NO
And suddenly after 3 months I receive a messages saying oh btw your issue is fixed in the upcoming firmware.
Hopefully a learning point for @Athom.
If the new firmware is released today I will test it and let you guys and girls know the result.
@Icarus and all other community people involved with the zwave-me app thanks for trying to help me I really appreciate it!
So hopefully I can start using homey again and stop letting it eat my dust ;-)
054436 ZW WS
https://github.com/athombv/homey/issues/1326#issuecomment-284478819
@Priknr1 is this something which you can fix in an update of the app?
Tip from @JeroenVollenbrock for the developer: if you disable the setOnDim capability option and your device turns on when setting a dim value, the app wil have to emit a realtime event upon receiving a set dim.