Not sure I can find the link for the original version.
I have reinstalled this version
Drivers now showing
Here is the link (just in case) ge4d / hubitat-code / Bundles / Bundle1.zip — Bitbucket
[downloading and installing bundle again just updates it; you will not get one more bundle but anupdate of all included content; no need to reinstall devices - they will get automatically updated]
I have a couple of the Shelly 1 Mini Gen 3 relays, firmware version 20250318-152134/1.5.1-g01dd7ff. Every 2 minutes I get the following message in the log:
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_drozovyk_Shelly_Plus_Pro_xPM_721.checkState() is applicable for argument types: () values: (method checkState)
It is marked as an error. Any idea what could be causing this? The devices seem to be working OK, though each of them is showing 22-23% "% of busy" on the Device Stats log page, the most of any of my devices.
I am using the Shelly Webhook/Websocket Driver v2.4.3 (it shows up as "Shelly Plus/Pro xPM" for the Type on the device info page).
Did you switch drivers? That error means a function in the code is missing. I looked at @dmitry.rozovik’s code and there is no checkState function. Curious how that reoccurring scheduled job got created unless you changed drivers.
What you can do is go to Logs / Scheduled Jobs and look for checkState in the method column for your device and then click the garbage can at the very right to remove this recurring 2 minute job.
The mention of webhooks and version is a bit confusing: "Shelly Plus/Pro xPM" is not using either of them.
From the behavior you described I suspect two passible reasons:
- There were some other driver scheduling this function internally before. And then driver were changed while scheduled job were active, So now it tries to call nonexistent function. (Probably external calling like RM also could fit here)
- Some weird mess. 2 minutes interval looks pretty much like device initiated status updates trough websocket. And for some reason every time the report gets in a try to call that 'checkState' happens.
Edit:
"version": "2.4.3" relates to a different driver by Daniel Winks distributed by Package Manager. ("packageName": "Shelly Webhook/Websocket Drivers",)
So you have mentioned one driver that shows as another driver. And your log is showing you have my driver set while trying to call a function it does not have (and I can't find it in Daniel's driver either).
It could be you tried different drivers on the same device at some point. And now you might have old attributes remainind in the data fields. And some scheduled function from some previous driver.
Thanks! Yes, I did switch from the Shelly drivers to @dmitry.rozovik's, which work much better. I also had someone else's driver installed while I was trying to get the Shelly relay to work. I trashed the Scheduled Job you said would be there and it stopped the error from being reported. Thanks again!
1 Like
Yes, I was sloppy in reporting my setup, my apologies. When I was reporting my setup I wanted to have the driver version number included and I just went into HPM and found a driver with a bunch of Shelly stuff and assumed it was yours. Again, that was very sloppy of me, sorry about that.
I have deleted all the other Shelly drivers and apps. I no longer have the error (thanks @ritchierich) and the Shelly devices are no longer using a lot of CPU.
Thanks for creating this driver and for your help!
There is no need in deleting other drivers. It was the device instance polluted with extra data and tasks. Cleaning device instance should be sufficient to fix such incident.
I wasn't using the other drivers, I only need yours, so it was more housekeeping than necessity.
Just curious, why isn't your driver in HPM?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
