Contribute to Open Source. Search issue labels to find the right project for you!

[Z-Wave] Wake Up Interval value: 0 should be possible

athombv/homey

What did you try to achieve? Have a battery device’s wake-up interval on 0 but the range starts from the minimal step size (in this case (ZW074) 240 seconds, but have seen more devices use this)

What was the result? The setting save button disables since 0 is not in the specified range even though 0 was the default wake up time.

What did you expect as result? 0 should be possible according to the specs, though it’s not really a good thing, it shouldn’t disable the save settings button causing confusion.

Any other remarks Version 1:

Values in the range 1..16777215 MUST indicate the time between Wake Up periods. The value 0 MUST indicate that the receiving node MUST Wake Up when initiated by an event determined by the application e.g. a pushbutton activation.

Version 2 (and up) there is an extra addition to this rule:

A receiving node SHOULD accept the value 0, even if the Minimum Wake Up Interval advertised by the Wake Up Interval Capabilities Report Command is larger than 0. If accepted, the value 0 MUST disable the timer-based transmission of Wake Up Notification Commands.

Updated 12/06/2017 12:14

Homey fails to see Z-Wave device from existing network

athombv/homey

What is your Homey version (Settings → System)?

1.3.0-rc.9

What did you try to achieve?

Inclusion in to existing Fibaro Home Centre 2 Z-Wave network

Please include detailed steps how we can reproduce the issue In Z-Wave select include into existing network and then on Fibaro Home Centre 2 select add device

What was the result?

Fibaro shows a new wave controller as included although it says it’s not fully configured. Homey does not show any Existing Z-Wave Devices

What did you expect as result?

The same as when I add a different Z-Wave controller such as a Samsung Smarththings, I expected the existing Z-Wave devices to show as available within Homey.

Any other remarks

100% swapping to homey from an already fully setup Z-Wave network is not a valid option till I have tested the capabilities of Homey, I purchased Homey because teeth idea of it sounds great, integration in to existing network is definitely required to allow for proper testing before taking the plunge if Homey performs well.

Please attach a Homey System log (Settings -> System -> Send Log)

EAD3163579

Updated 12/06/2017 12:08 5 Comments

Fibaro motion sensor plus-> Settings won't update after wakeup from sleep

athombv/homey

What is your Homey version (Settings → System)? 1.3.0 RC 7

What did you try to achieve? Update device settings

Please include detailed steps how we can reproduce the issue change device settings on fibaro motion sensor plus wait for device to wakeup (with and without button, press on device)

What was the result? the parameters didn’t update after device wakeupe from sleep. i tryd to disable everything except motion. …

2017-05-22_14-32-17 2017-05-22_14-33-53

What did you expect as result? updated device parameters

Any other remarks

Please attach a Homey System log (Settings -> System -> Send Log)

Updated 15/06/2017 12:20 1 Comments

fibaro motionsensor keeps motion state

athombv/homey

What is your Homey version (Settings → System)?

1.3.0 rc7 - node 85

What did you try to achieve? the sensor should turn the light out after 60 sec

Please include detailed steps how we can reproduce the issue i made 2 flows: -1 if motion, turn light on {node85} -2 if no motion turn light off

What was the result? the sensor kept the motion state

What did you expect as result? after 60 sec without movement the sensor should set movement to no Untitled.txt

Any other remarks

[2017-05-17T19:44:50.105Z] Node[85]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40 [2017-05-17T19:44:50.108Z] Node[85]: sendData to COMMAND_CLASS_SECURITY, params 0x800e0ef1f351c206a7 [2017-05-17T19:44:50.171Z] Node[85]: Received application command for COMMAND_CLASS_SECURITY, data: 0x8120a14cfc3e84c888020dc40825834c9578ecc60e206a6f92d00e8d80 [2017-05-17T19:44:50.194Z] Node[85]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_NOTIFICATION, data 0x05000000ff07000108

Please attach a Homey System log (Settings -> System -> Send Log) 58E91D8053 …

Updated 20/05/2017 19:39 5 Comments

[1.2.2] Z-wave unable to establish direct association anymore - security keys issue?

athombv/homey

What is your Homey version (Settings → System)? 1.2.2 / Fibaro app version 1.4.3

What did you try to achieve? Add direct association between 2 new Fibaro Dimmer-2’s (FGD-212, FW 3.5), linking S2 via association group 5 to another dimmer-2 (on Homey 1.2.2)… Similar to a setup I already use with multiple Dimmer-2’s for months, added ~ 1.1.2

What was the result? The to be controlled dimmer-2 does not respond to pressing the S2 button.

What did you expect as result? Same results as with the other dimmer-2’s: able to control the other dimmer-2 with the button connected to S2

