Down to three of 4 leds on the TalentCell.
1 Like
Well, it's been 36 hours on the TalentCell battery so far, with 15 of them on hub alone and the rest including the ZSE29 motion sensor.
Still at 3 of 4 leds, and the ZSE29 is still showing 100% battery.
After a hub on battery power such as this shuts down gracefully, how do you bring it back unattended?
First, with a shutdown command, in the interest of preserving the db integrity, the red light (and z-wave radio, at the least) is still on, so it's not totally off. You'd have to figure out a way to shut off battery power to the hub totally, if you wanted to restart it remotely. Some type of local, non-cloud timer, independent of the hub, since that will be shut down.
Unless maybe the battery died totally with the light on? Would any harm be caused to the hub in this shutdown mode by the battery dying a slow death?
Maybe the USB-C being designed will take care of this. I haven't looked. Perhaps a real UPS? Maybe. But the TalentCell battery I'm using is doing really well, so far. Under normal operation, I'll probably be using generators that'll keep it charged up anyway.
Interesting to think about. It's only during a real power outage that you can tell if things work, or don't.
Even apart from db corruption, I think, subjectively, things resume better after an outage if hub power isn't interrupted. I could be wrong though.
If the hub is shutdown and then loses power there should be no risk of database corruption as the hub will not be processing anything at that point.
I know that, but the red light on the hub is still on, meaning, at a minimum, z-wave radio is still on. Would a slowly dying battery potentially cause any damage? The hub can't be restarted unless power is completely cut off and restored.
Already have the Powerwall, came with the Solar system. Just looking to maximize reserve time if the power goes out. We don't get a lot of outages here, but usually 2-3 that will last several hours. and typically 1 year that last more than 10 hours. Before you ask, North Texas, the far NW side of the DFW Metroplex.
Radio is still powered but isn’t doing anything but sitting there, so a dying battery isn’t going to hurt anything
1 Like
I use kasa /tplink switches to reboot it after a power outage. Simply toggle it off and back on and the hub will boot up even after it was cleanly shutdown. I tested a bunch of wifi plugs and many did not remember the last state. The kasa does and when power is restored reboots to last state. In addition you can set a schedule to either turn off ( to weekly reboot something for instance), or turn on in case someone turns it off or the reboot fails for some reason. The schedules are local and run even if the switch drops off wifi.
1 Like
I'm not sure how I would set that up. How can the Kasa 120v. plug be incorporated when the hub is powered from the battery? Maybe you are talking about a commercial UPS? Plus, I didn't know the Kasa plugs could keep a schedule even without local wifi-that's pretty cool.
ya sorry probably cant if the talent outputs usb directly and not 120.. not sure what you can do.. kind of defeats the purpose.. as i said i use apc ups and they output 120 and then i plug the kasa into that and then the hubitat adapter into the kasa..
maybe something like this with the correct usb a/b to usb c adapter
obviously you want a wifi one, as having a zigbee or zwave on the hub doesnt help lol.
1 Like
The type a usb plug might not provide enough juice for the type c powered hub.
says 2.5a but 1.0 a for charging.. there is no way the hub uses more than that..
looked it up, hubitat adapters are 1.0a so you should be fine
1 Like
Hi, where can I get the link to install the app?
Available through HPM or at https://raw.githubusercontent.com/thebearmay/hubitat/main/apps/powOutMgr.groovy
1 Like
Thank you for your work on this. I added the app from github and configured it but it doesn't seem to work. when it detects the Ring Extender toggling from main to battery. It errors with this
2023-03-05 01:08:14.401 PMerrorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 295 (method startOutage)
and then when the the timer expires and its suppose to run the rule after the power is back up I see the following error
023-03-05 01:10:19.481 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_app_thebearmay_Power_Outage_Manager_522.restorerunRM() is applicable for argument types: () values: Possible solutions: restoreRunRM() (restorerunRM).
I don't think it will matter but this is running on a C8. Here is the full log with the debug slider on
app:5762023-03-05 01:10:19.481 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_app_thebearmay_Power_Outage_Manager_522.restorerunRM() is applicable for argument types: () values: Possible solutions: restoreRunRM() (restorerunRM)
app:5762023-03-05 01:08:19.323 PMdebug[dev447:true]
[:]
app:5762023-03-05 01:08:19.316 PMdebugTime: 1678043299288 Device: 447:Ring Power Outage Detection Value: mains
dev:4472023-03-05 01:08:19.288 PMinfoRing Power Outage Detection AC mains re-connected
dev:4472023-03-05 01:08:19.286 PMdebugNotification - Type: Power Management, Event: 3, EventParameters:
dev:4472023-03-05 01:08:19.284 PMdebugSupervision Get - SessionID: 6, CC: 113, Command: 5
dev:4472023-03-05 01:08:19.281 PMdebugparse:zw device: 19, command: 6C01, payload: 06 09 71 05 00 00 00 FF 08 03 00 , isMulticast: false
app:5762023-03-05 01:08:14.401 PMerrorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 295 (method startOutage)
app:5762023-03-05 01:08:14.245 PMdebug[:]
[dev447:true]
app:5762023-03-05 01:08:14.239 PMdebugTime: 1678043294191 Device: 447:Ring Power Outage Detection Value: battery
dev:4472023-03-05 01:08:14.191 PMinfoRing Power Outage Detection AC mains disconnected
dev:4472023-03-05 01:08:14.186 PMdebugNotification - Type: Power Management, Event: 2, EventParameters:
dev:4472023-03-05 01:08:14.148 PMdebugSupervision Get - SessionID: 5, CC: 113, Command: 5
dev:4472023-03-05 01:08:14.129 PMdebugparse:zw device: 19, command: 6C01, payload: 05 09 71 05 00 00 00 FF 08 02 00 , isMulticast: false
First error is due to value not being initialized, second is a typo. Both are fixed in v0.2.1
Thanks.
2 Likes
That fixed it thanks again for your work,
1 Like
@thebearmay -- thank you for this awesome app!
Question please... How are these two "delays" related -- On the main page, I think this first one ("AA") is an overall delay before doing anything, but then on the "Power Outage Actions" page, how do those 3 delay options (e.g. "BB") relate to AA?
Does the BB delay time start after AA expires? Or do they both start running at the same time? Thank you again!!
BB isn't activated until AA expires
1 Like
Right on - thanks! Our power here is typically very stable, but unknown to me until I woke up, we had a brief outage ~2am during an ice storm, so I'm just trying to piece together what happened when.
I'll make an according tweak to my setup -- it seems I had BB running simultaneously, so this info is super helpful getting me squared away. Thanks again!
1 Like
I have no battery enabled devices so this won't work for me but Kudos for developing Hub Ping and Hub Info!
This was a great workaround. I ping my server and when the APC UPS says shutdown my WC piston goes into action shutting down the hub via Hub Info. When the power returns another System Start piston cleans up the ZB lights that fail ON and Refresh(es) all the devices.
1 Like
