Best Fibaro Dimmer 2 driver?

🛎️ Get Help Devices
21

For inclusion or exclusion you can just toggle the light switch 3 times rather than having to get the device out, does the same as the B button for that. But I've also used the B button too with the same results.

The only time I can see config messages is after Inclusion and pressing the Save parameters button.

dev:692019-07-30 21:53:24.770 debugLivingroom Lights parameter '54' with a byte size of '1' is set to '0'

dev:692019-07-30 21:53:23.230 debugLivingroom Lights parameter '53' with a byte size of '2' is set to '10'

dev:692019-07-30 21:53:21.709 debugLivingroom Lights parameter '52' with a byte size of '2' is set to '3600'

dev:692019-07-30 21:53:20.185 debugLivingroom Lights parameter '50' with a byte size of '1' is set to '0'

dev:692019-07-30 21:53:18.674 debugLivingroom Lights parameter '44' with a byte size of '2' is set to '600'

dev:692019-07-30 21:53:17.135 debugLivingroom Lights parameter '43' with a byte size of '1' is set to '1'

dev:692019-07-30 21:53:15.656 debugLivingroom Lights parameter '42' with a byte size of '1' is set to '3'

dev:692019-07-30 21:53:14.138 debugLivingroom Lights parameter '41' with a byte size of '1' is set to '2'

dev:692019-07-30 21:53:12.636 debugLivingroom Lights parameter '40' with a byte size of '1' is set to '0'

dev:692019-07-30 21:53:11.098 debugLivingroom Lights parameter '39' with a byte size of '2' is set to '250'

dev:692019-07-30 21:53:09.589 debugLivingroom Lights parameter '35' with a byte size of '1' is set to '1'

dev:692019-07-30 21:53:08.080 debugLivingroom Lights parameter '28' with a byte size of '1' is set to '0'

dev:692019-07-30 21:53:06.538 debugLivingroom Lights parameter '26' with a byte size of '1' is set to '0'

dev:692019-07-30 21:53:05.026 debugLivingroom Lights parameter '23' with a byte size of '1' is set to '1'

dev:692019-07-30 21:53:03.493 debugLivingroom Lights parameter '22' with a byte size of '1' is set to '0'

dev:692019-07-30 21:53:01.974 debugLivingroom Lights parameter '20' with a byte size of '1' is set to '1'

dev:692019-07-30 21:53:00.452 debugLivingroom Lights parameter '19' with a byte size of '1' is set to '0'

dev:692019-07-30 21:52:58.957 debugLivingroom Lights parameter '10' with a byte size of '2' is set to '0'

dev:692019-07-30 21:52:57.431 debugLivingroom Lights parameter '9' with a byte size of '1' is set to '1'

dev:692019-07-30 21:52:55.914 debugLivingroom Lights parameter '8' with a byte size of '2' is set to '5'

dev:692019-07-30 21:52:54.417 debugLivingroom Lights parameter '7' with a byte size of '1' is set to '1'

dev:692019-07-30 21:52:52.884 debugLivingroom Lights parameter '6' with a byte size of '2' is set to '1'

dev:692019-07-30 21:52:51.379 debugLivingroom Lights parameter '5' with a byte size of '1' is set to '1'

dev:692019-07-30 21:52:49.863 debugAssociationReport AssociationReport(groupingIdentifier:2, maxNodesSupported:5, reportsToFollow:0, nodeId:[1])

dev:692019-07-30 21:52:46.835 debugAssociationReport AssociationReport(groupingIdentifier:1, maxNodesSupported:1, reportsToFollow:0, nodeId:[1])

dev:692019-07-30 21:52:43.829 debugFirmware Report FirmwareMdReport(checksum:null, firmwareId:null, manufacturerId:null)

dev:692019-07-30 21:52:43.635 debugCurrent value of parameter 54 is unknown

dev:692019-07-30 21:52:43.631 debugCurrent value of parameter 53 is unknown

dev:692019-07-30 21:52:43.628 debugCurrent value of parameter 52 is unknown

dev:692019-07-30 21:52:43.626 debugCurrent value of parameter 50 is unknown

dev:692019-07-30 21:52:43.623 debugCurrent value of parameter 44 is unknown

