Fibaro Dimmer not reporting status, etc

[vicksen]

A few days ago, I had som issues with my hub, in particular some z-wave devices, see here: All devices under Z-Wave Details missing - #14 by vicksen

I seem to have recovered my z-wave devices but have had to exclude & include the dimmers: 2 Qubino minis & 1 Fibaro Dimmer 2 after weird behaviour. The Qubinos have sorted themselves out, but I'm having issues with the Fibaro.

I've done exclude, a recalibration on it, ie factory reset. Then included it into the hub again. Prior to inclusion, the physical switches behave as normal. Post-inclusion, using the default driver, the dimming function disappears, and it is no longer possible to turn off. It doesn't seem to report status on the device page. Sometimes it works to turn it on or off from there. Sometimes it works to set the level. Often it doesn't.

The logs show an error that I'm not sure what to do about. (MissingMethodException?)
At this point I've excluded it so I can at least use it manually.

I would appreciate any ideas on what could be the cause/what I can try to fix this. I can understand/write some basic code but I don't know enough to be able to write a driver, for example.

dev:1912024-01-20 19:36:37.624errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.basicv2.BasicReport, java.util.LinkedHashMap) values: [BasicReport(value:99, targetValue:0, duration:0), [32:1, 38:3, ...]]
Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1912024-01-20 19:36:37.566debugparse description: zw device: 19, command: 3105, payload: 04 22 03 BE , isMulticast: false

dev:1912024-01-20 19:36:37.566debugparse description: zw device: 19, command: 9881, payload: 00 20 03 63 , isMulticast: false

dev:1912024-01-20 19:36:37.330debugrefresh()

dev:1912024-01-20 19:36:32.013errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.switchmultilevelv4.SwitchMultilevelReport, java.util.LinkedHashMap) values: [SwitchMultilevelReport(value: 99, targetValue: 0, duration: 0), ...]
Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1912024-01-20 19:36:31.993debugparse description: zw device: 19, command: 9881, payload: 00 26 03 63 , isMulticast: false

dev:1912024-01-20 19:36:30.852debugon()

dev:1912024-01-20 19:36:30.181errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.switchmultilevelv4.SwitchMultilevelReport, java.util.LinkedHashMap) values: [SwitchMultilevelReport(value: 0, targetValue: 0, duration: 0), ...]
Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1912024-01-20 19:36:30.051debugparse description: zw device: 19, command: 9881, payload: 00 26 03 00 , isMulticast: false

dev:1912024-01-20 19:36:28.766debugoff()

[vicksen]

Update:
I re-included the Fibaro Dimmer again, and it works to turn off, on and set the level from its device page, using the Fibaro Dimmer driver. The logs show an error whenever I send a command. The device status doesn't show on the device page. The physical button no longer works.

See below!
dev:1932024-01-22 13:13:16.354debugparse description: zw device: 1B, command: 3105, payload: 04 22 03 D0 , isMulticast: false

dev:1932024-01-22 13:13:11.086errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.switchmultilevelv4.SwitchMultilevelReport, java.util.LinkedHashMap) values: [SwitchMultilevelReport(value: 99, targetValue: 0, duration: 0), ...] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:13:11.063debugparse description: zw device: 1B, command: 9881, payload: 00 26 03 63 , isMulticast: false

dev:1932024-01-22 13:13:10.578errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.multichannelv4.MultiChannelCmdEncap, java.util.LinkedHashMap) values: [hubitat.zwave.commands.multichannelv4.MultiChannelCmdEncap@1411783, ...] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:13:10.556debugparse description: zw device: 1B, command: 9881, payload: 00 60 0D 01 00 20 01 FF , isMulticast: false

dev:1932024-01-22 13:13:09.377debugparse description: zw device: 1B, command: 3105, payload: 04 22 01 34 , isMulticast: false

dev:1932024-01-22 13:13:08.952errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.switchmultilevelv4.SwitchMultilevelReport, java.util.LinkedHashMap) values: [SwitchMultilevelReport(value: 0, targetValue: 0, duration: 0), ...] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:13:08.931debugparse description: zw device: 1B, command: 9881, payload: 00 26 03 00 , isMulticast: false

dev:1932024-01-22 13:13:08.422errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.multichannelv4.MultiChannelCmdEncap, java.util.LinkedHashMap) values: [hubitat.zwave.commands.multichannelv4.MultiChannelCmdEncap@101fe02, ...] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:13:08.402debugparse description: zw device: 1B, command: 9881, payload: 00 60 0D 01 00 20 01 00 , isMulticast: false

dev:1932024-01-22 13:13:03.952errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.switchmultilevelv4.SwitchMultilevelReport, java.util.LinkedHashMap) values: [SwitchMultilevelReport(value: 99, targetValue: 0, duration: 0), ...] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:13:03.878debugparse description: zw device: 1B, command: 9881, payload: 00 26 03 63 , isMulticast: false