Please attach a Homey System log (Settings -> System -> Send Log)

I’ve added Homey’s ID to the same 5th association group, providing the set commands within the Z-wave log: Switch on (Node 65 to 68): [2017-04-30T14:48:16.090Z] Node[65]: Received application command for COMMAND_CLASS_CRC_16_ENCAP, data: 0x012b011a0094c3 [2017-04-30T14:48:16.105Z] Node[65]: Decapsulated frame from COMMAND_CLASS_CRC_16_ENCAP to COMMAND_CLASS_SCENE_ACTIVATION, data 0x011a00 [2017-04-30T14:48:16.217Z] Node[65]: Received application command for COMMAND_CLASS_SWITCH_MULTILEVEL, data: 0x01ff01 [2017-04-30T14:48:16.234Z] Node[65]: Received application command for COMMAND_CLASS_SWITCH_MULTILEVEL, data: 0x01ff01

Switch off (Node 65 to 68): [2017-04-30T14:48:30.666Z] Node[65]: Received application command for COMMAND_CLASS_CRC_16_ENCAP, data: 0x012b011a0094c3 [2017-04-30T14:48:30.681Z] Node[65]: Decapsulated frame from COMMAND_CLASS_CRC_16_ENCAP to COMMAND_CLASS_SCENE_ACTIVATION, data 0x011a00 [2017-04-30T14:48:30.793Z] Node[65]: Received application command for COMMAND_CLASS_SWITCH_MULTILEVEL, data: 0x010001 [2017-04-30T14:48:30.815Z] Node[65]: Received application command for COMMAND_CLASS_SWITCH_MULTILEVEL, data: 0x010001 For reference the logs when adding Homey’s ID to the existing (pre 1.1.x added Dimmer-2’s): Switch on (Node 8 to node 4): [2017-04-30T14:37:25.914Z] Node[8]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40 [2017-04-30T14:37:25.915Z] Node[8]: sendData to COMMAND_CLASS_SECURITY, params 0x8047f2938d980aec01 [2017-04-30T14:37:25.916Z] Command[552] start: sendData [2017-04-30T14:37:25.921Z] ProcessSendData[548]: To node: 8 with data: 0x988047f2938d980aec01 and txOptions: ACK,AUTO_ROUTE,EXPLORE [2017-04-30T14:37:25.953Z] Command[552] end: sendData [2017-04-30T14:37:25.977Z] Node[8]: Received application command for COMMAND_CLASS_SECURITY, data: 0x810a12a543a84a58efc39c866840475d218b0d7e8f7b10 [2017-04-30T14:37:26.008Z] Node[8]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_SCENE_ACTIVATION, data 0x011a00 [2017-04-30T14:37:26.274Z] Node[8]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40 [2017-04-30T14:37:26.275Z] Node[8]: sendData to COMMAND_CLASS_SECURITY, params 0x80fc830e5b3d2ba375 [2017-04-30T14:37:26.275Z] Command[553] start: sendData [2017-04-30T14:37:26.280Z] ProcessSendData[549]: To node: 8 with data: 0x9880fc830e5b3d2ba375 and txOptions: ACK,AUTO_ROUTE,EXPLORE [2017-04-30T14:37:26.309Z] Command[553] end: sendData [2017-04-30T14:37:26.334Z] Node[8]: Received application command for COMMAND_CLASS_SECURITY, data: 0x81ffcc272bcfba053e4a3dbe4084e68b981afc83ba50b7122ff851 [2017-04-30T14:37:26.365Z] Node[8]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_SWITCH_MULTILEVEL, data 0x01ff01 [2017-04-30T14:37:26.365Z] Node[8]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_MULTI_CHANNEL, data 0x0d02002601ff01 [2017-04-30T14:37:27.319Z] Node[4]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40 [2017-04-30T14:37:27.320Z] Node[4]: sendData to COMMAND_CLASS_SECURITY, params 0x80b712102844c98228 [2017-04-30T14:37:27.321Z] Command[554] start: sendData [2017-04-30T14:37:27.325Z] ProcessSendData[550]: To node: 4 with data: 0x9880b712102844c98228 and txOptions: ACK,AUTO_ROUTE,EXPLORE [2017-04-30T14:37:27.586Z] Command[554] end: sendData [2017-04-30T14:37:27.756Z] Node[4]: Received application command for COMMAND_CLASS_SECURITY, data: 0x81262088228c3017d80e9dc7c7b71881ffc3889c2271 [2017-04-30T14:37:27.773Z] Node[4]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_SWITCH_MULTILEVEL, data 0x0332 [2017-04-30T14:37:27.933Z] Node[4]: Received application command for COMMAND_CLASS_CRC_16_ENCAP, data: 0x0131050422002ebc77 [2017-04-30T14:37:27.949Z] Node[4]: Decapsulated frame from COMMAND_CLASS_CRC_16_ENCAP to COMMAND_CLASS_SENSOR_MULTILEVEL, data 0x050422002e [2017-04-30T14:37:32.443Z] Node[4]: Received application command for COMMAND_CLASS_CRC_16_ENCAP, data: 0x0131050422006455f9 [2017-04-30T14:37:32.458Z] Node[4]: Decapsulated frame from COMMAND_CLASS_CRC_16_ENCAP to COMMAND_CLASS_SENSOR_MULTILEVEL, data 0x0504220064 Switch off (Node 8 to node 4): [2017-04-30T14:37:58.745Z] Node[8]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40 [2017-04-30T14:37:58.746Z] Node[8]: sendData to COMMAND_CLASS_SECURITY, params 0x80caebfee6262c1932 [2017-04-30T14:37:58.747Z] Command[557] start: sendData [2017-04-30T14:37:58.766Z] ProcessSendData[553]: To node: 8 with data: 0x9880caebfee6262c1932 and txOptions: ACK,AUTO_ROUTE,EXPLORE [2017-04-30T14:37:58.806Z] Command[557] end: sendData [2017-04-30T14:37:58.845Z] Node[8]: Received application command for COMMAND_CLASS_SECURITY, data: 0x81fbda2b3edb96409c35b4d9fce4ca7d728432576073b8 [2017-04-30T14:37:58.876Z] Node[8]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_SCENE_ACTIVATION, data 0x011a00 [2017-04-30T14:37:59.124Z] Node[8]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40 [2017-04-30T14:37:59.125Z] Node[8]: sendData to COMMAND_CLASS_SECURITY, params 0x807667b54416793006 [2017-04-30T14:37:59.126Z] Command[558] start: sendData [2017-04-30T14:37:59.130Z] ProcessSendData[554]: To node: 8 with data: 0x98807667b54416793006 and txOptions: ACK,AUTO_ROUTE,EXPLORE [2017-04-30T14:37:59.162Z] Command[558] end: sendData [2017-04-30T14:37:59.191Z] Node[8]: Received application command for COMMAND_CLASS_SECURITY, data: 0x813558c748a71e031b074c144cbcba52feeb7651d833876be45f9f [2017-04-30T14:37:59.221Z] Node[8]: Decapsulated frame from COMMAND_CLASS_MULTI_CHANNEL to COMMAND_CLASS_SWITCH_MULTILEVEL, data 0x010001 [2017-04-30T14:37:59.221Z] Node[8]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_MULTI_CHANNEL, data 0x0d020026010001 [2017-04-30T14:38:00.174Z] Node[4]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40 [2017-04-30T14:38:00.175Z] Node[4]: sendData to COMMAND_CLASS_SECURITY, params 0x801324e56bf86b2f20 [2017-04-30T14:38:00.176Z] Command[559] start: sendData [2017-04-30T14:38:00.180Z] ProcessSendData[555]: To node: 4 with data: 0x98801324e56bf86b2f20 and txOptions: ACK,AUTO_ROUTE,EXPLORE [2017-04-30T14:38:00.435Z] Command[559] end: sendData [2017-04-30T14:38:00.608Z] Node[4]: Received application command for COMMAND_CLASS_SECURITY, data: 0x81ec623b12f5bff689e6a705041359868abbfeaf9c11 [2017-04-30T14:38:00.625Z] Node[4]: Decapsulated frame from COMMAND_CLASS_SECURITY to COMMAND_CLASS_SWITCH_MULTILEVEL, data 0x0300 [2017-04-30T14:38:00.783Z] Node[4]: Received application command for COMMAND_CLASS_CRC_16_ENCAP, data: 0x0131050422002becd2 [2017-04-30T14:38:00.799Z] Node[4]: Decapsulated frame from COMMAND_CLASS_CRC_16_ENCAP to COMMAND_CLASS_SENSOR_MULTILEVEL, data 0x050422002b [2017-04-30T14:38:10.423Z] Node[4]: Received application command for COMMAND_CLASS_CRC_16_ENCAP, data: 0x0131050422000349b8 [2017-04-30T14:38:10.439Z] Node[4]: Decapsulated frame from COMMAND_CLASS_CRC_16_ENCAP to COMMAND_CLASS_SENSOR_MULTILEVEL, data 0x0504220003 Corrective actions taken * Tried removing and re-including both dimmer-2’s - no success * Association groups are correctly filled (verified with RAW data) * Compared settings: settings are identical

