That's good to know - I was looking at it more from the repeater end of things but power status seems like a great feature too. Cool!
Looking at @bcopeland old driver (and assuming the in-box one is the same) in theory hitting configure should refresh the power source info after 5s (but refresh or anything else does not - I think refresh should too, but that's me).
Haven't had a chance to test that though.
I never got it consistent on C5. It is one of those ring devices that doesn’t like to be included non-S2
1 Like
Regarding the wrong Powered state," Battery" on a hub reboot after a shutdown, it now makes sense to me. The last power state prior to shutdown is battery so that is what displays on Hub reboot. When the Ring device's power is restored prior to HE reboot, for all we know the device may send a Power Management message, however, there is nothing listening, so when HE restarts it remains at Battery.
My Zwave Command skill set is about -1, or I would attempt to code these changes that will hopefully fix this issue
-
Request and Update the Power Managemant state when on a Refresh command
-
subscribe to Hub's system boot event, then issue an (updated) Refresh command. My gut says subscribe does not work in a driver, in that case users could easily do a device Refresh with an RM or Groovy at hub reboot.
-
I suspect there may be other ways to accomplish this.
The fix for "Notifiction: null" ~line 35 change from Map to a List, remove the leading numbers.
@Field static List ZWAVE_NOTIFICATION_TYPES=[
"Reserverd",
"Smoke",
"CO",
"CO2",
"Heat",
"Water",
"Access Control",
"Home Security",
"Power Management",
"System",
"Emergency",
"Clock",
"First"
]
Great.. fix it.. It is fixed in the driver I wrote for the built-in .. Consider most of my community drivers to be abandoned .. If someone want's to fork and maintain them, it would make me happy.
2 Likes
As I said my Zwave skills are -1, or I would have attempted to fix it.
Kindly accept my apologies for upsetting your feelings. I did not know you were no longer maintaining your community drivers, so consider my request withdrawn.
Switched back to the System driver, device continues correctly reporting the Power State.
Does the system driver Refresh command on the system driver update the Power state, or does the state update at HE system reboot?
You didn’t .. I genuinely hope someone takes over my community drivers.. As I don’t have the time I had to maintain them.
1 Like
FWIW
-
Using the system driver I retested the power off, graceful HE shutdown, power up ring extender, then reboot hub scenario
-
Extender device displays "battery" at reboot until it is power cycled.
-
Issuing Configure or Refresh commands did not change the status.
I had a VERY difficult time pairing these- tried so many times I can't remember what worked. On the C5 hub when I paired, I don't think any security choices popped up. Whatever the default was worked I think. On the C7 it was kinda a nightmare trying over and over. If you figure out what worked for you PLEASE post it or message me so I can use it as a reference in the future.
How to set powerSouce setting when system reboots using a User driver including @bcopeland's
Tested with a Gen2 using a C4 Hub, YMMV
in metadata add
capability "Initialize"
Before refresh method (or wherever you prefer) insert:
void initialize() {
/* current state return a requested power management response. failing command issues a x'00' */
def cmds = []
cmds << zwave.notificationV3.notificationGet(notificationType: 8, v1AlarmType: 0, event: 0x03) //on mains?
cmds << zwave.notificationV3.notificationGet(notificationType: 8, v1AlarmType: 0, event: 0x02) //on battery?
sendToDevice(cmds)
}
Update :
should you be using a driver other than bcopeland's, change:
sendToDevice(cmds)
to
sendHubCommand(new hubitat.device.HubMultiAction(commands(cmds), hubitat.device.Protocol.ZWAVE))
4 Likes
I installed one of these a while back and set up the rules and forgot about it. I set myself a reminder to test a power failure once. Well I just had a power failure and decided this time to see whether it did anything. Actually it hasn't shown anything in the events at all, ever. I also noticed I plugged it into a UPS supplied outlet which was brilliant. Luckily I was not depending on it.
Anyway, I am beginning to think my unit is a dud. I can't find any real documentation on it. When plugged in should the switch glow? Mine does not. I have tried all manner of button pushing, repeated pushing, holding button in, but don't seem to get anything out of it. And occasionally I get a red flash from the button when trying all of my button stabbings.
Presumably a reset and re-add is the best way to go but I can't figure out how to even reset it let alone add it. Thanks for any help.
No. I have 6 of these scattered around, and they work perfectly. Way to test, if you have it paired to your hub, is simply to unplug it, look at the powersource state (mains, battery) in Current States on the device’s page.
It’s easy to write a rule that triggers on this state.
I suggest using Denny Page’s (@dennypage) excellent driver.
2 Likes
Thanks. I am using this driver. I had set it up sometime ago but as noted have just looked at it and found no events or logs. No updates coming through when I unplug it.
I decided to try and exclude it, reset it, whatever. I can't find any documentation on how to put it into add/delete mode, or reset it?
How to do you put it in pairing mode? How do you factory reset it? Thanks.
Here is the manual. I would not suggest doing a factory reset unless you have first excluded it from your hub. Otherwise, you could end up with a ghost.
1 Like
Thanks - I had previously only found versions of the manual that did not include the add/delete etc.
I was able to exclude it. And I factory reset it successfully. I am able to get it into add mode - three green flashes. But so far have not been able to add it. I have it next to the hub so I will keep trying.
It took me several tries of include/exclude.
Others here in the forum have had success using SmartStart. I haven’t used SmartStart.
1 Like
It took several attempts to remove ghost nodes that were created while attempting to add the Ring Extenders. Then it took several attempts to add them back. I was finally able to do so, and they(X2) seem to be functioning properly now.
Thanks. I did get it eventually. I had to factory reset and then immediately hold for three seconds. And instead of flashing three times it was flashing continuously when it finally did pair. Not sure if I read the docs wrong.
Also I paired without security which I assume doesn’t matter?
I have no idea why it stopped working in the first place but I am back up and running. Thanks everyone.
It really doesn't matter, mine are paired S2. Security pairing has no effect on what packets are repeated by the device, all are repeated regardless.
The only reason I paired mine S2 was because of this comment from Bryan Copeland, upthread:
