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

[com.fibaro] Analog Input on Fibaro RGBW does not work (for me).

athombv/homey

<!–

Thank you for reporting an issue. Please take some time to review the contributing guidelines if you haven’t done so.

This issue tracker is for bugs and issues found within Homey. If you require more general support contact our support team at: support@athom.com

Please fill out as much of the fields below as you’re able. The Homey log code can be generated at Settings -> System -> Send Log. The Homey App log code can be generated at Settings -> Apps (hold ALT to show the ‘Send Log’ link).

If possible, please provide examples that demonstrates the problem, keeping it as simple and clear as you are able to.

–>

Metadata

  • Homey Version: 1.5.3
  • Homey Log Code: 0D83AC48DE
  • Smartphone Platform: Android
  • Smartphone App Version: 2.4.7 - Build 77

If related to a Homey App: * Homey App Version: Fibaro 1.5.13 * Homey App Log Code: ??? no ‘Send Log’ link when holding ALT ! * Affected Devices (preferably product codes): FGRGBWM-441

What did you try to achieve? <!– Please include detailed steps to reproduce the issue below this line –> I’ve been using the RGBW module for input with three standard closed magnetic switches. That worked OK for the past six months. Now I want to use the remaining IN-port as ‘Analog in’ port but that doesn’t work. This is how things are connected: aansluiting rgbw controller - 2 N.B. the three switches are standard closed until I open a door or window.

Homey settings: instellingen rgbw controller

What did you expect as result? <!– Please describe what you expected to happen below this line –> I expected to be able to read-out the analog signal and be able to use the level of the signal as a trigger.

What was the result? <!– Please describe what happened instead below this line –> Nothing worked anymore: - Open/close of the three switches were not detected anymore. - Voltage changes on IN4 are not detected.

N.B. if I measure on the IN4 port when nothing is connected, there standard is a 10.45 Volt level (as is on the other IN-ports when a switch is open). It seems there is a pull-up resistor on the port. Will that 10.45 Volt disappear when the configuration is correct?

Any other remarks In my first attempt I had the analog signal on IN1. When I could not get that working I tried to use the ‘Expert parameters’ to force parameter 14. But when I want to set it using ‘14,2,34406’ (hex: 8666) I get error ‘value’ argument is out of bounds. Test show out that the max allowed parameter value is 32767. Value 32768 will produce the error. It seems that the parameter value is treated as a INT16 where it should be an UINT16. I do not know if this is a Homey-problem or a Fibaro-problem.

So I thought to work around this problem by switching some wires, changing some flows and put my analog signal on IN4 (as shown above). That would keep the value of parameter 14 under 32767. Now the new expert parameter setting ‘14,2,26216’ (hex: 6668) was accepted, but it still does not work. I think the ‘Expert parameter’ is supposed to overrule any userinterface setting. So I did some tests, but if I set the ‘Ingang x configuratie’ as shown above, and set expert parameter to overrule the setting to ‘Tuimel schakelaar (schakelaar status gebaseerd)’ for all the inputs by setting expert parameter ‘14,2,26214’ (hex: 6666) then the switches still do not work. Only when all the ‘Ingang x configuratie’ settings are ‘Tuimel schakelaar (schakelaar status gebaseerd)’ it is no problem setting expert parameter ‘14,2,26214’, but any other value will give the problems again. So what use is an expert parameter if it must duplicate the userinterface setting?

Best regards, Johan Mulderij

Updated 05/12/2017 21:24 2 Comments

Motion trigger data not processed correctly from fibaro motion sensor

athombv/homey-issues-dp

What is your Homey version (Settings → System)? 1.5.6 RC3

What did you try to achieve? Get the motion to trigger

Please include detailed steps how we can reproduce the issue Device is not triggered, walk in room, wait for trigger and get no result.

What was the result? In the log I got the following data:

2017-11-28T20:21:18.142Z Command[10599] start: getNetworkTopology
2017-11-28T20:21:19.023Z Command[10599] end: getNetworkTopology
2017-11-28T20:21:36.178Z Node[43]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
2017-11-28T20:21:36.178Z Node[43]: [COMMAND_CLASS_SECURITY] {}
2017-11-28T20:21:36.178Z Node[43]: [COMMAND_CLASS_SECURITY] [SECURITY_NONCE_REPORT] {“type”:“Buffer”,“data”:[191,228,161,227,174,105,66,230]}
2017-11-28T20:21:36.178Z Node[43]: sendData to COMMAND_CLASS_SECURITY, params 0x80bfe4a1e3ae6942e6
2017-11-28T20:21:36.181Z Command[10600] start: sendData
2017-11-28T20:21:36.181Z ProcessSendData[10598]: To node: 43 with data: 0x9880bfe4a1e3ae6942e6 and txOptions: AUTO_ROUTE,EXPLORE
2017-11-28T20:21:36.200Z Command[10600] end: sendData
2017-11-28T20:21:39.439Z Node[43]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
2017-11-28T20:21:39.440Z Node[43]: [COMMAND_CLASS_SECURITY] {}
2017-11-28T20:21:39.440Z Node[43]: [COMMAND_CLASS_SECURITY] [SECURITY_NONCE_REPORT] {“type”:“Buffer”,“data”:[192,247,242,44,112,120,138,155]}
2017-11-28T20:21:39.440Z Node[43]: sendData to COMMAND_CLASS_SECURITY, params 0x80c0f7f22c70788a9b
2017-11-28T20:21:39.442Z Command[10601] start: sendData
2017-11-28T20:21:39.443Z ProcessSendData[10599]: To node: 43 with data: 0x9880c0f7f22c70788a9b and txOptions: AUTO_ROUTE,EXPLORE
2017-11-28T20:21:39.461Z Command[10601] end: sendData
2017-11-28T20:21:43.487Z Node[43]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
2017-11-28T20:21:43.487Z Node[43]: [COMMAND_CLASS_SECURITY] {}
2017-11-28T20:21:43.487Z Node[43]: [COMMAND_CLASS_SECURITY] [SECURITY_NONCE_REPORT] {“type”:“Buffer”,“data”:[193,143,161,204,223,136,109,171]}
2017-11-28T20:21:43.487Z Node[43]: sendData to COMMAND_CLASS_SECURITY, params 0x80c18fa1ccdf886dab
2017-11-28T20:21:43.490Z Command[10602] start: sendData
2017-11-28T20:21:43.490Z ProcessSendData[10600]: To node: 43 with data: 0x9880c18fa1ccdf886dab and txOptions: AUTO_ROUTE,EXPLORE
2017-11-28T20:21:43.509Z Command[10602] end: sendData
2017-11-28T20:21:43.758Z Node[43]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
2017-11-28T20:21:43.758Z Node[43]: [COMMAND_CLASS_SECURITY] {}
2017-11-28T20:21:43.758Z Node[43]: [COMMAND_CLASS_SECURITY] [SECURITY_NONCE_REPORT] {“type”:“Buffer”,“data”:[194,201,61,229,4,57,225,1]}
2017-11-28T20:21:43.758Z Node[43]: sendData to COMMAND_CLASS_SECURITY, params 0x80c2c93de50439e101
2017-11-28T20:21:43.759Z Command[10603] start: sendData
2017-11-28T20:21:43.759Z ProcessSendData[10601]: To node: 43 with data: 0x9880c2c93de50439e101 and txOptions: AUTO_ROUTE,EXPLORE
2017-11-28T20:21:43.777Z Command[10603] end: sendData
2017-11-28T20:21:47.020Z Node[43]: Received application command for COMMAND_CLASS_SECURITY, data: 0x40
2017-11-28T20:21:47.021Z Node[43]: [COMMAND_CLASS_SECURITY] {}
2017-11-28T20:21:47.021Z Node[43]: [COMMAND_CLASS_SECURITY] [SECURITY_NONCE_REPORT] {“type”:“Buffer”,“data”:[195,9,189,18,252,81,166,99]}
2017-11-28T20:21:47.021Z Node[43]: sendData to COMMAND_CLASS_SECURITY, params 0x80c309bd12fc51a663
2017-11-28T20:21:47.023Z Command[10604] start: sendData
2017-11-28T20:21:47.024Z ProcessSendData[10602]: To node: 43 with data: 0x9880c309bd12fc51a663 and txOptions: AUTO_ROUTE,EXPLORE
2017-11-28T20:21:47.043Z Command[10604] end: sendData

What did you expect as result? The motion alarm to be triggered.

Updated 12/12/2017 14:55 14 Comments

[1.5.x] multiChannelNode class ignored

athombv/homey

Metadata * Homey Version: 1.5.x