dev:1932024-01-22 13:13:03.727errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.multichannelv4.MultiChannelCmdEncap, java.util.LinkedHashMap) values: [hubitat.zwave.commands.multichannelv4.MultiChannelCmdEncap@e3d0a4, ...] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:13:03.687debugparse description: zw device: 1B, command: 9881, payload: 00 60 0D 01 00 20 01 63 , isMulticast: false

dev:1932024-01-22 13:08:27.568errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.basicv2.BasicReport, java.util.LinkedHashMap) values: [BasicReport(value:99, targetValue:0, duration:0), [32:1, 38:3, ...]] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:08:27.542debugparse description: zw device: 1B, command: 9881, payload: 00 20 03 63 , isMulticast: false

dev:1932024-01-22 13:08:27.409debugrefresh()

dev:1932024-01-22 13:08:26.277debugparse description: zw device: 1B, command: 3105, payload: 04 22 03 CD , isMulticast: false

dev:1932024-01-22 13:08:20.608errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.switchmultilevelv4.SwitchMultilevelReport, java.util.LinkedHashMap) values: [SwitchMultilevelReport(value: 99, targetValue: 0, duration: 0), ...] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:08:20.584debugparse description: zw device: 1B, command: 9881, payload: 00 26 03 63 , isMulticast: false

dev:1932024-01-22 13:08:20.365debugstopLevelChange()

dev:1932024-01-22 13:08:17.209errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.switchmultilevelv4.SwitchMultilevelReport, java.util.LinkedHashMap) values: [SwitchMultilevelReport(value: 99, targetValue: 0, duration: 0), ...] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:08:17.188debugparse description: zw device: 1B, command: 9881, payload: 00 26 03 63 , isMulticast: false

dev:1932024-01-22 13:08:14.577debugstartLevelChange(up)

dev:1932024-01-22 13:08:12.519errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.switchmultilevelv4.SwitchMultilevelReport, java.util.LinkedHashMap) values: [SwitchMultilevelReport(value: 50, targetValue: 0, duration: 0), ...] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:08:12.497debugparse description: zw device: 1B, command: 9881, payload: 00 26 03 32 , isMulticast: false

dev:1932024-01-22 13:08:12.322debugparse description: zw device: 1B, command: 3105, payload: 04 22 03 8B , isMulticast: false

dev:1932024-01-22 13:08:11.305debugsetLevel(50, 1)

dev:1932024-01-22 13:08:07.233errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.switchmultilevelv4.SwitchMultilevelReport, java.util.LinkedHashMap) values: [SwitchMultilevelReport(value: 99, targetValue: 0, duration: 0), ...] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:08:07.211debugparse description: zw device: 1B, command: 9881, payload: 00 26 03 63 , isMulticast: false

dev:1932024-01-22 13:08:06.069debugon()

dev:1932024-01-22 13:08:04.020errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.switchmultilevelv4.SwitchMultilevelReport, java.util.LinkedHashMap) values: [SwitchMultilevelReport(value: 0, targetValue: 0, duration: 0), ...] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:08:03.954debugparse description: zw device: 1B, command: 9881, payload: 00 26 03 00 , isMulticast: false

dev:1932024-01-22 13:08:02.720debugoff()

dev:1932024-01-22 13:07:24.941warndescription logging is: true

dev:1932024-01-22 13:07:24.938warndebug logging is: true

dev:1932024-01-22 13:07:24.932infoupdated...

dev:1932024-01-22 13:07:01.666errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.basicv2.BasicReport, java.util.LinkedHashMap) values: [BasicReport(value:99, targetValue:0, duration:0), [32:1, 38:3, ...]] Possible solutions: wait(), any(), trim(), next(), split(), dump() on line 76 (method parse)

dev:1932024-01-22 13:07:01.643debugparse description: zw device: 1B, command: 9881, payload: 00 20 03 63 , isMulticast: false

dev:1932024-01-22 13:07:01.042debugrefresh()

dev:1932024-01-22 13:07:00.985warnconfigure...

[jtp10181]

Screenshots of logs are much easier to read, since it is in the format we are used to seeing on our own hubs.

Also, what hub model and platform.
What is the device model? If not known the "data" section at the bottom of the device page has info that can be used to ID it.

Were you possibly using a custom driver for it before? You could check your driver code list to see if anything already installed rings a bell. Once you removed and included it again, it got reset to the system driver but you may have manually set it to a custom driver before.

[johnwill1]

@vicksen

Post-inclusion, using the default driver, the dimming function disappears, and it is no longer possible to turn off.

I had some issues with Dimmer 2's early on. After calibration they'd be off, then the first time I used the momentary switch they'd come on and stay on. Pressing and holding the switch they would turn off but as soon as I released my finger they'd come back on - frustrating.