LOG ID: 342A715E89

Updated 01/05/2017 15:46

zwave devices marked as invalid_node

athombv/homey

What is your Homey version (Settings → System)?

1.2.2

What did you try to achieve?

Removed some zwave devices and tryed to repair. Repair worked couple of times, after that no more. Last repaired devices are all marked as invalid_node. Even one older device (fabro roller shutter) is now marked as invalid_node. Removing zwave from settings is working, but the device is still here. Removing with the cross from devices and timeout is working. Removed devices now unpossible to pair.

What was the result?

Dead devices, zwave unusable, pairing not possible, removing old devices problematic.

What did you expect as result?

Working zwave

Any other remarks

Zwave IDs are over 200 atm, maybe i have the max. IDs used? Is Homey not restarting with the zwave ID Nummbers? PTP and Rebooted many times, not better

Please attach a Homey System log (Settings -> System -> Send Log)

557E168C2B is a new one, 3F06DE6438 older (better) one

Updated 25/05/2017 10:46 13 Comments

Battery drain

athombv/homey

What is your Homey version (Settings → System)? 1.2.0 rc9

What did you try to achieve? Yesterday almost all batteries were empty. Fibaro and Aeotec devices

What was the result? Some batteries went from 100% to 86 overnight.

What did you expect as result? That batteries don’t drain overnight.

