Getting the following message in the logs over and over. And I’ve even turned off all logging. I selected the Zooz double plug as the driver. Any clue what to make of this error?
As you can see it does it frequently and it's done it all night.
dev:72020-08-02 04:53:59.639 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:44, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 0, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:53:59.036 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:43, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 30, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:53:29.062 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:41, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 0, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:53:28.467 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:40, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 30, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:53:11.230 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:39, commandLength:14, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 68, 0, 0, 0, 1, 0, 0, 0, 0, 0, 1]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:53:10.687 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:38, commandLength:14, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 68, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:53:08.820 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:35, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[161, 74, 0, 0, 0, 0, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:53:08.237 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:34, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[161, 74, 0, 0, 0, 0, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:53:07.628 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:33, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[161, 34, 0, 0, 0, 0, 5, 9]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:53:07.040 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:32, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[161, 34, 0, 0, 0, 0, 5, 9]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:52:59.058 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:29, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 0, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:52:58.473 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:28, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 30, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:52:29.068 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:26, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 0, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:52:28.460 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:25, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 30, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:51:59.020 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:23, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 0, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:51:58.497 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:22, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 30, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:51:29.042 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:20, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 0, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:51:28.449 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:19, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 30, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:50:59.046 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:17, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 0, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:50:58.457 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:16, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 30, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:50:29.043 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:14, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 0, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
dev:72020-08-02 04:50:28.454 am errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:13, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 30, 0, 0]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
Also I see now that the two child devices that appear will not toggle the left and right plug at all but the main device will toggle both.
I have excluded the device and then added it back and I'm still getting the same errors.
Which platform version are you running?
C7 and 2.2.2.129. Replied again as I didn't reply directly to you the first time and wasn't sure if you'd see it otherwise. Sorry if you did already. 
I'm having the same issue, also ZEN25 on C7. I moved it from my old c5 which didn't have the issue.
2020-08-10 10:11:03.287 pm errorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:63, commandLength:14, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 68, 0, 0, 0, 6, 0, 0, 0, 0, 0, 6]), ...] Possible solutions: wait(), any(), trim(), dump(), collect(), grep()
this will be resolved in platform release 2.2.3
I just added one of these to my network this morning, and am seeing a similar error. I’m on a C7 on the latest firmware.
Just to follow up, the update to 2.2.3 did not help w/my Zooz plug...I tried to pair it today after completing a move of about 50-60 devices from ST to HE.
Zooz failed to pair, stuck at initializing and could not get it beyond that w/the normal tricks that have been discussed. It's boxed up to go back tomorrow.
I'm new to Hubitat, long time ST user preceded by Insteon and X10. Just received a C7, immediately upgraded using the two step procedure to also update the z-wave component.
Off Topic
Anyway, I've been wrestling this Hubitat and trying to unearth the numerous chicken waving routines outlined for it here in the forum for the last day. For now I just want to clean up my device list before I continue adding any more.
I have two opposing versions of ghost devices listed in my z-wave radio details table. One shows a status of "Failed" with the following clusters: in: , out:
Whereas my other ghost is nowhere to be found taking the form of a node listed as the middleman all but one of the 22 "Route" column (ex: A5 in 01 -> A5 -> 07) while not actually being listed anywhere in the "Node" column or as the final destination in the "Route" column.
On topic...
This evening I updated again to catch the minor C7 bump to 2.2.3.119. Due to prior issues with devices as I brought them on board I figured I'd just focus on the closest physical device which happens to be a ZEN25 "Double Plug" located about three feet from the Hubitat. After the update, I removed and successfully excluded the Zen25 from the hub. Then I put the hub into device discovery in order to rejoin it. After a couple failed attempts (why on earth is the inclusion mode countdown timer in the discover devices interface located so far away from the Found Devices tag?!) I remembered that the hub needed to be rebooted before just about every individual z-wave device pairing for the best chance of success. After a reboot, and my guess of whatever undefined extra time one of the gurus here suggested should be considered before actually using the device to discover devices lest something else go wrong, the Zen25 was discovered successfully and assumed the wrong (which is what my problem was before as well) driver code for the Zen20 power strip. Since I was unable to locate a means of changing the driver before being allowed to save the newly added device I changed the driver to the correct one afterward. However, all of the cruft from the Zen20 driver remains associated with the device after having switched to the Zen25 driver such as the five component channels the Zen20 does not have. I don't know what else it might be affecting but I don't much care for having five extra devices in my device list and every selection list when creating apps which don't actually exist.
@tivomaniac ... you're not alone. I have a brand new C-7 and was getting these errors with 2.2.3.118 and now with 2.2.3.119. But unlike you, I do not get the 2 child devices to control each plug. Just for comparison here is a few entries from my log
Summary
dev:662020-08-16 01:57:49.000 am errorgroovy.lang.MissingMethodException: No signature of method: zoozDoublePlug.parse() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:2, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 0, 0, 0]), ...] Possible solutions: parse(java.lang.String), wait(), run(), reset(), run(), grep() (parse)
dev:662020-08-16 01:57:48.398 am errorgroovy.lang.MissingMethodException: No signature of method: zoozDoublePlug.parse() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:1, commandLength:10, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 50, 0, 0, 0, 27, 0, 0]), ...] Possible solutions: parse(java.lang.String), wait(), run(), reset(), run(), grep() (parse)
dev:662020-08-16 01:57:24.996 am errorgroovy.lang.MissingMethodException: No signature of method: zoozDoublePlug.parse() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:63, commandLength:14, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 68, 0, 0, 0, 1, 0, 0, 0, 0, 0, 1]), ...] Possible solutions: parse(java.lang.String), wait(), run(), reset(), run(), grep() (parse)
dev:662020-08-16 01:57:24.408 am errorgroovy.lang.MissingMethodException: No signature of method: zoozDoublePlug.parse() is applicable for argument types: (hubitat.zwave.commands.supervisionv1.SupervisionGet, java.lang.Short) values: [SupervisionGet(statusUpdates:false, reserved:0, sessionID:62, commandLength:14, commandClassIdentifier:50, commandIdentifier:2, commandByte:[33, 68, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0]), ...]
I've exchanged a few emails with Zooz Support and they have asked me to remove and readd mine twice. The error in the log persist. Best I can tell from what I'm getting from support, it might have something to do with the C-7 and new Z-Wave security and might require a driver update.
@k5map I don't have that device connected at the moment but I do see where I have two drivers that I downloaded for this. Maybe you are missing the child driver? I just don't recall since I've been installing and configuring so many other things I lost track on that one.
@tivomaniac ... I found a Double Plug driver which was included in the C-7. Am I correct in I should use the driver you referenced instead of the built-in driver?
Thanks for the heads up. I installed both drivers, but don't understand how to assign both to a single device.
Also, you mentioned in the release thread
Hubitat doesn't allow you to delete or change the type of child devices so you'll have to remove the device and join it again.
With your drivers installed the inclusion recognizes and defaults to your Zooz Double Plug Advanced driver. Before I installed your driver I don't understand why it kept loading the power strip driver instead of the appropriate double plug one.
Am I the only one who seems to need to reboot the hub after any Z-wave inclusion/exclusion in order for it to operate as expected?
Giving your driver a run now, will let you know if it's an improvement although just having it clean up my device list was already worth it 
I couldn't get it to work right without that driver. And @arri they aren't my drivers I just was pointing you to them to try them.
Indeed, nor could I. It seems considerably better now than what I got "out of the box." Thanks to Kevin @krlaframboise for the driver!
One down, so many more random issues still to go.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