What did you try to achieve? Use different class for multiChannelNode as for main device node.. "id": "ZHC5010", "name": { "en": "ZHC5010 - Relay" }, "class": "other", "capabilities": [ "onoff", "configuration_custom_capability", "scene_notification_custom_capability" ], "zwave": { "multiChannelNodes": { "1": { "class": "socket", "capabilities": [ "onoff", "dim" ], "icon": "/drivers/ZHC5010/assets/icon_1.svg", "name": { "en": "ZHC5010 - Button 1" } }, "2": { "class": "socket", "capabilities": [ "onoff", "dim" ], "icon": "/drivers/ZHC5010/assets/icon_2.svg", "name": { "en": "ZHC5010 - Button 2" } }, "3": { "class": "socket", "capabilities": [ "onoff", "dim" ], "icon": "/drivers/ZHC5010/assets/icon_3.svg", "name": { "en": "ZHC5010 - Button 3" } }, "4": { "class": "socket", "capabilities": [ "onoff", "dim" ], "icon": "/drivers/ZHC5010/assets/icon_4.svg", "name": { "en": "ZHC5010 - Button 4" } } }, Due to #2000 issue (overwriting the custom capabilities), I thought to use the other or light class for the mainnode and still use the socket class for the multiChannelNodes…

What did you expect as result? It should be possible to define a different class for the multiChannelNodes.

What was the result? But I don’t get a pop-up with the options for the multiChannelNodes… the multiChannelNodes get the same class as the mainNode….

Any other remarks

Updated 06/12/2017 16:46 1 Comments

Flows are not triggered - Fibaro devices stop responding until Homey Restart

athombv/homey

After upgrade of Homey or Fibaro app my devices keep disconnecting from Homey - when I restart the homey it works igen.

I can’t exactly say what happend but 1.5.5 and Fibaro 1.5.13 came about the same day.

Metadata

  • Homey Version: 1.5.5
  • Homey Log Code: 726A33BDB1

If related to a Homey App: Fibaro * Homey App Version: v1.5.13 * Homey App Log Code: c062e5e1-08a1-457f-b856-ec94c8cacbbc * Affected Devices (preferably product codes): Fibaro Dimmer 2 and other fibre devices!

What did you try to achieve? Nothing in particular - it have been working for ages but after either a Homey update or App update I have to restart my homey every day to get it working again.

When a sensor sees motion my light does not turn on - I reboot homey and it works again - I can’t see whats wrong.

Any other remarks

Updated 01/12/2017 15:58 3 Comments

z-wave - remove device does not work

athombv/homey

<!–

Thank you for reporting an issue. Please take some time to review the contributing guidelines if you haven’t done so.

This issue tracker is for bugs and issues found within Homey. If you require more general support contact our support team at: support@athom.com

Please fill out as much of the fields below as you’re able. The Homey log code can be generated at Settings -> System -> Send Log. The Homey App log code can be generated at Settings -> Apps (hold ALT to show the ‘Send Log’ link).

If possible, please provide examples that demonstrates the problem, keeping it as simple and clear as you are able to.

–>

Metadata

  • Homey Version: v1.5.5
  • Homey Log Code: C033C3052D
  • Smartphone Platform:
  • Smartphone App Version:

If related to a Homey App: * Homey App Version: * Homey App Log Code: * Affected Devices (preferably product codes):

What did you try to achieve? Tried to remove a unrecognised z-wave devise

What did you expect as result? That the removal process reports that the device could not be found - which is what was true - but was still removed from Homey.

What was the result? Device was not found, but is NOT removed from Homey.

<img width=“1023” alt=“schermafbeelding 2017-11-17 om 10 33 53” src=“https://user-images.githubusercontent.com/10754229/32940618-6ef73770-cb83-11e7-942f-8ebb6ac386b4.png”>

Any other remarks

Updated 14/12/2017 22:26 30 Comments

[com.fibaro]

athombv/homey

<!–

Thank you for reporting an issue. Please take some time to review the contributing guidelines if you haven’t done so.

This issue tracker is for bugs and issues found within Homey. If you require more general support contact our support team at: support@athom.com

Please fill out as much of the fields below as you’re able. The Homey log code can be generated at Settings -> System -> Send Log. The Homey App log code can be generated at Settings -> Apps (hold ALT to show the ‘Send Log’ link).

If possible, please provide examples that demonstrates the problem, keeping it as simple and clear as you are able to.

–>

Metadata

  • Homey Version: 1.5.3
  • Homey Log Code:
  • Smartphone Platform:
  • Smartphone App Version:

If related to a Homey App: * Homey App Version: * Homey App Log Code: * Affected Devices (preferably product codes):

What did you try to achieve? <!– Please include detailed steps to reproduce the issue below this line –> I try to put on and off the light connected with a Fibaro Dimmer 2.

What did you expect as result? <!– Please describe what you expected to happen below this line –> I expect the light to go on and off when I press the button on a Nodon Wall Switch or a Nodon Soft switch or on the Android app or in the management tool on the PC

What was the result? <!– Please describe what happened instead below this line –> All other lights in the living room react on commands, but the Fibaro Dimmer 2 (2 times in the living room) do not react. Even when I talk to Homey it turns on and of all the lights, except the two Fibaro Dimmer 2 lights. Sometimes when I restart the Fibaro app on the Homey, it starts working again, but most of the times I have to reboot the Homey to get it work again. After the reboot it works oke for a while, but after a longer time the both Fibaro dimmers “hang” again and I will have to reboot again. I searched for combinations with other apps, tried to restart them too, but that didn’t help.

Any other remarks When sometimes the problem can be solved with a restart of the Fibaro app, the lights turn on or off, as if it the commands were cached somewhere. But most of the times I have to reboot the Homey.

Updated 02/12/2017 16:42 4 Comments

[com.danalock] Does not always respond

athombv/homey

<!–

Thank you for reporting an issue. Please take some time to review the contributing guidelines if you haven’t done so.

This issue tracker is for bugs and issues found within Homey. If you require more general support contact our support team at: support@athom.com

Please fill out as much of the fields below as you’re able. The Homey log code can be generated at Settings -> System -> Send Log. The Homey App log code can be generated at Settings -> Apps (hold ALT to show the ‘Send Log’ link).

If possible, please provide examples that demonstrates the problem, keeping it as simple and clear as you are able to.

–>

Metadata

  • Homey Version:1.5.4
  • Homey Log Code:
  • Smartphone Platform:Iphone
  • Smartphone App Version:

If related to a Homey App: Danalock V3 * Homey App Version: 2.0.3 * Homey App Log Code: * Affected Devices (preferably product codes):

What did you try to achieve? <!– Please include detailed steps to reproduce the issue below this line –> I am trying to open the lock directly from the Homey app or the homey windows app, but lock only reacts sometimes

I also have a flow opening the street door, and if someone is at home the Danalock should open as well, but this flow only works 50% of the times.

What did you expect as result? <!– Please describe what you expected to happen below this line –> The lock to open :-)

