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.

[APP] Z-Wave.Me

1235789

Comments

  • Priknr1Priknr1 Member
    edited January 2017
    @pascal, Happpen to have 
    Manufacturer ID:
    Product Type ID:
    Product ID:

    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>:smile:</span>
    http://www.pepper1.net/zwavedb/device/36
    Never used it since I bought it 2 years ago :P
  • kastelemankasteleman Member
    edited January 2017
    @Priknr1 Not yet, because other testers can not include it at all ( @mauriceb ) and it needs to work for me because i use it for turning on and off some lights that have no physical switch attached to it.

  • Update works for my dimmers :)

    Now the battery switch still is on the list. 054436
    Anyone got that working? OR does any knwo how to add a device to homey as main controller.
    But also let the device accept external input from my switch?
    I want the switch to be implemented as the one at the bottom right   (no adding in homey but direct to a lamp known by homey)



    I tried everything the manual said last night but couldnt get it to work.
    Once the dimmer has been connected to homey, it wont send a NIF anymore that it is available.

    Anyone has an idea how to do this?
    Or could the switch be added to Homey?

    Posted before:
    Also by Priknr1 (https://forum.athom.com/discussion/comment/40122/#Comment_40122)
    064435
    http://www.pepper1.net/zwavedb/device/35
    Duwi battery wall controller (switch)
    inclusion  hold 2 sec
    Manufacturer:         100
    Product Type ID:     20482
    Product ID:         0

    OR/the same?

    054436
    Wall switch/dimmer   (Plak schakelaar op batterijen)
    http://www.pepper1.net/zwavedb/device/321
    Ik ga even checken of de id's overeenkomen.
    Google cache PDF:
    http://webcache.googleusercontent.com/search?q=cache:yUzPXI_1cyEJ:manuals.zwaveeurope.com/make.php%3Flang%3Den%26type%3Dmini%26sku%3DZME_054436%26pdf%3D1+&cd=7&hl=nl&ct=clnk&gl=nl&client=firefox-b-ab
    https://www.robbshop.nl/z-wave-me-wandzender-duwi-everlux






    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?
  • Priknr1Priknr1 Member
    edited January 2017
    @luccie_007
     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.
  • Priknr1 said:
    @luccie_007
     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.
    You need a similar zwave device?

    Because smartwares had a few battery operated switches:
    SH5-TSW-A
    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)
    Devolo Scene Switch (Z-Wave Plus) (in app)

    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?
  • @luccie_007
    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))
  • caseda said:
    @luccie_007
    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))
    I know how it all should work, i have multiple dimmers paired ;) so that works.

    Its the battery switch that's giving me a hard time, because it isnt supported
  • Hi Y'all

    Any update on the stuck on MULTICHANNEL Issue while including a wall switch
  • MennoMenno Member
    edited January 2017
    Help needed!

    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


  • On github you can go back in revisions. So normally you can get older version from the githubpage itself
  • I don't see any on the github of z-wave.me: https://github.com/IcarusProject/me.zwave/releases

  • @BasVanDenBosch whoooo thanks I didn't know that will try the old version from november!
  • YvesGeffensYvesGeffens Member
    edited February 2017
    @Menno

    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.
  • Menno said:
    just did a check with latest github version but still "Multi Channels Nodes worden opgehaald" error/timeout
    Same here with the 05433. What could be the problem/solution?
  • Pietje5Pietje5 Member
    edited February 2017
    Also on the november app the same. When i remove the app completely and pair with the zwave tool from Homey i get the same message: Multi Channel Nodes worden opgehaald and then it stucks again. Seems to be a Homey issue.
  • Pietje5 said:
    Also on the november app the same. When i remove the app completely and pair with the zwave tool from Homey i get the same message: Multi Channel Nodes worden opgehaald and then it stucks again. Seems to be a Homey issue.
    Somebody already raised an issue about this with Athom? If somebody can tell me how to do it, I will...
  • home78 said:
    Pietje5 said:
    Also on the november app the same. When i remove the app completely and pair with the zwave tool from Homey i get the same message: Multi Channel Nodes worden opgehaald and then it stucks again. Seems to be a Homey issue.
    Somebody already raised an issue about this with Athom? If somebody can tell me how to do it, I will...
    @Annemarie
  • I still have problems adding the 054436 ZW WS
    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.

  • @YvesGeffens

    Still the still "Multi Channels Nodes worden opgehaald" error/timeout here. Is there already a solution?
  • I think there is something missing in the zwave core that is causing this. There also Some problems with Some Qubino shutters devices that look simular. Best is to make an issue on github concerning that.
  • contact homey about the issue. Keep you informed
  • AnnemarieAnnemarie Member
    edited February 2017
    We're looking into this issue. Thanks for notifying! 
  • Annemarie said:
    We're looking into this issue. Thanks for notifying! 

    Thnx for your mail, awaiting solution....

    Many thanks in advance...

    Frans Klerks
  • Annemarie said:
    We're looking into this issue. Thanks for notifying! 
    Thnx!
  • Robin Bolscher <notifications@github.com> wrote:

    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.

  • Robin Bolscher <notifications@github.com> wrote:

    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.

    Great!!!
  • MennoMenno Member
    edited March 2017
    I'm not sure if I have to be happy or really angry!
    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 ;-)

  • Now i hope this also fixes the issues for my wall switch.
    054436 ZW WS


  • JesperJesper Member
    edited March 2017
    I reported an issue about the dimmer icon bug on github but Athom told me that it was a app specific bug and that it must be fixed by the app developer.

    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.
Sign In or Register to comment.