Attached insight from the fibaro floodsensor 2017-03-24_09-54-11

Updated 04/04/2017 07:53

Z-Wave map goes berserk

athombv/homey

What is your Homey version (Settings → System)?

1.2.0 RC8

What did you try to achieve?

The Z-Wave topology map loads correctly, once loaded it starts spinning around like crazy and it seems it can’t stop forever. Have around 30 Z-Wave devices, this is insane. Not really noticeable on the picture, please see the video.

schermafbeelding 2017-03-20 om 19 23 44

https://www.youtube.com/watch?v=5o6mbDt4SoY

Issue, is active since the Z-Wave map has been implented

What was the result?

Can’t read Z-Wave map. Please note, there is a workaround to get the Z-Wave map to see: 1.full screen page, 2. Zoom out to a far maximum 3. grap one of the nodes and pull it away as far as possible (once dragged and moved The Z-wave map should come to a hold 4 Let go of the node and zoom back in, you should now have a good view.

What did you expect as result?

Working Z-Wave Map.

Updated 05/05/2017 13:58 5 Comments

[Z-wave] Multi Channel association not possible (input validation NOK)

athombv/homey

What is your Homey version (Settings → System)? 1.1.2

What did you try to achieve? Add a multi channel end-point (Light connected to one of the Greenwave Powernode-6 sockets) node ID to the association group of a Fibaro Dimmer-2 (supporting COMMAND_CLASS_MULTI_CHANNEL and COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION) to switch on the light simultaneously with the light connected to the Dimmer-2

What was the result? Input validation of the association groups field does not accept non integer input (e.g. 10.1) to indicate the node ID of the multi channel end point (light connected to the greenwave powernode) <img width=“655” alt=“schermafbeelding 2017-01-21 om 10 45 31” src=“https://cloud.githubusercontent.com/assets/17163431/22173528/096a5f7a-dfc7-11e6-9c88-df6379bf4f6d.png”>

What did you expect as result? Able to add it to the association groups.

Has the COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION been fully implemented and is this only an input validation issue or is the COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION not (fully) implemented yet?

Any other remarks Work around is to create a flow within Homey to do this. But this is not the desired situation. Specifically in case of Z-wave sensors with alarm capability (e.g. motion or smoke sensors) it should be possible to directly switch on (or off) any other Z-wave devices by creating a direct association

In addition, new Z-wave Multi-channel sockets are currently under development by different parties…

Updated 19/06/2017 21:59 6 Comments

feature request: OTA firmware upgrade for ZWAVE devices

athombv/homey

What is your Homey version (Settings → System)?

1.0.4

What did you try to achieve?

I have several zwave devices that can get a firmware update Over The Air (OTA). E.g. the fibaro multisensor and the Aeotec multisensor. I only have a Homey as a controller, so I would very much like to be able to do the fw update using Homey! It would probably also solve a lot of device issues that users are experiencing with older device firmwares.

Please include detailed steps how we can reproduce the issue

What was the result?

What did you expect as result?

For Homey to support OTA zwave firmware updates.

Any other remarks

See for instance the information at:

https://aeotec.freshdesk.com/support/solutions/articles/6000036562-how-do-i-upgrade-the-firmware-for-multisensor-6-

https://forum.fibaro.com/index.php?/topic/21711-fibaro-device-firmware-list/

Updated 15/05/2017 21:01 13 Comments

Fork me on GitHub