Errors in System in built system driver for Aeotec Dual Nano Switch

I just realized that I am getting these errors in the System driver for the aeotec dual nano driver..
further, the child devices dont update the on/off status when toggled.. I have to refresh them, and then they show the state.

dev:272025-06-19 08:10:09.619

error

groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (java.lang.Short, java.lang.Short) values: [255, 2]

dev:272025-06-19 08:10:08.173

error

groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (java.lang.Short, java.lang.Short) values: [0, 2]

dev:272025-06-19 08:10:04.436

error

groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (java.lang.Short, java.lang.Short) values: [255, 2]

dev:272025-06-19 08:10:02.652

error

groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (java.lang.Short, java.lang.Short) values: [0, 2]

dev:272025-06-19 07:16:49.448

error

groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (java.lang.Short, java.lang.Short) values: [255, 2]

dev:272025-06-19 07:14:30.085

error

groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.meterv5.MeterReport, java.lang.Short) values: [MeterReport(scale: 5, rateType: 1, scale2: 0, deltaTime: 0, previousMeterValue: , meterType: 1, precision: 3, size: 1, meterValue: [103]), ...]

dev:272025-06-19 07:14:30.033

error

groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.meterv5.MeterReport, java.lang.Short) values: [MeterReport(scale: 4, rateType: 1, scale2: 0, deltaTime: 0, previousMeterValue: , meterType: 1, precision: 1, size: 2, meterValue: [4, 214]), ...]

dev:272025-06-19 07:14:29.968

error

groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.meterv5.MeterReport, java.lang.Short) values: [MeterReport(scale: 2, rateType: 1, scale2: 0, deltaTime: 0, previousMeterValue: , meterType: 1, precision: 3, size: 2, meterValue: [34, 193]), ...]

What hub hardware model and platform version are you running? And did you switch to Z-Wave JS or are you running default/"legacy" Z-Wave?

Platform Version : 2.4.1.177
Hardware Version: C8 Pro
Zwave JS (Non Legacy Z-Wave)

Also, found out another device also having errors .. it is a vision dual microswitch)

dev:662025-06-19 08:15:36.377

debug

Parsing desc => β€˜{"cc":114,"cmd":5,"ep":0,"values":[{"request":{"args":,"command":"endpoint.invoke_cc_api","commandClass":114,"endpoint":0,"messageId":"expected43291","methodName":"get","nodeId":40},"response":{"manufacturerId":265,"productId":5911,"productType":8215}}]}’

dev:662025-06-19 08:15:29.083

error

java.lang.NullPointerException: Cannot invoke method format() on null object on line 129 (method off1)

dev:662025-06-19 08:15:28.144

error

org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_hubitat_Enerwave_Dual_Load_ZWN_RSM2__Vision_microswitch__679.off() is applicable for argument types: () values:

dev:662025-06-19 08:15:27.060

error

java.lang.NullPointerException: Cannot invoke method format() on null object on line 147 (method off2)

dev:662025-06-19 08:15:25.379

error

java.lang.NullPointerException: Cannot invoke method format() on null object on line 138 (method on2)

dev:662025-06-19 08:15:21.017

error

java.lang.NullPointerException: Cannot invoke method format() on null object on line 120 (method on1)

dev:662025-06-18 05:39:19.621

error

java.lang.NullPointerException: Cannot invoke method format() on null object on line 147 (method off2)

There are some fixes for Meter Reports in 2.4.2, currently in beta, though I don't know if it will fix your exact issue. You can join now if you want or wait for release -- no timeline, as usual.

The other issue appears to involve a user driver. Maybe there's just not an off() command in the code for some reason?

Sure, how do I sign up for the beta version?

.. in the meanwhile.. I installed the custom driver from here by dmitry.rozovik

and everything is working, without any errors, and it also enabled the energy monitoring.. that is missing from the inbuilt driver.

You can join the beta with these steps:

However, I'd guess it's likely to be released fairly soon if you aren't otherwise interested in testing, so just waiting a bit more should work, too. :slight_smile:

For now, however, you might also want to keep the custom driver. It doesn't look like the built-in one parses power events, though the command class appears to be there for all the fingerprints the driver was written to support, so if the device doesn't do anything weird, it should be fairly easy to add (just probably not in 2.4.2).