What was the result? <!– Please describe what happened instead below this line –> very often Nothing happens

Any other remarks I dont have any battery indicator working as well, i can see the battery indicator but it does not show anything.

It seems like since the latest Danalock firmware update the lock has a life of its own.

I have tried to uninstall everything and repair after the FW update, but still same result.

Updated 11/12/2017 12:04 2 Comments

Z-Wave devices stop responding/network failure occurs

athombv/homey

What is your Homey version (Settings → System)?

1.5.3

What did you try to achieve?

Control Z-Wave devices with Homey.

What was the result?

After a variable amount of time (even directly after reboot) Z-Wave devices stop responding to commands, and probably also stop sending reports.

Any other remarks

This is an issue summarizing various other issues: - https://github.com/athombv/com.fibaro/issues/174 - https://github.com/athombv/com.fibaro/issues/164 - https://apps.athom.com/app/com.fibaro

The issue is common and known in our community, someone who can (almost) always reproduce is m-ruiter.

Updated 11/12/2017 15:03 40 Comments

(Z-Wave) devices with unknown capability values after reboot

athombv/homey

What is your Homey version (Settings → System)?

1.5.3

What did you try to achieve?

Use device capability tokens in Flows as a condition.

Please include detailed steps how we can reproduce the issue

Install a Fibaro FGRM-222 (or another similar device), use the ‘dim level’ token as condition in a Flow. Reboot Homey (do not control the device in the meanwhile), and when the Flow is expected to run (force run it after reboot) it will not continue as the condition is not fulfilled as the value is ‘-’ or null.

What was the result?

After a reboot the Flows will not run as expected as the values of the capabilities are null.

What did you expect as result?

Homey to store the last known capability values, or retrieve them from the device on boot.

Any other remarks

This issue was created from a discussion in this ticket: https://github.com/athombv/com.fibaro/issues/139. Also reported here: https://github.com/athombv/com.fibaro/issues/170.

It also causes issues with speech, I think speech should catch null values, instead of trying to pronounce e.g. ‘It is NaN degrees’, see: https://github.com/athombv/com.aeotec/issues/62

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

Not relevant.

