›
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.
Official

[App] Qubino by Athom - main discussion topic

1246

Comments

  • pascalpascal Member
    Heb bij alle modules de blauwe draad ook aangesloten. Zal het nogmaals nakijken maar ik heb de handleiding er bij gehouden. Ik zal een tekening maken hoe ik het heb aangesloten.
  • kastelemankasteleman Member
    Hallo Pascal, ik vind het nl gek want ik heb ook de ZMNHDA2 icm eenzelfde schakelaar en werkt bij mij vlekkeloos. Heb wel een keer gehad dat ik op de schakelaar 2 draden had verwisseld waardoor ik een gelijk gedrag kreeg.
  • pascalpascal Member
    @kasteleman
    Duidelijk. Dan ga ik als het wat langer licht is nogmaals de draden nakijken.
  • kastelemankasteleman Member
    Pascal, 1 dingetje nog: heb je tussentijds de settings nig eens gesaved nadat je de qubino had toegevoegd?
  • bvbbvb Member
    Looking for support of the Qubino roller flush shutter, can someone help here? Does it work with homey. I have normal electrical blinds wich I want to automate. As I read several bad feedbacks from fibaro, I'm asking myself if this module could be a more relible alternative?

    Thanks for your feedback
    Berni
  • kastelemankasteleman Member
    Look for comments from @clandmeter. He has build an app for it available on his github
  • clandmeterclandmeter Member
    AFAIK fibaro does not have DC roller shutters, so i guess he means regular shutter? My fibaro shutters work fine.
  • bvbbvb Member

    Hello, got the Momey today and also the Qubino Roller Shutter ZMNHCD1... I looked on Github but not sure what I should do there... can someone give me  a high level step by step tutorial, so that I can find a starting point what to do?

    As far I see the Qubino module is not supported via the Qubino App from  @clandmeter...

    Thanks for your help

    Berni 

  • clandmeterclandmeter Member
    This module is currently not supported by the Qubino app. This means you will have to wait or add support for this yourself. What you could try is copy my driver and rename it to yours and adjust the devices ID's ( you can get the ID's by including the module without a driver loaded).

    PS, there are currently issues with shutters and newer firmware, so it might by it wont even include with or without the driver loaded. https://github.com/athombv/homey/issues/1317
  • bvbbvb Member

    Hi, I included the module now, the PN: ZMNHCD1 H1S5P1 to the Z-Wave Network as "Generic Z-Wave Device".

    It seems that it is connected as an "unknown Z-Wavew Device" with Home ID: 3982883491, is this the device ID?

    I got the following code in the "Z-Wave Setup for Geeks" (I'm not a geek ;-P)

    [2017-03-15T18:35:45.808Z] Command start: addNode
    [2017-03-15T18:35:45.857Z] command status: addNode, status: ADD_NODE_STATUS_LEARN_READY
    [2017-03-15T18:35:58.900Z] command status: addNode, status: ADD_NODE_STATUS_NODE_FOUND
    [2017-03-15T18:35:59.322Z] command status: addNode, status: ADD_NODE_STATUS_ADDING_SLAVE
    [2017-03-15T18:35:59.363Z] command status: addNode, status: ADD_NODE_STATUS_PROTOCOL_DONE
    [2017-03-15T18:35:59.423Z] command status: addNode, status: ADD_NODE_STATUS_DONE
    [2017-03-15T18:35:59.718Z] command status: addNode, status: INTERVIEW_CC
    [2017-03-15T18:35:59.727Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x135e
    [2017-03-15T18:35:59.744Z] Command start: sendData
    [2017-03-15T18:35:59.761Z] ProcessSendData[10]: To node: 3 with data: 0x86135e and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:35:59.792Z] Command end: sendData
    [2017-03-15T18:35:59.813Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x145e02
    [2017-03-15T18:35:59.830Z] command status: addNode, status: INTERVIEW_CC_1_OF_16
    [2017-03-15T18:35:59.832Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1386
    [2017-03-15T18:35:59.833Z] Command start: sendData
    [2017-03-15T18:35:59.844Z] ProcessSendData[11]: To node: 3 with data: 0x861386 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:35:59.872Z] Command end: sendData
    [2017-03-15T18:35:59.894Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x148602
    [2017-03-15T18:35:59.897Z] command status: addNode, status: INTERVIEW_CC_2_OF_16
    [2017-03-15T18:35:59.898Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1372
    [2017-03-15T18:35:59.899Z] Command start: sendData
    [2017-03-15T18:35:59.915Z] ProcessSendData[12]: To node: 3 with data: 0x861372 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:35:59.943Z] Command end: sendData
    [2017-03-15T18:35:59.990Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x147202
    [2017-03-15T18:35:59.998Z] command status: addNode, status: INTERVIEW_CC_3_OF_16
    [2017-03-15T18:36:00.002Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x135a
    [2017-03-15T18:36:00.003Z] Command start: sendData
    [2017-03-15T18:36:00.016Z] ProcessSendData[13]: To node: 3 with data: 0x86135a and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.075Z] Command end: sendData
    [2017-03-15T18:36:00.120Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x145a01
    [2017-03-15T18:36:00.128Z] command status: addNode, status: INTERVIEW_CC_4_OF_16
    [2017-03-15T18:36:00.129Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1373
    [2017-03-15T18:36:00.129Z] Command start: sendData
    [2017-03-15T18:36:00.147Z] ProcessSendData[14]: To node: 3 with data: 0x861373 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.183Z] Command end: sendData
    [2017-03-15T18:36:00.206Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x147301
    [2017-03-15T18:36:00.209Z] command status: addNode, status: INTERVIEW_CC_5_OF_16
    [2017-03-15T18:36:00.210Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1320
    [2017-03-15T18:36:00.210Z] Command start: sendData
    [2017-03-15T18:36:00.217Z] ProcessSendData[15]: To node: 3 with data: 0x861320 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.243Z] Command end: sendData
    [2017-03-15T18:36:00.263Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x142001
    [2017-03-15T18:36:00.266Z] command status: addNode, status: INTERVIEW_CC_6_OF_16
    [2017-03-15T18:36:00.267Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1327
    [2017-03-15T18:36:00.268Z] Command start: sendData
    [2017-03-15T18:36:00.275Z] ProcessSendData[16]: To node: 3 with data: 0x861327 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.305Z] Command end: sendData
    [2017-03-15T18:36:00.324Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x142701
    [2017-03-15T18:36:00.329Z] command status: addNode, status: INTERVIEW_CC_7_OF_16
    [2017-03-15T18:36:00.330Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1325
    [2017-03-15T18:36:00.333Z] Command start: sendData
    [2017-03-15T18:36:00.339Z] ProcessSendData[17]: To node: 3 with data: 0x861325 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.367Z] Command end: sendData
    [2017-03-15T18:36:00.388Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x142501
    [2017-03-15T18:36:00.391Z] command status: addNode, status: INTERVIEW_CC_8_OF_16
    [2017-03-15T18:36:00.391Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1326
    [2017-03-15T18:36:00.392Z] Command start: sendData
    [2017-03-15T18:36:00.400Z] ProcessSendData[18]: To node: 3 with data: 0x861326 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.430Z] Command end: sendData
    [2017-03-15T18:36:00.460Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x142603
    [2017-03-15T18:36:00.463Z] command status: addNode, status: INTERVIEW_CC_9_OF_16
    [2017-03-15T18:36:00.464Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1332
    [2017-03-15T18:36:00.465Z] Command start: sendData
    [2017-03-15T18:36:00.472Z] ProcessSendData[19]: To node: 3 with data: 0x861332 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.500Z] Command end: sendData
    [2017-03-15T18:36:00.520Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x143204
    [2017-03-15T18:36:00.523Z] command status: addNode, status: INTERVIEW_CC_10_OF_16
    [2017-03-15T18:36:00.524Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1385
    [2017-03-15T18:36:00.525Z] Command start: sendData
    [2017-03-15T18:36:00.534Z] ProcessSendData[20]: To node: 3 with data: 0x861385 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.571Z] Command end: sendData
    [2017-03-15T18:36:00.595Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x148502
    [2017-03-15T18:36:00.598Z] command status: addNode, status: INTERVIEW_CC_11_OF_16
    [2017-03-15T18:36:00.599Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x138e
    [2017-03-15T18:36:00.600Z] Command start: sendData
    [2017-03-15T18:36:00.610Z] ProcessSendData[21]: To node: 3 with data: 0x86138e and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.643Z] Command end: sendData
    [2017-03-15T18:36:00.670Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x148e03
    [2017-03-15T18:36:00.673Z] command status: addNode, status: INTERVIEW_CC_12_OF_16
    [2017-03-15T18:36:00.674Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1359
    [2017-03-15T18:36:00.674Z] Command start: sendData
    [2017-03-15T18:36:00.682Z] ProcessSendData[22]: To node: 3 with data: 0x861359 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.717Z] Command end: sendData
    [2017-03-15T18:36:00.739Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x145902
    [2017-03-15T18:36:00.742Z] command status: addNode, status: INTERVIEW_CC_13_OF_16
    [2017-03-15T18:36:00.744Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1370
    [2017-03-15T18:36:00.744Z] Command start: sendData
    [2017-03-15T18:36:00.758Z] ProcessSendData[23]: To node: 3 with data: 0x861370 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.807Z] Command end: sendData
    [2017-03-15T18:36:00.825Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x147001
    [2017-03-15T18:36:00.845Z] command status: addNode, status: INTERVIEW_CC_14_OF_16
    [2017-03-15T18:36:00.846Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1320
    [2017-03-15T18:36:00.847Z] Command start: sendData
    [2017-03-15T18:36:00.863Z] ProcessSendData[24]: To node: 3 with data: 0x861320 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.889Z] Command end: sendData
    [2017-03-15T18:36:00.912Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x142001
    [2017-03-15T18:36:00.914Z] command status: addNode, status: INTERVIEW_CC_15_OF_16
    [2017-03-15T18:36:00.915Z] Node[3]: sendData to COMMAND_CLASS_VERSION, params 0x1326
    [2017-03-15T18:36:00.916Z] Command start: sendData
    [2017-03-15T18:36:00.922Z] ProcessSendData[25]: To node: 3 with data: 0x861326 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:00.952Z] Command end: sendData
    [2017-03-15T18:36:00.971Z] Node[3]: Received application command for COMMAND_CLASS_VERSION, data: 0x142603
    [2017-03-15T18:36:00.974Z] command status: addNode, status: INTERVIEW_CC_16_OF_16
    [2017-03-15T18:36:01.463Z] command status: addNode, status: INTERVIEW_MANUFACTURER_SPECIFIC
    [2017-03-15T18:36:01.464Z] Node[3]: sendData to COMMAND_CLASS_MANUFACTURER_SPECIFIC, params 0x0404
    [2017-03-15T18:36:01.465Z] Command start: sendData
    [2017-03-15T18:36:01.473Z] ProcessSendData[26]: To node: 3 with data: 0x720404 and txOptions: ACK,AUTO_ROUTE,EXPLORE
    [2017-03-15T18:36:01.508Z] Command end: sendData
    [2017-03-15T18:36:31.466Z] Command end: addNode
    [2017-03-15T18:36:45.572Z] Command start: addNode
    [2017-03-15T18:36:45.595Z] command status: addNode, status: ADD_NODE_STATUS_LEARN_READY
    [2017-03-15T18:37:15.648Z] command status: addNode, status: ADD_NODE_STATUS_DONE
    [2017-03-15T18:37:15.648Z] ProcessAddNode[27]: Error: timeout
    [2017-03-15T18:37:15.658Z] Command end: addNode
    [2017-03-15T18:37:17.528Z] Command start: getNetworkTopology
    [2017-03-15T18:37:17.660Z] Command end: getNetworkTopology
    [2017-03-15T18:37:54.809Z] Command start: addNodeAbort
    [2017-03-15T18:37:54.823Z] Command end: addNodeAbort


    What do I Need to do next?I

    P.S: There is no device added to the room I added the device....

    Thanks

    Bernhard

  • clandmeterclandmeter Member
    I would suggest you return this module and buy a Fibaro shutter. Please read: https://github.com/athombv/homey/issues/1317  (this counts for all Qubino shutter devices)
  • bvbbvb Member

    Is it the plan that there is no "Switch" on the "Device Card" where I can see the Status of my "Door", like on/off or open/closed? Im using the Flush 1D relay with a dry contact..

  • bvbbvb Member
    @clandmeter any commetn regarding my question above?
  • clandmeterclandmeter Member
    @bvb I guess this is ZMNHND1? if so, this device is not added by me. You could ask @kasteleman as he added it (not sure he owns one).
  • kastelemankasteleman Member
    @bvb Don't own the device, so can not reproduce, but i did have a look in the app that is published by Athom.
    It is by design. No slider or switch as you call it. The icon itself is the switch. If turned off, it is grey. If turned on it is black.
  • bvbbvb Member

    Hi again, I have now the Qubino Dimmer ...DD1 and the device Shows no power consumption. Is this a bug? I see in the settings some functions for power selection. Thanks for your help.

  • TedTolboomTedTolboom Member
    bvb said:

    Hi again, I have now the Qubino Dimmer ...DD1 and the device Shows no power consumption. Is this a bug? I see in the settings some functions for power selection. Thanks for your help.

    You've included the device as light. Currently power reporting is nog available when you include the device as light; if you want power reporting, you should choose 'other' as device class
  • bvbbvb Member
    Where can I change the device class? Do i need to exclude the device and include it again or is thre a switch in the App somewhere?
  • TedTolboomTedTolboom Member
    bvb said:
    Where can I change the device class? Do i need to exclude the device and include it again or is thre a switch in the App somewhere?
    Currently the only option is to exclude the device and include it again..
    A long requested feature is to be able to change the device class and add capabilities of devices without the need to re-pair the device... stil WIP
  • bvbbvb Member
    edited April 2017

    I have now included the Qubino Flush 2 Relays (ZMNHBD1) and the Status of the Relays is not written back to Homey. If I Switch it On or Off over the App then everything is fine. If I use the Wallswitch then the Status of the device card is not updated.

    The report of the power consumption is working correct. Also the status in the Flow Editor unter Tags is reporting the correct status of the Switch under Power Consumption, but not for the Switch. See Screenshot.

    Can anyone help?

    BTW: The Power Meter Shows always 0

  • basdbasd Member
    @kasteleman

    Zou je support voor de ZMNHBA2 kunnen toevoegen ?
  • casedacaseda Member
    @basd
    i'm not @kasteleman but that module is already supported by the app in the app store.
    Qubino

    can be that the id's have changed with an update of the module, then please make an issue on github with a screenshot of the id's in the device's settings
  • basdbasd Member
    @caseda can in install both of them together? 
  • kastelemankasteleman Member
    @basd install both of them together? 
  • basdbasd Member
    edited May 2017
    @kasteleman

    if install your qubino app the app off athom disapears
    Thats my problem

    So if i wish to support the qubino devices that athom supports and the device your app supports. it doesn't work :-(

  • kastelemankasteleman Member
    edited May 2017
    I don't get it ;) can you (again) mention the devices you are missing?
  • basdbasd Member
    I don't get it ;) can you (again) mention the devices you are missing?
    ZMNHBA2 
  • kastelemankasteleman Member
    Did you manage to pair it with Homey? If so, as @caseda already mentioned, we need the device id.
  • basdbasd Member
    Somting like this ?
    If not where can i find the device id? 
  • kastelemankasteleman Member
    Jip, i'l have a look later this day to check the app
Sign In or Register to comment.