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

[App] Fibaro by Athom (v1.5.18)

12527293031

Comments

  • phil_sphil_s Member
    edited March 2017
    @TedTolboom
    any suggestions so far? is complicated isn't it?

    there must be a toggle command and not only an on/off command, right? so it is not possible now for cross circuit switches with double switches/relays from fibaro i think....
  • @phil_s 1st opportunity to respond...
    had a night off on Friday with some fathers from school.. and recovered yesterday next to the soccer field ;-P

    No, don't think it is complicated.... the toggle command is a conditional on / off command handled within Homey; not a Z-wave command... based on the condition of the switch Homey recalls, it will send a ON command in case the switch is in the OFF condition and vice versa...

    So setting up the motion sensor, with 255 (ON) at 'Motion detection ON command' and 0 (OFF) at 'Motion detection OFF command' should do the trick.

    But there is a BUT...
    The FGS-223 is a multi-channel device; S1 and S2 are two (different) end points (independently switchable) within 1 node(ID). Although the Fibaro Motion sensor supports Multi Channel Association (towards a NodeID + end point), this is not yet implemented in Homey v1.1.9.
    So creating a direct association towards a multi-channel device (like the Fibaro FGS-223 or Greenwave powernode-6) will not be possible (for now). I will add this note to the guide above.
  • Thank you @TedTolboom for your explaination! So I can hope for future support?
  • This will require a change in Homey's Core where associations are handled.. so work for Athom... I can't estimate the impact or effort..
    but yes I'll be pushing for it (also preventing Dimmer-2 S2 to be linked to a switch-2)
  • again thank you @TedTolboom  for your effort! 
  • Since a week I have a motion sensor. But since a few days the temperature isn't logged or send and it keeps saying it's 20,4 degrees. Is there any explanation for this? See my charts;


  • I have associated one dimmer 2 to another dimmer 2 module. It works fine.
    Now I want to remove the association. How to do that? Filling in blanks in the association setting dialog boxes does not remove the association. 
    I am on homey 1.1.9 and Fibaro 1.4.0
  • @JoopBanaan Yes, removing the node ID out of group 4 or 5 will remove the association (re-checked on my dimmer-2's) on the same release.

    It might be that the removal command was not properly received.
    Can you try to re-add the same node ID > save settings > remove the node ID > save settings?
  • In the Fibaro app v1.4.0 (currently in master branch), some additional functions have been implemented:

    'Set timer functionality' action card for Fibaro dimmer-2:
    use case: Change or update the timer functionality enabling to switch off the dimmer automatically after the defined time
    how to implement:
    1. Define a new flow (e.g. time triggered)
    2. Add the 'Set timer functionality' action card and set the duration in seconds before the device will be switched off (in this case 300 seconds). 
    3. Setting the duration to 0 will disable the function
    'Reset meter values' action card for all supported devices:
    use case: reset the meter values (kWh) as recorded on the device to 0 via a flow on the defined interval (January 1st, 1st of the month, etc)
    how to implement:
    1. Define a new flow (e.g. time triggered)
    2. Add the 'Reset meter values ' action card and execute the flow
  • Very nice @TedTolboom
  •  re-add the same node ID > save settings > remove the node ID > save settings did indeed remove the association.
    Thanks Ted
  • In the Fibaro app v1.4.0 (currently in master branch), some additional functions have been implemented:

    'Set timer functionality' action card for Fibaro dimmer-2:
    [...]
    why only for dimmer 2? Is it really so different from Dimmer 1?
  • Yannick said:
    In the Fibaro app v1.4.0 (currently in master branch), some additional functions have been implemented:

    'Set timer functionality' action card for Fibaro dimmer-2:
    [...]
    why only for dimmer 2? Is it really so different from Dimmer 1?
    Yep. Firmware of the Dimmer-2 is providing more options to configure.
    Dimmer-1 does not have a timer settings (at least I didn't find one) like the Dimmer-2.

    Where possible, I will always release an improvement to all applicable devices... even if the parameter number might be different. 
    Feedback (in case I missed one) and suggestions are always welcome.
  • EternityEternity Member
    edited April 2017
    My Fibaro FGS-222 Relays stopped working...

    I noticed the light in my bathroom didn't switch on anymore (a motion detector triggers the Fibaro relay).
    I cheched the flow, that was OK.

    In devices I can manually switch on the relay, but this does not do anything anymore. Same with the Homey App; switching the relay to ON, does not switch the light on.
    If I change a setting in the Fibaro settings page, the device gives the response that the settings are updated (so, communication from Homey to the relay works...?!)

    Homey f/w 1.2.0-rc.10
    Fibaro v1.4.1

    Any ideas?
  • Had the same twice with this module on Domoticz. A re-pair usually solves this. Never knew what caused it though.
  • Put in a new battery in my Door / window sensor (non-plus) last week and it's aready dead now. Any ideas what could be going on?
  • @Skorpion

    How strange!
    I will repair them too.

    Thanks for the answer.
  • @Yannick,
    checked your devices  wake-up interval at its settings?
  • All default, actually had to repair as just replacing the battery didn't bring it back online.

  • Priknr1Priknr1 Member
    edited April 2017
    @Yannick
    How many times did you open your door or window? Been opening/closing it all day?  :D

    Maybe just a broken sensor, you could check your z--wave log, filter the device id, and see if there is a large amount of communication?
  • EternityEternity Member
    edited April 2017
    Hm, re-pairing is even difficult. Can't get Homey to  remove the (no longer working) FGS-222.
  • TedTolboomTedTolboom Member
    edited April 2017
    Eternity said:
    Hm, re-pairing is even difficult. Can't get Homey to  remove the (no longer working) FGS-222.
    @Eternity go to devices > click on the X of the FGS-222 > Homey will show the instructions to remove...
    if the device is not responsive, simply wait (keep window open)... Homey will remove the device after a time out

    Now execute factory reset on the FGS-222 according to the manual and you should be able to re-add it to Homey
  • @TedTolboom

    I tried that, and it didn't work. But, guess what.... all three my FGS-222's are working again ! !

    I don't know what caused the problem....nor what solved it...
  • Eternity said:
    @TedTolboom

    I tried that, and it didn't work. But, guess what.... all three my FGS-222's are working again ! !

    I don't know what caused the problem....nor what solved it...
    Were you able to control any Z-wave device (only receive updates) and did you reboot Homey in between?
    if so, you had a similar issue as I experience: https://github.com/athombv/homey/issues/1442
  • EternityEternity Member
    edited April 2017
    PTP several times, as I needed Homey near the relay. 

    Other zwave devices still worked. 
  • My 3 Fibaro relays (FGS-222) have stopped working again....

    So, for no apparent reason they stop working, and after a while function again... This must be Homey f/w related.
  • Eternity said:
    My 3 Fibaro relays (FGS-222) have stopped working again....

    So, for no apparent reason they stop working, and after a while function again... This must be Homey f/w related.
    @Eternity which Homey software version are you using 1.1.9 or 1.2.0-RCxx?
    Latest experimental build (1.2.0-RC12) has some additional improvements to the Z-wave system...
  • EternityEternity Member
    edited April 2017
    @TedTolboom

    I am on the latest f/w RC12. 

    But, they are working again! As my curtains were opened in the middle of the night, I thought Homey must of updated itself overnight. => it did :-)

    It's working again. 
  • Hi,

    is it possible to add the Protection Mode setting to the FGR-222 Roller Shutter?

    In Protection Mode it will not be possible to control FIBARO Roller Shutter 2 from buttons. It is not recomended to control all Roller Shutters in this mode.

    1. Local Protection
      Local Protection State:
      0 – no protection. Roller Shutter responds to push buttons.
      1 – not supported
      2 – Local protection active. Roller Shutter does not respond to push buttons.
      Once the Local Protection is activated, the module stops responding to S1 and S2 push buttons. SCENE ID and association commands will not be sent as well. The only exception is the B-button. Menu and Z-Wave network inclusion, after the B-button or S1 push button triple click, are still active.

    I made a new issue request at github but no response.

  • @madmax I think this is more a Fibaro issue then a Homey issue. It should be possible to use the protection mode using the "Raw configuration parameters". However, the manual (http://manuals.fibaro.com/roller-shutter-2/) is a bit vague. 
    I think the "1. local protection" indicated it uses parameter 1 because the line is similarly formatted to the advanced parameters lower in the manual. You can try to enter "1,1,2" and see if you successfully deactivated the push buttons. There should be no harm in trying this out and otherwise, there is always the factory reset procedure.

    If you want to enable/disable protection mode via flows, an enhancement will need to be made, but since it would be a bit of an obscure usecase it might have low priority. Perhaps someone from the community can implement it. 

This discussion has been closed.