dev:692019-07-30 21:52:43.620 debugCurrent value of parameter 43 is unknown

dev:692019-07-30 21:52:43.618 debugCurrent value of parameter 42 is unknown

dev:692019-07-30 21:52:43.615 debugCurrent value of parameter 41 is unknown

dev:692019-07-30 21:52:43.612 debugCurrent value of parameter 40 is unknown

dev:692019-07-30 21:52:43.609 debugCurrent value of parameter 39 is unknown

dev:692019-07-30 21:52:43.607 debugCurrent value of parameter 35 is unknown

dev:692019-07-30 21:52:43.604 debugCurrent value of parameter 28 is unknown

dev:692019-07-30 21:52:43.601 debugCurrent value of parameter 26 is unknown

dev:692019-07-30 21:52:43.599 debugCurrent value of parameter 23 is unknown

dev:692019-07-30 21:52:43.596 debugCurrent value of parameter 22 is unknown

dev:692019-07-30 21:52:43.593 debugCurrent value of parameter 20 is unknown

dev:692019-07-30 21:52:43.590 debugCurrent value of parameter 19 is unknown

dev:692019-07-30 21:52:43.587 debugCurrent value of parameter 10 is unknown

dev:692019-07-30 21:52:43.584 debugCurrent value of parameter 9 is unknown

dev:692019-07-30 21:52:43.581 debugCurrent value of parameter 8 is unknown

dev:692019-07-30 21:52:43.572 debugCurrent value of parameter 7 is unknown

dev:692019-07-30 21:52:43.569 debugCurrent value of parameter 6 is unknown

dev:692019-07-30 21:52:43.566 debugCurrent value of parameter 5 is unknown

dev:692019-07-30 21:52:43.521 debugSetting association group 2

dev:692019-07-30 21:52:43.518 debugSetting association group 1

dev:692019-07-30 21:52:43.515 debugRequesting device firmware version

dev:692019-07-30 21:52:43.474 debugupdated() is being called

dev:12019-07-30 21:51:09.729 infoSpare Motion Sensor: motion is inactive

dev:692019-07-30 21:50:52.832 debugskip: Crc16Encap(checksum:65535, command:6, commandClass:112, data:[58, 1, 0])

dev:692019-07-30 21:50:52.828 debugparse description: zw device: 14, command: 5601, payload: 70 06 3A 01 00 1D 2A , isMulticast: false

dev:692019-07-30 21:50:52.820 debugskip: Crc16Encap(checksum:65535, command:6, commandClass:112, data:[33, 1, 0])

dev:692019-07-30 21:50:52.813 debugparse description: zw device: 14, command: 5601, payload: 70 06 21 01 00 AE B8 , isMulticast: false

dev:692019-07-30 21:50:52.801 debugskip: Crc16Encap(checksum:65535, command:6, commandClass:112, data:[32, 1, 2])

dev:692019-07-30 21:50:52.796 debugparse description: zw device: 14, command: 5601, payload: 70 06 20 01 02 B9 CA , isMulticast: false

dev:692019-07-30 21:50:52.774 debugskip: Crc16Encap(checksum:65535, command:6, commandClass:112, data:[30, 1, 2])

dev:692019-07-30 21:50:52.767 debugskip: Crc16Encap(checksum:65535, command:6, commandClass:112, data:[31, 1, 1])

dev:692019-07-30 21:50:52.763 debugparse description: zw device: 14, command: 5601, payload: 70 06 1F 01 01 60 3D , isMulticast: false

dev:692019-07-30 21:50:52.760 debugparse description: zw device: 14, command: 5601, payload: 70 06 1E 01 02 67 6E , isMulticast: false

dev:692019-07-30 21:50:52.737 debugskip: Crc16Encap(checksum:65535, command:6, commandClass:112, data:[14, 1, 1])

dev:692019-07-30 21:50:52.732 debugparse description: zw device: 14, command: 5601, payload: 70 06 0E 01 01 14 6E , isMulticast: false

dev:692019-07-30 21:50:52.722 debugskip: Crc16Encap(checksum:65535, command:6, commandClass:112, data:[2, 1, 70])

dev:692019-07-30 21:50:52.713 debugparse description: zw device: 14, command: 5601, payload: 70 06 02 01 46 59 2C , isMulticast: false

