Announcement

Collapse
No announcement yet.

3.0.1.154 and Fibaro Dimmer2

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

    3.0.1.154 and Fibaro Dimmer2

    Hello all,

    I recently purchased a Fibaro Dimmer2 and am interested in using it with a pair of momentary switches to control a dimmable light. The first step in the project is to get the Fibaro device working with Homeseer, which I am having trouble with. I have read multiple threads on this board but none of them quite describes the issue I am having. I think the difference is that since I just bought my dimmer a few days ago, it has Firmware 3.5 (the other threads mention v3.2 and 3.3 but not 3.5).

    I have tried including the device both securely and non-secure and the behavior is the same. The device includes without error and creates a bunch of devices:

    Click image for larger version

Name:	Screen Shot 2017-11-10 at 11.52.29 AM.png
Views:	1
Size:	108.8 KB
ID:	1211585

    Whenever I switch one of the physical switches (either S1 or S2) I see the following in my log:

    Nov-10 11:45:46 AM Z-Wave Error Node Change Event for Node 187 on Network 0184EF25, CC=COMMAND_CLASS_CONFIGURATION_V3 but no valid devices were found. (70-06-0D-01)
    Nov-10 11:45:46 AM Z-Wave Error Node Change Event for Node 187 on Network 0184EF25, CC=COMMAND_CLASS_CONFIGURATION_V3 but no valid devices were found. (70-06-0D-01-00)
    Nov-10 11:45:45 AM Z-Wave Error Node Change Event for Node 187 on Network 0184EF25, CC=COMMAND_CLASS_CONFIGURATION_V3 but no valid devices were found. (70-06-0D-01)
    Nov-10 11:45:45 AM Z-Wave Error Node Change Event for Node 187 on Network 0184EF25, CC=COMMAND_CLASS_CONFIGURATION_V3 but no valid devices were found. (70-06-0D-01-01)


    So it looks like communication works between the devices, but Homeseer doesn't understand what the Fibaro device is trying to say. Is anyone else seeing this?

    For reference, here is my system info:

    HomeSeer Version: HS3 Pro Edition 3.0.0.379
    Linux version: Linux homeseer 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 0 Days 0 Hours 30 Minutes 52 Seconds
    IP Address: 172.16.100.132
    Number of Devices: 437
    Number of Events: 90
    Available Threads: 199
    HSTouch Enabled: True
    Event Threads: 0
    Event Trigger Eval Queue: 0
    Event Trigger Priority Eval Queue: 0
    Device Exec Queue: 0
    Plugin Callback Queue: 0
    HSTouch Event Queue: 0
    Email Send Queue: 0
    Anti Virus Installed:

    Enabled Plug-Ins
    3.0.0.37: EasyTrigger
    3.5.1029.11: HSBuddy
    3.0.0.6: Log2Syslog
    0.0.0.34: Pushover 3P
    3.0.0.76: weatherXML
    3.0.1.154: Z-Wave

    Thanks.

    #2

    Comment


      #3
      Ok, I think I got it figured out...

      I didn't have a load hooked up to the Dimmer while I was testing. Apparently, this new generation is smart enough to know that the "light bulb is burned out" (i.e. no load connected). It then a) tells Homesser this (the message it doesn't understand most likely) and b) doesn't turn on or off. Hooking a light up seems to have fixed everything.

      Comment


        #4
        I just went through something along these lines with the Dimmer 2. I even created a bugzilla https://forums.homeseer.com/bugzilla...ug.cgi?id=3548.

        The root cause or problem depending which side of the fence you're on, is that the device needs to be included as non-secure. It was amazing the difference in response, proper function of energy reporting, etc.

        BTW, mine also has FW 3.5.

        Based on what I learned from this experience, I plan on excluding other devices that don't function the way I would expect and then including non-secure.

        Supposedly there is a new "secure" protocol that will be more efficient.

        Comment

        Working...
        X