The screenshot below was taken at 6:52 PM. You can see that the last event was at 6:40 PM, 12 minutes prior. I have a rule that waits for the wattage to reach 0 for one minute, but it was not triggered. Looking at the logs it just reports the same wattage time and values.
Any ideas why this seems to be hanging?
You did not share any Logs. I don't see any duplicate reports by either time or value in your Events, however, which you did share, as seems to be implied. There is no indication of any problem from this alone.
It would be helpful to share more information, including: what you're expecting to happen and why, what driver you are using, and the value of any preferences the driver may offer that relate to power reporting.
I'd also zoom out and look at whether your rule could be re-written. Does the difference between 3 W and 0 really matter? I recall you writing something about this in the past and me warning you about this possibility. It may be helpful if you found and re-read that discussion as well. If you want a "washing machine done" notification, a rule like the one I suggested in that topic is probably a better approach.
This issue has nothing to do with the washer notification rule functionality. It is now 8:00 PM and the events are still stuck at 6:40 PM. I did just turn on debug logging and you can see the electrical measurement failed error. I'll try running the washer again and see what happens...
UPDATE:
I ran the washer on spin for about 30 seconds, and events and logging resumed normally.
I had a VINDSTYRKA Air Quality Monitor about 6 inches from my C8 Pro, and it was between the Hubitat and the Washer. I wonder if this may have been causing a loss of signal? I moved it regardless. Also, I noticed other Zigbee power outlets don't report any log or event entries for long periods.
Unless you've programmed them to additionally report at certain intervals (I have no clue if that device offers such capability), then if they have nothing new/changed to report, they could go for quite a long while without piping up.
My power reporting plugs are all typically very quiet since they monitor stuff that may not get used daily, and I carefully prune their reporting paramaters.
So I include them in my daily wee-hours maintenance rule that (among other things) refreshes these and other typically quiet devices -- that way, my Device Activity Check at least gets that proof-of-life.
Understood, but you neglected to answer the first question (or any) here:
A device or driver isn't usually going to send or generate events when nothing is happening, so that first question is particuarly important.
This provides further evidence that nothing is actually wrong.
The configuration log isn't necessarily an error, as there is another cluster that might be used for this, depending on the device. There are several different models by this brand, and I don't know what does what, but the fact that reports are working at all suggests at least one worked.
Yes, I checked some of my other Zigbee outlets don't report any events or log entries for fairly long periods of time. In this case however I had a rule which was waiting for the wattage to reach 0 as usual, but it got hung at 3. I think I need to up my trigger to 3 watts.
-Thanks
It would be particularly helpful if you shared your rule and a description of what you want it to do so someone can advise if there is a different approach that might work better for your goal.
I have removed your duplicate post below mine. Everyone can see all replies, so there is no reason to post the same response multiple times. Please also consolidate multiple successive replies, if needed, into one post as has been asked of you previously, and use the quote feature if needed to make replies clear. Continued violation of this community guideline may result in flags, and multiple flags may result inaccount suspension. Thanks for your cooperation!
For my power-reporting rules, I use "power < X" conditional to drive my "off/done" action where X is a slightly padded power value that's still comfortably below the appliance's on/active power reading.
X needs to be equal or greater than the power-reporting threshold you have set for the device. For example, I use a 10W reporting threshold on one plug, so in that plug's rule, X=12.
ETA -- In that example case, the appliance's active active load is consistently ~25W, so when it ticks down below 12, it's most definitely off/done.
That is a good approach! And the name of the plug and the nature of the questions asked make it pretty hard to accept the claim that this is unrelated to the washing machine rule discussed previously. 
In that topic, I did link to a similar approach I made for mine. Here it is again if that is helpful:
Thanks, I used <= 3 (watts) which is working so far. 0 did not always work because sometimes the last event reported was 3 watts where it seemed to hang.
Download the Hubitat app