dev:692019-07-30 21:50:52.701 debugskip: Crc16Encap(checksum:65535, command:6, commandClass:112, data:[1, 1, 6])

dev:692019-07-30 21:50:52.692 debugparse description: zw device: 14, command: 5601, payload: 70 06 01 01 06 48 B8 , isMulticast: false

dev:692019-07-30 21:50:37.811 infoFibaro Dimmer is off [digital]

dev:692019-07-30 21:50:37.756 debugdimmerEvents value: 0

dev:692019-07-30 21:50:37.752 infoBasicReport value: 0

dev:692019-07-30 21:50:37.748 debugparse description: zw device: 14, command: 2003, payload: 00 , isMulticast: false

sys:12019-07-30 21:50:37.438 infoZ-Wave Discovery Stopped

sys:12019-07-30 21:50:37.435 infoZ-Wave Device Discovered: Fibaro Dimmer

dev:692019-07-30 21:50:37.425 debugrefresh

dev:692019-07-30 21:50:37.344 warnconfigure...

sys:12019-07-30 21:50:32.165 infoInitializing Z-Wave Device : 14

sys:12019-07-30 21:50:19.144 infoZ-Wave Discovery Running

22

Sorry mate, was the only thing i found that worked for me.

I'm out of ideas for you i'm afraid. Hope you manage to find the solutions.

23

It looks like the "SwitchMultilevelReport" isn't getting parsed. Was the dimmer included in secure mode or non-secure mode?

24

That was non-secure mode.

25

I've emailed Fibaro to ask about how to get the Firmware upgraded in case that is the issue.

I've also ordered a new Fibaro Dimmer 2 with firmware 3.5 and an Aoetec Nano Dimmer to test.

I really appreciate you help on this issue so far :slight_smile:

1 Like
26

I've now installed a Fibaro Dimmer 2 with firmware 3.5 but am seeing the exact same results all works apart from feedback from the physical switch to the driver when turned On/Off.

Below is the entries in the log when the physical switch is turned from Off to On, are there supposed to be Unhandled Z-Wave Events in the log? I've also attached screenshots in the hope that someone may spot the issue :slight_smile:

dev:1612019-08-05 13:43:06.314 debugSensorMultilevelReport: SensorMultilevelReport(precision:1, scale:0, sensorType:4, sensorValue:[0, 198], size:2, scaledSensorValue:19.8)

dev:1612019-08-05 13:43:01.301 debugSensorMultilevelReport: SensorMultilevelReport(precision:1, scale:0, sensorType:4, sensorValue:[0, 43], size:2, scaledSensorValue:4.3)

dev:1612019-08-05 13:43:01.136 debugUnhandled Z-Wave Event: SwitchMultilevelReport(value:99)

dev:1612019-08-05 13:43:00.615 debugUnhandled Z-Wave Event: BasicSet(value:255)

dev:1612019-08-05 13:43:00.586 debugbuttonEvent() Button:1, Value:held

dev:1612019-08-05 13:43:00.583 debugUnhandled Z-Wave Event: BasicSet(value:255)

dev:1612019-08-05 13:43:00.580 debugSwitch configured as Toggle

dev:1612019-08-05 13:43:00.564 debugConfiguration for preference "Switch Type" is set to 1

dev:1612019-08-05 13:43:00.561 debugdimmingDuration: 0

dev:1612019-08-05 13:43:00.558 debugsceneId: 10

dev:1612019-08-05 13:43:00.554 debugSceneActivationSet: SceneActivationSet(dimmingDuration:0, sceneId:10)

Capture1
Capture1.JPG1441×638 56.1 KB
Capture2
Capture2.JPG1597×808 170 KB
Capture3
Capture3.JPG1569×917 191 KB
Capture4
Capture4.JPG1599×734 65.3 KB
Capture5
Capture5.JPG1630×575 53.5 KB

27

Just want to +1 that I am having the same problems as you are, the on/off state (in the hub) is not reflected when changing state physically. Mine does not change state when doing it from the interface either. I have to the refresh command button for it to update in the UI.

I am also seeing similar (likely same) errors in the log "unhandled z-wave event"
Is there something related to us having the EU version of the hub and devices?