Note: a solution would be to get all capability values from Z-Wave devices on boot. Question is whether this is a smart thing to do on large Z-Wave networks (given the current load time). Maybe initialize Z-Wave devices in batches? Similar to apps?

Updated 21/11/2017 16:04

Fibaro Motion Sensor suddenly not connected anymore

athombv/homey

What is your Homey version (Settings → System)?

1.5.2

What did you try to achieve?

My Fibaro Motion Sensor did not report anything anymore. When looking at the zwave network graph it was not ‘connected’ to Homey anymore. Never had problems with this. The sensor is about 2 meters away from Homey.. Restarted Homey and still the same

What was the result?

No communication with the sensor anymore

What did you expect as result?

A nicely working sensor which communicates with Homey

Any other remarks

Please attach a Homey System log (Settings -> System -> Send Log) It’s about node 18 in the logs: zwave logs.txt

Homey log file code: D55285419F

Updated 20/11/2017 15:50 1 Comments

Motion and sabotage alarm stay on with firbaro Motion (Zwave plus)

athombv/homey

What is your Homey version (Settings → System)?

1.5 rc9

Motion and sabotage-alarm are on and never go off after reboot. Also waking up the device wont help.

On Slack it seemed there are more people having this issue. Since the Motion alarm stays on it also does not detect any Motion again (flows are not triggered)

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

Updated 13/12/2017 12:43 27 Comments

[com.qubino] ZMNHBD1 doesn't update meter/measure power after long time unpowered

athombv/homey

What is your Homey version (Settings → System)? Homey Firmware Versie: 1.3.2

What did you try to achieve? use the devices Fibaro FGS-221 and Qubino ZMNHBD1 (Both 2-relay modules) and be able to monitor the momentary-power use

Please include detailed steps how we can reproduce the issue After Pairing these devices, the power/energy is displayed, status change by connected switch is not shown on Homey

What was the result? Added the device, then the “Energy” was shown and updated while it was changing. The switch-status was updated when it was changed by a connected switch/pushbutton. Then I did a power down for 5 minutes of the device and powered it up again, then there was no update of the “Energy” it stays on 0W, several times switching the device on/off does work for the load but no energy indication.

What did you expect as result? an indication of the power data

Any other remarks when pairing the Qubino device, the default on the display says “pushbutton” but the function is “switch”, if you need “pushbutton” then you first have to change the parameters to “switch” and then back to “pushbutton”, then it works.

Homey_ZWAVE.txt

see also https://forum.athom.com/discussion/3461/multichannel-nodes-not-updating-status#latest https://forum.athom.com/discussion/3427/z-wave-devices-dont-show-energy-power-after-power-down#latest

Updated 27/11/2017 16:12 5 Comments

Z-wave inclusion doesn't work - stuck at Exchanging security key and other issues

athombv/homey

What is your Homey version (Settings → System)?

1.3.2

What did you try to achieve?

Include a Philio device

Please include detailed steps how we can reproduce the issue

Tried 3 times to include and everytime it gets stuck at the phase it showing “exchanging security key” after a while (timeout?) it asked again to put it into inclusion mode as it is paired, it gives error that it is already paired. Then first delete it through Z-wave settings and tried to include again. After 3 times I decided to reboot and then it worked directly. I have seen this behaviour on 1.3 RCs as well and then also reboot fixed the issue. Errors like Error: queue_full are visible in the Z-wave log

Then performed reboot. Then tried again, it got further when retrieving classes it stopped and showing that it could not reach despite the fact the device is 5 cm from Homey After Homey seems to be very busy. When trying to add a device again it it slower and when Z-wave device creation starts it shows for a long period of time waiting z-wave to be ready Then I had to remove node again (twice… ) and after that it was succesfull included

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

After 3 times and before reboot: FDA8C0F1E2 After reboot, other issues and succesful inclusion: 308CE686C3

Updated 01/12/2017 14:07 11 Comments

Exclude zwave mobile(items)/flows from view that are optional and not enabled

athombv/homey

What is your Homey version (Settings → System)?

1.1.2

The optional parameter in z-wave driver will ignore capabilities that are currently not available, but they will still be added to the mobile cards in the webif/mobile apps. While for a temperature sensor this is not that problematic, when other capabilities like onoff/dim/… this results in options in the mobile cards that are very confusing for end-users.

It would be nice if optional is specified and the capability is not available the items in mobile/flows will be excluded from the view. (Alternatively one could include an interface where you can disable devices/capabilities).

Updated 20/11/2017 14:11

Fork me on GitHub