Problem with Refresh Custom Action

My apology, thanks for moving to a new topic.

Not sure what you want here, but here in successive screenshots is the full device page for one of the 6 devices. All are similar.

These happen to be using Denny Page’s (@dennypage’s) driver found here:

I had been using the built-in driver, but refresh hasn’t worked on that driver for over a year. I turned in a couple of identical PM bug reports to Bryan Copeland (@bcopeland ) (an initial one and then a follow-up inquiry many months later), who said he would take a look at it but apparently never did. I realize that he and all of you have been very busy on more important things, so I switched to Denny Page’s driver because the refresh capability works in Denny Page’s driver. I don’t need or use any of the additional features in Denny Page’s driver, but I do need the refresh capability in order to restore the mains/battery power source status of the Ring Extender after a power fail comeback because the hub, being shut down, misses the ā€œreturn to mainsā€ event of the Ring Extenders.

metadata
{
    definition (
        name: "Ring Alarm Range Extender gen2", namespace: "cococafe", author: "Denny Page"
    )
    {
        capability "Configuration"
        capability "Refresh"
        capability "Battery"
        capability "PowerSource"

If you will re-read my problem statement, I indicated that not only would the action become broken if any attempt was made to edit it, but also that no new action with refresh could be created, even in a new rule with an attempt to create such an action.

I can’t explain why it seems to work for you. I will try switching the devices to the built-in driver, see if I can create a refresh action with that driver.