I have tried both the official and the erocm123 drivers. Also, neither of these drivers seem capable of updating any parameter values of the device. I have to use the basic z-wave tool to set the switch type for example.

28

I managed to modify the erocm123 Fibaro Dimmer 2 driver (GitHub - erocm123/Hubitat) so that it detects on/off via the button, I created a pull request with the change incase anyone with problems want to try it out.

29

Is anyone getting any errors from this updated driver? I've had 2 of these fibaro dimmers for over a year on hubitat using Erics previous driver. I recently purchased another hub to separate my old non plus devices and my newer z wave plus devices. I've excluded the dimmers and factory reset them, then re-included and swapped drivers. After setting the params I'm attempting to send the config but keep getting the error:

java.lang.NullPointerException: Cannot invoke method and() on null object on line 65 (parse)

Im also seeing this error when I turn the device on/off from the device page:

dev:15952020-04-21 06:37:25.320 pm errorjava.lang.NullPointerException: Cannot invoke method and() on null object on line 65 (parse)

dev:15952020-04-21 06:37:25.139 pm debugRequesting device firmware version

dev:15952020-04-21 06:37:25.087 pm infoOFF sent

I've also lost the button presses for s2 as well, i'm not even seeing push/hold under current states. I also excluded, reset and re-included with the same results. I'm no dev but it seems like the config is never sent because of the error. Thanks for any help.

1 Like
30

I get exactly the same as you and have searching for answers.

Did you have any luck?

1 Like
31

Mine work? There does seem to be some in consistency to the dimmer bits at times but the buttons always worked.

32

@AutoM8 @mark.oswell

I'm seeing the same error in my logs whenever a switch is toggled:

java.lang.NullPointerException: Cannot invoke method and() on null object on line 65 (parse)

I don't know when exactly it started, and I'm not actually seeing any ill effects in my system; all my switches still seem to work fine, even one for which I had setup S2. I wonder if that's because my device was already configured before this error started happening. I haven't tried re-configuring it, and I'm not sure I want to try that right now :slight_smile:

But... If this error is in fact preventing the driver from configuring your device, you could probably try setting all your desired options manually using the "Basic Z-Wave Tool" and then, once the options are all set, if you switch the driver back to Eric's, you might find that it all works properly again (even if the error still appears in the logs). FYI, I tried switching my driver to the newer built-in Hubitat driver, just to see if S2 would work after being configured previously, but it did not. I switched the driver back to Eric's, and S2 still works.

@ericm, any chance you know off-hand what the error might be? Maybe there's a simple explanation and fix?

1 Like
33

I had this set up and working perfectly with the ericm driver at my old house. I have just built and moved in, set everything up from scratch exactly the same and now have the problems mentioned above....

I have also lost the S2 ability. I'm really disappointed, this was such a good setup.

@ericm - are you able to shed any light?

34

You helped me design my setup and it was all working great. I reset all my devices ands set up from scratch in the new house, using exactly the same design but am now seeing the issues others are... So it would seem that if you haven't changed or updated anything you are safe from the issues.

35

Have you tried my idea of setting up the switch options using Basic Z-Wave Tool, then switching back to Eric's driver?

36

If lots of people are using the device as buttons aswell it might be something the team will add to the built in driver if we ask? I have also asked @bcopeland if he wouldn't mind looking at doing it.

1 Like
37

I lost this the other day the only thing that fixed it was a factory reset (once excluded) then re include it. I matched all the parameters with one that was working using the basic z-wave tool (they were already matched) but it didn't make a difference. The factory reset was the only thing to fix it.

I have brought a Fibaro hub and am trying to update everything, it's not going well, haven't been able to find it. Their system is crap!

38

Just to clarify - when you lost s2 capability you excluded the Fibaro Dimmer, factory reset the Fibaro Dimmer and then re-included it? Did you change anything on your hub? Remove and reinstall drivers or anything?
If you look at the logs when using the Fibaro Dimmer with the ericm driver, are you still seeing that above error?

39

I'd love to see that. Seems like the simpler option (for the end user) to just have it enabled in the inbuilt driver. Don't know why you wouldn't when the device has it.

40

Yeah, just like @BorrisTheCat, no difference.