I have a Shelly plug and set it up to trigger a function when power consumption is past a certain level. That all works, but the refresh rate of the Shelly device status is so pathetic (about 1 minute) that it HE C7 cannot detect any changes, unless they last for longer than one full minute.
Any idea if/how this can be fixed? (using the built in driver as none of the others seem to be maintained/working).
I can't claim any experience with Shelley devices, but I suspect it may be useful to confirm the exact model of plug you are using and potentially any more details about which driver you are using, though I suspect confirming the model will likely achieve the same.
The reason I say this is that for some (many?) Z-type devices the frequency or threshold for reporting power consumption is a fixed period / level determined by the manufacturer, rather than something that can be dictated by, in this case, the HE driver. This is of course not the same for all, and will need confirmation in your exact case, but just paving the way for this being a possibility and explaining why it is important to be clear about the model of the device and the driver being used. If you open the Device Details page for the plug in HE, do you see anything in the Preference Settings section where you can control the refresh / reporting frequency or level?
One or two other points I would add are that drivers / devices that see increases of X Watts as a reason to report means the frequency of "events" in the HE platform can be something you need to consider. Not that automations are impossible with these considerations (in most instances), just that you need think about it..... Or look to an alternative device for your use case.
Perhaps you could try using RM and set up a refresh for say every 15 - 20 seconds or so and see how that goes.
Well, I am using the built in Shelly device driver. The Shelly device is being detected and on/off works just fine. However, there is not "refresh every xx seconds" anywhere. The device has realtime information available and when manually clicking the "refresh" button on the device page in Hubitat, it updates the power usage immediately and correctly. So, it is not a problem with the device not providing the information, but an issue that the driver cannot pull the information on a predefined schedule.
The driver refreshes/polls after 1 minute. A lot of drivers do that.
What I meant was if you would like it to refresh more than that make a rule in RM to refresh your device say ever 15-20 seconds or so or what ever works for you.
Something like this.
Thanks - yes, I implemented that. Did not know you could do refreshes in the RM Working great now! Thanks for the hint!