I think it may have been the driver I was using and there may be some difference between the EU and other versions that the (community) driver didn't suit. In the end (after calibration) I changed the driver to 'Basic Z-Wave tool' and manually sent the parameters. Once complete I switched driver back to the inbuilt Hubitat one and all is well.

With the Basic Z-Wave tool, it was a case of opening a separate log window and clicking to get all parameters. Then I'd individually send each parameter and value that I wanted to change (seeing that update occur in the log window)

[vicksen]

This sounds exactly like what is happening to me. But I can't find "Basic Z-Wave tool" in the driver list... is this something I need to install?

[vicksen]

ah sorry, I will post som screenshots. It's a C-5, platform 2.3.7.145.
I used the Fibaro driver from the start, then when I had problems I tried the Generic Z-wave dimmer. That also didn't help. So I went back to the Fibaro. I haven't installed any user drivers for this device, I read on some forum that they don't work so well with the current iteration of hubitat/its platform.

Edited to change to z-wave from zigbee. brain fart!

[jtp10181]

The Generic Zigbee driver for sure will not work, it is a z-wave device.

The Basic Zwave tool you have to install the code for, it is not built in: Super basic Z-Wave parameter tool

Those errors are making me think this is a possible bug that was fixed in the 2.3.8 beta being tested right now.

@gopher.ny is this error above related to this fix?

• Fixed NotSerializableException for LazyMap error that was affecting a wide range of functionality.

[vicksen]

sorry I meant generic z-wave dimmer

[jtp10181]

Can you show a screenshot showing the Driver/Type selected, the "Data" at the bottom of the page, and also the "State Variables" and "Current States" at the top? Basically the entire device page but those are the specific things.

That error is very strange coming from a system driver, it would make me think there is no way that driver was working for anyone with those errors happening.

[johnwill1]

@vicksen

is this something I need to install?

I just checked. It is a Hubitat driver but isn't pre installed, I must've installed it from a link on this forum somewhere.

@vicksen

I read on some forum that they don't work so well with the current iteration of hubitat/its platform.

Because they are Z Wave 500 devices, when you include them to a C-7 or C-8 they pair with security set to 'S0' which is bad. The only way to include them with security set to 'none' (which is desirable) is to use a separate Z Wave stick and controller while including them. You have a C-5 so when you include ether you just need to select security as 'none' rather than 'S0' to avoid that problem. Other than that they work fine with Hubitat. I have around 20 and have been without issue for 3 years (apart from that initial teething)

When you switched to the Hubitat Fibaro Dimmer driver (from the incorrect Generic Zigbee) did you remember to click configure after setting preferences?

[vicksen]

I have installed the z-wave tool now.

I did press configure after changing drivers each time. (and it was the z-wave not the zigbee, my bad, I wrote the wrong thing).

[vicksen]

Some screenshots:

[johnwill1]

What about preferences? Do you see those? There should be one for switch type.

Also have a look in your Settings > Z Wave Details page. Has the device included with S0 or None for security? You can't change it once included so if it's S0 you want to be excluding it, then including it again with security as none. S0 is very chatty and can bring down a Z Wave mesh.

[vicksen]

@johnwill1

The only way to include them with security set to 'none'

I noticed that it says on the device page that secure pairing is 'true' which sounds incorrect from what you're saying here.
I'm just wondering, these are new devices and the box says z-wave plus. But that doesn't mean secure joining?

[johnwill1]

Z wave plus means that the devices report their status back to the hub without needing to be polled but it doesn't mean they're securely paired. It's counterintuitive I know, but you don't want security for anything other than locks, garage doors or alarm devices.

@jtp10181 Doyou know how to work out what the security is on a C5 connected device? Does it show in the Z Wave details page the same or do you need to work it out from clusters?

[vicksen]

@johnwill1

What about preferences?

[jtp10181]

It looks to be this device:

Z-Wave JS Config DB Browser

The HE compatibility list says to use the Fibaro Dimmer driver as you have selected.

To check on the way it is paired, check the Settings > Z-Wave details page, it will say None, S0, or S2. I think it is paired as None due to the data I see on the device page.

Can you please enable both logging options on the driver, clear the logs page, then run "Configure". Lets see what that looks like in the logs.

[johnwill1]

It shows as momentary for the switch but probably isn't when you use the Basic Z Wave tool and check the parameters. That's what I found anyway and why I configured them manually.

[vicksen]

@jtp10181

Settings > Z-Wave details page

This is the z-wave details page:

This is the log post configure:

[jtp10181]

Forgot you have a C5, so the details page is not as useful. I dont think the C5 can do S2, so it is likely joined with no security.

@bobbyD @bcopeland can someone comment on this error from the system driver? Looks like it is bombing out on configure and the device is not working because of this. Seems like maybe even the lifeline association is not even able to be set.

@vicksen you could also try the "Generic Z-Wave Smart Dimmer" or "Generic Z-Wave Plus Dimmer" and run configure on those. See if you can at least get the device working on a basic level.