I have five (5) EveMotion Matter shades in my home, all connected to Hubitat via my Alexa Hub acting as the TBR. They've been working essentially perfectly, with the exception of an occasional disconnect of one of the shades (see this thread). But that happens rarely and seems to remedy itself within minutes.
Today, as I was doing some random tinkering in Hubitat, I noticed my shade battery levels were a bit low and, as I started charging them, I was also opening up the device pages periodically to check battery levels. That's when it caught my eye that one of my shades, and only one, had an odd looking list of State Variables (well, at least odd to me). I then looked at the logs, and noticed a repeating error...
error
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: smartwingsMatterShade.deviceHealthCheck() is applicable for argument types: () values: (method deviceHealthCheck)
Interestingly, this error is NOT showing on the shade that occasionally loses its connection as mentioned above. It's showing on one of the other four shades that has never had any issues. And I can't attribute the error to any pattern - it just seems to happen whenever the device is checking itself, like for battery level or position, but even then, not consistently. Sometimes it will repeat a several times, and sometimes it shows a cluster of the error, like 20-30 occurrences.
I've double checked all settings for all five shades to determine if there was something unique about this shade throwing the error, and I can't find any difference. They are all running the same driver (SmartWings Matter Shade) and every other device setting is the same. As for the odd, huge list of State Variables, here's a screen capture of what I see for the shade throwing the error...
Again, this shade, the one throwing the error, is the only shade that displays a list of State Variables like this. All other shades simply show the following for State Variables...
I am wondering if any Matter over Thread gurus out there might have an idea of what's going on that makes this one shade unique. If the only oddity was the State Variables list, I wouldn't pay much attention to it. But I am concerned about the error showing in the log, especially since I have no clue what it's indicating. And again, the shade itself has always worked perfectly.
Oh, I should add, I confirmed that all five shades are running the same hardware & software versions... 1.1 and 3.2.1 respectively.
Any and all ideas/theories appreciated. Can anyone decipher the error for me?
