My Ikea blinds have been working fine for years with the built in Ikea Window Blinds driver. With one of the last updates they seem to not be working at all anymore. This is the error in the log:
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_a4refillpad_IKEA_Window_Blinds_1050.ping() is applicable for argument types: () values: []
Possible solutions: find(), print(java.lang.Object), print(java.io.PrintWriter), find(groovy.lang.Closure), print(java.lang.Object), run() (method ping)
That would not have come from a built-in driver. You must have been using a custom driver at some point that created a scheduled job, then switched to the built-in driver.
This isn't really a problem, at least not one that would prevent the device from working. If that's happening, there is another problem. But to get rid of it, you can go to Logs > Scheduled Jobs, find one listed for this device under "App/Driver Name" with "ping" as the "Method Name," then use the delete (trash can) icon under "Actions" to get remove it.
That's good, but note that a reboot won't help with the specific error in your logs -- you'll have to follow the steps above to get rid of that. But, as I mentioned, if the device wasn't actually working (not clear from either of your posts), that is/was an unrelated problem.
If you ran the command from the device detail page and got that error -- not sure what you mean but taking a guess in the absence of any other information -- there is still a problem with the driver (albeit an unusual one, and not one that should affect anything else per se unless there are similar problems elsewhere).
OK, that isn't from a built-in driver, so you must be using a custom driver for this. Ignoring the command is probably easiest, unless there is a scheduled job the driver created that uses it; otherwise, asking the author to address the underlying issue (or doing so yourself -- or asking someone here if you aren't sure, but without a link to the actual code, there isn't much that can be done) would probably be best. Good luck!
I didn't catch this before, but there isn't a built-in driver by this name (though one of the Generic Zigbee drivers would probably work for this kind of device) -- adding to the clues that you're using a custom driver, which is also where the error in your first post would have come from looking at it a bit more closely.
