Announcement

Collapse
No announcement yet.

Fibaro Dimmer 2 FGD-212 Central Scene device?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Fibaro Dimmer 2 FGD-212 Central Scene device?

    In accordance with the z-wave pluging changelog the Dimmer2 should have a scene activation device:

    Changed in version 3.0.1.154 (Beta)
    * For Fibaro Dimmer2, added a scene activation device so events can be triggered on scene commands sent from dimmers

    This works withs with the Fibaro Double Switch, se attached image.

    Rescan of Dimmer2 with latest beta z-wave plugin .207. No scene device created. The dimmer 2 was included with plugin version .188
    Code:
    apr-05 11.53.14	 	Z-Wave	9 out of 9 Child devices of node 139 were created successfully.
    apr-05 11.53.11	 	Z-Wave	Getting association information for 2. etg Hovedsov Taklampe, root
    apr-05 11.53.08	 	Z-Wave	Assigning return route from node 1 to 2. etg Hovedsov Taklampe, root
    apr-05 11.53.07	 	Z-Wave	Z-Stick: Adding association for Z-Wave device 2. etg Hovedsov Taklampe, root (Node 139, Group 2, Endpoint 2) to HomeSeer
    apr-05 11.53.03	 	Z-Wave	Assigning return route from node 1 to 2. etg Hovedsov Taklampe, root
    apr-05 11.53.02	 	Z-Wave	Z-Stick: Adding association for Z-Wave device 2. etg Hovedsov Taklampe, root (Node 139, Group 1, Endpoint 1) to HomeSeer
    apr-05 11.53.02	 	Z-Wave	All associations for node 139 have been retrieved successfully, it supports associations on these groups: 1, 2, 3, 4, 5.
    apr-05 11.53.02	 	Z-Wave	Node 139 Association Group 5 can have 8 associations, and currently has 1
    apr-05 11.53.02	 	Z-Wave	Node 139 Association Group 4 can have 8 associations, and currently has 1
    apr-05 11.53.02	 	Z-Wave	Node 139 Association Group 3 can have 8 associations, and currently has 1
    apr-05 11.53.02	 	Z-Wave	Node 139 Association Group 2 can have 8 associations, and currently has 1
    apr-05 11.53.02	 	Z-Wave	Node 139 Association Group 1 can have 1 associations, and currently has 1
    apr-05 11.52.59	 	Z-Wave	Getting association information for node 139
    apr-05 11.52.57	 	Z-Wave	Node 139 Meter is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
    apr-05 11.52.57	 	Z-Wave	Node 139 Meter is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
    apr-05 11.52.57	 	Z-Wave	Processing Information for Node 139 Multi-CHANNEL Command Class of SWITCH_MULTILEVEL_V3, Endpoint 2
    apr-05 11.52.55	 	Z-Wave	Processing Information for Node 139 Multi-CHANNEL Command Class of NOTIFICATION_V6, Endpoint 1
    apr-05 11.52.54	 	Z-Wave	Processing Information for Node 139 Multi-CHANNEL Command Class of SENSOR_MULTILEVEL_V7, Endpoint 1
    apr-05 11.52.54	 	Z-Wave	Node 139 Meter Instance 1 is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
    apr-05 11.52.54	 	Z-Wave	Node 139 Meter Instance 1 is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
    apr-05 11.52.54	 	Z-Wave	Processing Information for Node 139 Multi-CHANNEL Command Class of METER_V3, Endpoint 1
    apr-05 11.52.54	 	Z-Wave	Processing Information for Node 139 Multi-CHANNEL Command Class of SWITCH_MULTILEVEL_V3, Endpoint 1
    apr-05 11.52.52	 	Z-Wave	Node 139 is a Z-Wave Plus node. Retrieving ZWPlus Info...
    apr-05 11.52.52	 	Z-Wave	Node 139 is Z-Wave version: Lib: 4,05 App: 3.4
    apr-05 11.52.51	 	Z-Wave	Node: 139 Controls Class(es): SCENE_ACTIVATION
    apr-05 11.52.51	 	Z-Wave	Node: 139 Supports Class(es): ZWAVEPLUS_INFO, BASIC_V2, VERSION_V2, MANUFACTURER_SPECIFIC_V2, SWITCH_MULTILEVEL_V3, DEVICE_RESET_LOCALLY, ASSOCIATION_GRP_INFO_V2, ASSOCIATION_V2, POWERLEVEL, FIRMWARE_UPDATE_MD_V2, CRC_16_ENCAP, CONFIGURATION_V4, SENSOR_MULTILEVEL_V7, METER_V3, MULTI_CHANNEL_ASSOCIATION_V3, MULTI_CHANNEL_V3, PROTECTION_V2, NOTIFICATION_V6, SWITCH_ALL, APPLICATION_STATUS
    Firmware 3.4 on my dimmer 2. Do I need firmware 3.5 or is it something wrong with my HS3-system?
    Attached Files

    #2
    Originally posted by iceball View Post
    In accordance with the z-wave pluging changelog the Dimmer2 should have a scene activation device:

    Changed in version 3.0.1.154 (Beta)
    * For Fibaro Dimmer2, added a scene activation device so events can be triggered on scene commands sent from dimmers

    This works withs with the Fibaro Double Switch, se attached image.

    Rescan of Dimmer2 with latest beta z-wave plugin .207. No scene device created. The dimmer 2 was included with plugin version .188
    Code:
    apr-05 11.53.14	 	Z-Wave	9 out of 9 Child devices of node 139 were created successfully.
    apr-05 11.53.11	 	Z-Wave	Getting association information for 2. etg Hovedsov Taklampe, root
    apr-05 11.53.08	 	Z-Wave	Assigning return route from node 1 to 2. etg Hovedsov Taklampe, root
    apr-05 11.53.07	 	Z-Wave	Z-Stick: Adding association for Z-Wave device 2. etg Hovedsov Taklampe, root (Node 139, Group 2, Endpoint 2) to HomeSeer
    apr-05 11.53.03	 	Z-Wave	Assigning return route from node 1 to 2. etg Hovedsov Taklampe, root
    apr-05 11.53.02	 	Z-Wave	Z-Stick: Adding association for Z-Wave device 2. etg Hovedsov Taklampe, root (Node 139, Group 1, Endpoint 1) to HomeSeer
    apr-05 11.53.02	 	Z-Wave	All associations for node 139 have been retrieved successfully, it supports associations on these groups: 1, 2, 3, 4, 5.
    apr-05 11.53.02	 	Z-Wave	Node 139 Association Group 5 can have 8 associations, and currently has 1
    apr-05 11.53.02	 	Z-Wave	Node 139 Association Group 4 can have 8 associations, and currently has 1
    apr-05 11.53.02	 	Z-Wave	Node 139 Association Group 3 can have 8 associations, and currently has 1
    apr-05 11.53.02	 	Z-Wave	Node 139 Association Group 2 can have 8 associations, and currently has 1
    apr-05 11.53.02	 	Z-Wave	Node 139 Association Group 1 can have 1 associations, and currently has 1
    apr-05 11.52.59	 	Z-Wave	Getting association information for node 139
    apr-05 11.52.57	 	Z-Wave	Node 139 Meter is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
    apr-05 11.52.57	 	Z-Wave	Node 139 Meter is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
    apr-05 11.52.57	 	Z-Wave	Processing Information for Node 139 Multi-CHANNEL Command Class of SWITCH_MULTILEVEL_V3, Endpoint 2
    apr-05 11.52.55	 	Z-Wave	Processing Information for Node 139 Multi-CHANNEL Command Class of NOTIFICATION_V6, Endpoint 1
    apr-05 11.52.54	 	Z-Wave	Processing Information for Node 139 Multi-CHANNEL Command Class of SENSOR_MULTILEVEL_V7, Endpoint 1
    apr-05 11.52.54	 	Z-Wave	Node 139 Meter Instance 1 is Supported for Electric_meter, Type ELECTRIC_W, Scale is INSTANT
    apr-05 11.52.54	 	Z-Wave	Node 139 Meter Instance 1 is Supported for Electric_meter, Type ELECTRIC_kWh, Scale is ACCUMULATED
    apr-05 11.52.54	 	Z-Wave	Processing Information for Node 139 Multi-CHANNEL Command Class of METER_V3, Endpoint 1
    apr-05 11.52.54	 	Z-Wave	Processing Information for Node 139 Multi-CHANNEL Command Class of SWITCH_MULTILEVEL_V3, Endpoint 1
    apr-05 11.52.52	 	Z-Wave	Node 139 is a Z-Wave Plus node. Retrieving ZWPlus Info...
    apr-05 11.52.52	 	Z-Wave	Node 139 is Z-Wave version: Lib: 4,05 App: 3.4
    apr-05 11.52.51	 	Z-Wave	Node: 139 Controls Class(es): SCENE_ACTIVATION
    apr-05 11.52.51	 	Z-Wave	Node: 139 Supports Class(es): ZWAVEPLUS_INFO, BASIC_V2, VERSION_V2, MANUFACTURER_SPECIFIC_V2, SWITCH_MULTILEVEL_V3, DEVICE_RESET_LOCALLY, ASSOCIATION_GRP_INFO_V2, ASSOCIATION_V2, POWERLEVEL, FIRMWARE_UPDATE_MD_V2, CRC_16_ENCAP, CONFIGURATION_V4, SENSOR_MULTILEVEL_V7, METER_V3, MULTI_CHANNEL_ASSOCIATION_V3, MULTI_CHANNEL_V3, PROTECTION_V2, NOTIFICATION_V6, SWITCH_ALL, APPLICATION_STATUS
    Firmware 3.4 on my dimmer 2. Do I need firmware 3.5 or is it something wrong with my HS3-system?
    Hi

    I have just installed a number of Fibaro Dimmer 2's Version: 4.05 (ZDK 6.51.6) Firmware: 3.5 and am also wanting to trigger events based on a scene activation device. However, so far no such device is being created by my ZWave plugin version 3.0.1.210.

    Have you been able to make any further progress with this issue?

    Comment


      #3
      No, I was hoping HomeSeer tech would respond to this.

      Comment


        #4
        Hi, Just seeing if you have found a way to act on double clicks yet?

        Comment


          #5
          Originally posted by pricey1985@hotmail.com View Post
          Hi, Just seeing if you have found a way to act on double clicks yet?
          Only with global scene ID, which means a triple click on S2 (scene ID 25) will run the same event from all your Dimmer2.
          Under events just select IF Z-wave Scene ID XX is activated. You find the different scene IDs in the manual.

          Comment


            #6
            Thanks, at least this would give me one scene working in the house.

            This means that HomeSeer is able to receive the sceneID from the devices but just not acting on it correctly.

            Comment


              #7
              Doesn't a triple click on Dimmer 2 activate include/exclude mode?

              I really would like a proper fix for this. I've found 3 threads on this topic with no solution!

              I am running 3.0.1.190 and have tried re-adding multiple times with secure/non secure etc and failed to get a central scene device created.

              Has anyone worked this out?

              Comment


                #8
                Originally posted by Stevemeck View Post
                Doesn't a triple click on Dimmer 2 activate include/exclude mode?
                Triple with the B button on the back of the Fibaro, or FOUR clicks of the S1 switch.

                Comment


                  #9
                  Originally posted by Stevemeck View Post
                  Doesn't a triple click on Dimmer 2 activate include/exclude mode?
                  Triple click on s1 activates the include/exclude mode, but s2 allows you to do triple. So many people are having problems with this, I submited a bug report but they said it's working. More people that submit a report the better.

                  Comment


                    #10
                    Same here , i only managed to make it work with global scene IDs , no central scene device being created

                    Comment


                      #11
                      This is still (12 months on with numerous updates and attempts to get it working) not happening for me. Z-Wave plugin version is now 3.0.1.243 and I have 6 Fibaro Dimmer 2's on FW 3.4.

                      I have tried removal and re-adding, both secure and non secure. Everything seems to work as expected. I then set parameter 28 to '1' and re-scan the device... no scene device created.

                      I've tried a multitude of variations on this theme (re-adding after setting scene 28 to '1' / removal, full hardware reset of module and re-adding etc) and nothing seems to work. Is there anyone who has this working as expected and can provide step by step details? There are at least 3 other threads on this topic with lots of people asking the same question and no answers (other than update z-wave plugin and re-add).

                      Anyone cracked this?!

                      Comment


                        #12
                        I have half a house worth of these and have tried everything I can think of and have given up on it. All I can get is GlobalsceneID, which works fine but activates the same scene from every dimmer.

                        All I can suggest is raise a bug report and hope for the best, although when I raised one, they told me "everything is working fine" and closed the report straight away.

                        More people that report the better I guess.
                        Good luck.

                        Chris

                        Comment


                          #13
                          Originally posted by Pricey1985 View Post
                          I have half a house worth of these and have tried everything I can think of and have given up on it. All I can get is GlobalsceneID, which works fine but activates the same scene from every dimmer.

                          All I can suggest is raise a bug report and hope for the best, although when I raised one, they told me "everything is working fine" and closed the report straight away.

                          More people that report the better I guess.
                          Good luck.

                          Chris
                          Can you give me a hint how to work with GlobalsceneID.

                          Thank you

                          Comment


                            #14
                            Originally posted by Almighty View Post

                            Can you give me a hint how to work with GlobalsceneID.

                            Thank you
                            You can find this in events triggers. Select zwave actions and you can find the global scene triggers.

                            The IDs will be in Fibaro Dimmer 2 manual for S1 and S2 , I’m assuming you figured this out already if not it’s easy to activate it

                            Comment


                              #15
                              Originally posted by rmohsen View Post

                              You can find this in events triggers. Select zwave actions and you can find the global scene triggers.

                              The IDs will be in Fibaro Dimmer 2 manual for S1 and S2 , I’m assuming you figured this out already if not it’s easy to activate it
                              Thanks for fast reply, I'll try that when I get home.


                              I was just thinking, is there a way, to listen to changes of certain variables of the devices? I'm migrating from VeraPlus (well I may reconsider it, given the number of problems with fibaro scene activation on HomeSeer) and there was no official support for scene activation either, however you could make a script, that registered function which was fired whenever the LastSceneTime variable of the dimmer changed, then you just read the variable with scene id (LastSceneId) for that device and executed desired event.

                              Simple example of how things are done with Vera is at the attached link.

                              Comment

                              Working...
                              X