Since the last update i am unable to toggle a fibaro dimmer off and on.
I'm using the built in fibaro dimmer driver.
If i set the level it works, but if i just try to switch it off and on all i get is the following in the logs and the light doesn't come on.
dev:1292020-01-09 13:54:04.319 errorgroovy.lang.MissingMethodException: No signature of method: fibaroSingleDimmer2.parse() is applicable for argument types: (hubitat.zwave.commands.switchmultilevelv3.SwitchMultilevelReport, java.util.LinkedHashMap) values: [SwitchMultilevelReport(value:80), [32:1, 38:3, 96:3, 152:1]] Possible solutions: parse(java.lang.String), wait(), run(), run(), any(), grep() (parse)
dev:1292020-01-09 13:54:18.681 errorgroovy.lang.MissingMethodException: No signature of method: fibaroSingleDimmer2.parse() is applicable for argument types: (hubitat.zwave.commands.basicv2.BasicReport, java.util.LinkedHashMap) values: [BasicReport(value:80, targetValue:0, duration:0), [32:1, 38:3, ...]] Possible solutions: parse(java.lang.String), wait(), run(), run(), any(), grep() (parse)
Have you updated your hub to the latest version?
yeah i'm running 184.108.40.206
I believe there’s a newer update now.
Updated and still not working, throwing the same errors in the logs.
Might have to drop it off and re-pair it, which is a pain as it's in the loft.
Are you using the built-in driver for that device?
yes built in driver,
Just realised it's now also not updating status on the dashboard or the device attributes, i'll drop it off the network on monday when the family aren't in and i can get in the loft.
Could be a mesh issue of course.
Have you new neighbors or have you added something that may have added to the local EMI ?
I'll try a repair and see if that does anything, if not i'll knock it off and set it up again.
I have the same symptoms with Fibaro on 2.1.7 and a downgrade to 2.1.6 solved the problem. Haven’t tested 2.1.8 yet so I don’t know if it is fixed.
Yeah i've tried 2.1.8 and still the same issues.
I tried a couple of z-wave repairs, every driver available and exclude and re-include. In the end dropping back to 2.1.6 resolved the issue.
Hopefully they manage to fix it in the next release.
It sounds like it’s time to tag in the big boys @mike.maxwell , @bobbyD so that they’re aware of the issue and any work in progress etc.