›
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)

1…89111314…31

Comments

  • roelvdbergeroelvdberge Member
    roelvdberge said:

    I responded to the issue on GitHub. They say that resetting Homey should trigger the Z-Wave reset but in my case it didn't solve anything. Any more ideas? 
    Powering Homey off and on again did solve the issue. My flows worked again and the dimmers could be controlled through Homey again.
  • blusserblusser Member
    @caseda said:

    But still, if i had one i could try to debug this issue, maybe it has already been fixed in my (ex) pull request?
    would like to hear when it lands in the app store (should be today or tomorrow).
    Is today or tomorrow "promised" by athom or your owm educatued guess ?
    I'm realy looking foward to this update so I'm able to include a lot of relay switches :+1: 
  • casedacaseda Member
    blusser said:
    Is today or tomorrow "promised" by athom or your owm educatued guess ?
    I'm realy looking foward to this update so I'm able to include a lot of relay switches :+1: 
    LOL, athom and promised in one sentence.

    it's just an educated guess, it doesn't change much of the internal coding (it's mostly all the same coding way), so not that much testing is needed before being accepted into the store.
  • blusserblusser Member
    @caseda,

    While we're joking about it, they seem to have accept you pull request :smile: 

    https://github.com/athombv/com.fibaro/commit/dda3ad148276950902a6d30cdf11ba31282eac62

    Hope it will survive their acceptance tests (assuming there are).
  • casedacaseda Member
    @blusser ;
    that's exactly the reason why i said today or tomorrow.
    If the pull request wasn't accepted it would have been a longer periode :smile:
  • Fire69Fire69 Member
    @caseda: don't know if you are aware (see Slack), @RobinBolscher has a working implementation for the FGRM-222, I'm testing it with him.  Hope you don't mind :)
  • casedacaseda Member
    @Fire69 ;
    i'm not on slack, so no i was not aware.
    But, really? i couldn't think of a way yet to make it work properly with both switches and outputs.

    What do you use to "listen" to both multichannelnodes of the multilevel_switch command class
  • Fire69Fire69 Member
    caseda said:
    @Fire69 ;
    i'm not on slack, so no i was not aware.
    But, really? i couldn't think of a way yet to make it work properly with both switches and outputs.

    What do you use to "listen" to both multichannelnodes of the multilevel_switch command class
    I have no clue how he did it, I'm no programmer :smiley: 
    Maybe you can contact him to see if his method can be of help for your relays?

    This is the list of classes you asked for a couple of days ago:
    [debug] ------------------------------------------
[debug] Node: c22be8ef-d095-4b98-bc51-e8af5c633f90
[debug] - Battery: false
[debug] - CommandClass: COMMAND_CLASS_MANUFACTURER_SPECIFIC
[debug] -- Version: 1
[debug] -- Commands:
[debug] --- MANUFACTURER_SPECIFIC_GET
[debug] --- MANUFACTURER_SPECIFIC_REPORT
[debug] - CommandClass: COMMAND_CLASS_VERSION
[debug] -- Version: 1
[debug] -- Commands:
[debug] --- VERSION_COMMAND_CLASS_GET
[debug] --- VERSION_COMMAND_CLASS_REPORT
[debug] --- VERSION_GET
[debug] --- VERSION_REPORT
[debug] - CommandClass: COMMAND_CLASS_CONFIGURATION
[debug] -- Version: 1
[debug] -- Commands:
[debug] --- CONFIGURATION_GET
[debug] --- CONFIGURATION_REPORT
[debug] --- CONFIGURATION_SET
[debug] - CommandClass: COMMAND_CLASS_ASSOCIATION
[debug] -- Version: 2
[debug] -- Commands:
[debug] --- ASSOCIATION_GET
[debug] --- ASSOCIATION_GROUPINGS_GET
[debug] --- ASSOCIATION_GROUPINGS_REPORT
[debug] --- ASSOCIATION_REMOVE
[debug] --- ASSOCIATION_REPORT
[debug] --- ASSOCIATION_SET
[debug] --- ASSOCIATION_SPECIFIC_GROUP_GET
[debug] --- ASSOCIATION_SPECIFIC_GROUP_REPORT
[debug] - CommandClass: COMMAND_CLASS_SWITCH_BINARY
[debug] -- Version: 1
[debug] -- Commands:
[debug] --- SWITCH_BINARY_GET
[debug] --- SWITCH_BINARY_REPORT
[debug] --- SWITCH_BINARY_SET
[debug] - CommandClass: COMMAND_CLASS_POWERLEVEL
[debug] -- Version: 1
[debug] -- Commands:
[debug] --- POWERLEVEL_GET
[debug] --- POWERLEVEL_REPORT
[debug] --- POWERLEVEL_SET
[debug] --- POWERLEVEL_TEST_NODE_GET
[debug] --- POWERLEVEL_TEST_NODE_REPORT
[debug] --- POWERLEVEL_TEST_NODE_SET
[debug] - CommandClass: COMMAND_CLASS_METER
[debug] -- Version: 2
[debug] -- Commands:
[debug] --- METER_GET
[debug] --- METER_REPORT
[debug] --- METER_RESET
[debug] --- METER_SUPPORTED_GET
[debug] --- METER_SUPPORTED_REPORT
[debug] - CommandClass: COMMAND_CLASS_SENSOR_MULTILEVEL
[debug] -- Version: 2
[debug] -- Commands:
[debug] --- SENSOR_MULTILEVEL_GET
[debug] --- SENSOR_MULTILEVEL_REPORT
[debug] - CommandClass: COMMAND_CLASS_FIRMWARE_UPDATE_MD
[debug] -- Version: 1
[debug] -- Commands:
[debug] --- FIRMWARE_MD_GET
[debug] --- FIRMWARE_MD_REPORT
[debug] --- FIRMWARE_UPDATE_MD_GET
[debug] --- FIRMWARE_UPDATE_MD_REPORT
[debug] --- FIRMWARE_UPDATE_MD_REQUEST_GET
[debug] --- FIRMWARE_UPDATE_MD_REQUEST_REPORT
[debug] --- FIRMWARE_UPDATE_MD_STATUS_REPORT
[debug] - CommandClass: COMMAND_CLASS_MANUFACTURER_PROPRIETARY
[debug] -- Version: 1
[debug] -- Commands:
[debug] - CommandClass: COMMAND_CLASS_PROTECTION
[debug] -- Version: 2
[debug] -- Commands:
[debug] --- PROTECTION_EC_GET
[debug] --- PROTECTION_EC_REPORT
[debug] --- PROTECTION_EC_SET
[debug] --- PROTECTION_GET
[debug] --- PROTECTION_REPORT
[debug] --- PROTECTION_SET
[debug] --- PROTECTION_SUPPORTED_GET
[debug] --- PROTECTION_SUPPORTED_REPORT
[debug] --- PROTECTION_TIMEOUT_GET
[debug] --- PROTECTION_TIMEOUT_REPORT
[debug] --- PROTECTION_TIMEOUT_SET
[debug] - CommandClass: COMMAND_CLASS_BASIC
[debug] -- Version: 1
[debug] -- Commands:
[debug] --- BASIC_GET
[debug] --- BASIC_REPORT
[debug] --- BASIC_SET
[debug] ------------------------------------------
  • RobinRobin Member

    @caseda it is just a basic implementation (just up/down), but the multilevel_switch cc you speak of, are you certain the device supports this? I can not find it in the documentation, and neither does the device advertise it is capable of this cc.
  • casedacaseda Member
    edited August 2016
    @Robin ;
    ah i see, the FGRM-222 uses binary switch, definitely need to look at more repositories when trying to create drivers

    I've been looking at the supported class shown on pepper and openhab, and they both use/say MultiLevel Switch cc when "controlling" the roller blind, this is for both the FGR-221 and FGRM-222

    and got the node info from @viktor yesterday, from the FGRM-222 (Roller Shutter 2), and it also states:
        "deviceClassGeneric": {
            "value": 17,
            "name": "GENERIC_TYPE_SWITCH_MULTILEVEL"

    and

        "commandClass": [
            {
                "value": 38,
                "name": "COMMAND_CLASS_SWITCH_MULTILEVEL",
                "version": 3
            },

    so even homey itself is stating it when giving the node info (not the debug)
    kinda weird it's different for the node_info (general device when no driver) and the debug log
  • Fire69Fire69 Member
    It wasn't in my debug info either. Only Sensor_MultiLevel, not Switch_MultiLevel. 
    It absolutely supports it, I used it like that before with my main controller (paired as a dimmer)
    It also reports its percentage. 
  • RobinRobin Member

    @Fire69 does it report is percentage on homey as well? As in, can you see that percentage incoming in the logging? If yes, what command class does it use to report this?
  • Fire69Fire69 Member
    No, don't see it on my Homey, probably because the class isn't implemented yet? 
  • RobinRobin Member
    That would be strange, I use SWITCH_MULTILEVELon Aeotec Dimmer and that works perfectly fine...
  • casedacaseda Member
    edited August 2016
    @Fire69 ;
    the multilevel sensor cc is a totally different command class then the multilevel switch cc.
    The switch cc is ment for dimmer purposes (almost the same as Binary Switch CC, just uses different data types)
    The sensor cc for multi purposes, like door/window contacts (which is called a sensor), and any data like temperature

    but until now it seems like all command classes have been implemented.
  • Fire69Fire69 Member
    Robin said:
    That would be strange, I use SWITCH_MULTILEVELon Aeotec Dimmer and that works perfectly fine...
    caseda said:
    but until now it seems like all command classes have been implemented.

    I meant implemented in the driver @RobinBolscher made for the fgrm-222. :smile: 
  • ArjanArjan Member
    edited August 2016
    Is there any chance the binary sensor is supported in the near future?
  • AljoenAljoen Member
    Will the driver for fgrm-222 V1 also be implemented? Only see the V2 in the new released app
  • Fire69Fire69 Member
    So you mean fgr-221?
  • RobinRobin Member
    Arjan said:
    Is there any chance the binary sensor is supported in the near future?
    I thought someone from the community was going to create a driver for that! (We don't have the device at the office at the moment)
    Aljoen said:
    Will the driver for fgrm-222 V1 also be implemented? Only see the V2 in the new released app
    Yep, either by community or once we receive one at the office ourselves!
  • djeskodjesko Member
    If anyone need some binary sensor info,  xml from fibaro let me know,  I need that one to work to  :)
  • ArjanArjan Member
    edited August 2016
    Robin said:
    Arjan said:
    Is there any chance the binary sensor is supported in the near future?
    I thought someone from the community was going to create a driver for that! (We don't have the device at the office at the moment)

    I haven't found a clear function for it so i haven't ordered it yet.

    @Robin, in my case i might not need the S2 switch at all times (Fibaro single relay), how do i get rid of the S2 device in Homey?
  • AljoenAljoen Member
    Robin said:
    Arjan said:
    Is there any chance the binary sensor is supported in the near future?
    I thought someone from the community was going to create a driver for that! (We don't have the device at the office at the moment)
    Aljoen said:
    Will the driver for fgrm-222 V1 also be implemented? Only see the V2 in the new released app
    Yep, either by community or once we receive one at the office ourselves!
    I have the fgrm-222v2.1-v2.3 (which is superseded by the fgrm-222 shutter 2..correct me if I am wrong).  I can offer to test this one,  if needed. 
  • casedacaseda Member
    @Aljoen ;
    What do you mean with superseded, makes no sense. 
    Fgrm-222 = fgrm-222 which has been implemented in 1.0.9. 
    That came in the app store yesterday
  • AljoenAljoen Member
    My manual and box states fgrm-222 shutter.  Nowadays version sold says fgrm-222 shutter 2.  I guess is same with dimmer vs dimmer 2 and therefote the FW? is different between the two versions.  But than again I am no expert,  just a simple user...
  • casedacaseda Member
    Nope
    FGR-221 = Roller Shutter (so v1)
    FGRM-222 = Roller Shutter 2 (and always been)

    Dimmer is about the same:
    FGD-211 = Dimmer (v1)
    FGD-212 = Dimmer 2

    So maybe just a re-package but the version is still 2.2-2.4 (2.5 only since shortly)

    no expert either, but not really a simple user as well :wink: 
  • AljoenAljoen Member
    Ok.  Will try to include my shutter this weekend..  Is now still under control of my veralite..  Hope it works coz have no manual backup....  Ah well leave the curtains open then :wink: 
  • cnvissercnvisser Member
    When i add my Roller Shutter 2 (FGR-222 not FGRM) it still says that there is no compatible app found and it will be added as a basic device.
    Homey 0.9.3 app 1.0.9

  • RobinRobin Member
    edited September 2016

    @cnvisser can you run the app from command line and PM me the console logging?

    EDIT: missed your mention of FGR. The app supports FGRM, not sure what the difference is yet.
  • casedacaseda Member
    @cnvisser ;
    I've been googling around, there is not that much information about it..
    but seems like the FGR-222 is the newer version (v2.5) of FGRM-222 (v2.2 - v2.4),

    included the device in my PR @Robin, needs to be a completely new device because the product type also changes, but its practically the same device
This discussion has been closed.