Here are my comments and suggestions:
(1) I stopped using the HE built-in driver because, at some point about a year ago, the Refresh command stopped working with the Ring Extender V2 on one of the HE firmware updates . I raised the issue several times but it never got fixed. Search the forum and you will find my posts.
(2) I switched to Denny Page’s (@dennypage’s) driver for the Ring Extender V2 because Refresh works on his driver. His driver works perfectly, I have not had any issues. I do not know whether the Hubitat built-in driver for the Ring Extender V2 was ever fixed in recent months; I have not seen any indication of a fix in Release Notes.
(3) the reason Refresh was needed is that, when power fail occurs, I have a set of voting rules that looks at the power failures that occur on the six Ring Extender V2 devices I have and determines if it’s a “real” power fail or if one of the Ring Extenders just failed (hardware failure) or if someone (e.g., my wife) knocked the Ring Extender V2 out of the wall socket. The rules are a bit subtle and handle the “flapping” of the power up and down as the utility company tries to self-heal the grid during a power outage, and handle the up-down simultaneous events from the Ring Extenders V2 during power fail. If the power stays down for a few minutes (determined by the voting rules), which is shorter than the battery time of my UPS devices, then the voting rule shuts the Hub down with a clean shutdown. The real problem is on power restoration because the Ring Extender V2 devices power up before the Hub, so the Hub (and the Ring Extender V2 driver) misses the “return to mains” event from the Ring Extender V2, so the driver thinks the Ring Extender is still on battery. This could be handled by a Refresh in a systemStart triggered rule, but that requires Refresh to work in the Ring Extender V2 driver. I posted about this a while back, and Denny Page enhanced his driver so that it automatically schedules a Refresh when the Hub reboots and initializes the drivers, which means that the ,mains/battery state is always correct with his driver. From what you are describing, though, it does not sound like a refresh issue. However, it may be a driver issue, but maybe not.
(4) Denny Page’s driver is here, but it can also be found in Hubitat Package Manager:
(5) my Ring Extender V2 devices are on my C-7 production Hub, paired S2. I have never used them on my C5 development hub, which does not support S2. There has been extensive discussion in the forum whether the Ring Extender V2 works properly if not paired S2. The writer of the Hubitat built-in driver (Bryan Copeland) has reported that he couldn’t get it to work unless it was paired S2. Others have disputed that requirement. I don’t know the answer. It shouldn’t matter for a repeater whether it is paired S2, S0, or none, because the packets it repeats are just bits, and it just repeats the bits without decrypting and re-encrypting. But some repeaters might care about encryption for commands to the repeater itself and status reports back. I just don’t know, but I toss out that possibility.
(6) you say your Ring Extender V2 “paired fine”. I’m not sure what that means. You might try switching to Denny Page’s driver to see if that changes anything and seeing if the Extender responds to commands from his driver. Hit Configure after switching drivers.
(7) if you want to see my voting rules for the Ring Extender V2 devices, just ask. The complexity of voting is not needed if you only have one Ring Extender,
