The video download channel is the last bit on my list. Ive tried a few approaches and none have worked as expected. When they download, we log jam the event notifications which isn’t desirable.
Have you seen a difference by more than 1? I’m wondering if it’s just a rounding difference between the two. We get battery stats every update so they should be accurate.
The battery status is working a little bit strange for me at this moment. I figured out if you create a new item for the channel it stays NULL (I tested this behavior with a time of 24h and nothing changed). Only if I disable and activate the thing, the status shows up …
Before reactivate the thing
After…
I set now my Doorbell on the maximum power settings to see if the binding update the battery status if it will get less.
I’ll take a look at the battery updates next time I get into the code. I just noticed that the battery updates on my stickup cams are staying as NULL as well. Something may be jammed in the system during the updates. I made a bunch of changes there, always possible something jammed.
EDIT: Found problem, stupid problem. The readme has the thing type as “stickup” but it’s really “stickupcam”. That fixed that…
Stumbled across this and thought I would give it a try. Running openHAB 3.4.2 on a Pi 4B running openhabian. Install went smoothly.
Dropped the jar file into the addons folder. Added the Account thing, immediately received the 2FA code, entered it, Account thing came online, device things appeared in the inbox.
I will be watching the events to see what useful information I can get from it.
Thanks for the work
Awesome! Im hoping to have some more time soon to dig into the video downloads. I know what has to be done, I just can’t figure out a clean way of doing it that isn’t going to cause leaky threads.
I pushed a new version (a78a12b). I’ve done some minimal testing and it looks cleaner. There are a few changes here.
2023-05-08 15:25:29.236 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'RingEventCreated' updated to 2023-05-08T15:25:08.000-0500
2023-05-08 15:25:29.236 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'RingEventKind' updated to motion
2023-05-08 15:25:29.237 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'RingEventDeviceID' updated to REMOVED
2023-05-08 15:25:29.237 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'RingEventDeviceDescription' updated to Back Yard
2023-05-08 15:25:45.221 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'RingEventVideoURL' updated to http://OH-IPADDRESS:8080/ring/video/BackYard-motion-2023-05-08T15-25-08.mp4
Notice the event happened at 15:25:08, the file is still named 15-25-08, it was reported at 15:25:29 when the periodic update happened, but it actually finished downloading at 15:25:45. I’ve only had a limited time to test this, please let me know if this works better. Also to note, we’re back to the URLs we had before that pointed to the OH server instead of the ring api.
2023-05-08 15:36:44.662 [DEBUG] [ing.ring.handler.AbstractRingHandler] - DoorbellHandler - minuteTick - device REMOVED
2023-05-08 15:36:44.662 [DEBUG] [ing.ring.handler.AbstractRingHandler] - Battery Level Unchanged for REMOVED - 98 vs 98
2023-05-08 15:36:44.663 [DEBUG] [ing.ring.handler.AbstractRingHandler] - StickupcamHandler - minuteTick - device REMOVED
2023-05-08 15:36:44.663 [DEBUG] [ing.ring.handler.AbstractRingHandler] - Battery Level Unchanged for REMOVED - 91 vs 91
2023-05-08 15:36:44.665 [DEBUG] [ing.ring.handler.AbstractRingHandler] - StickupcamHandler - minuteTick - device REMOVED
2023-05-08 15:36:44.665 [DEBUG] [ing.ring.handler.AbstractRingHandler] - Battery Level Unchanged for REMOVED - 48 vs 48
2023-05-08 15:36:45.089 [DEBUG] [ing.ring.handler.AbstractRingHandler] - DoorbellHandler - minuteTick - device REMOVED
2023-05-08 15:36:45.089 [DEBUG] [ing.ring.handler.AbstractRingHandler] - Battery Level Unchanged for REMOVED - 0 vs 0
This should at least indicate that we are in fact checking the level versus what we know about the device. If this never goes down I’ll have to go one step back to figure out why we aren’t getting updated information about the devices.
Thank you!
I just tested it with motion and ring with 45 minutes between them.
It looks like it’s grabbing the previous last event as the current event.
HoffmanEstates-motion-2023-05-08T15-33-35.mp4 ← got this URL for the DING one below
HoffmanEstates-ding-2023-05-08T16-12-58.mp4
Lets give it some more time to see if I’m wrong about this.
Best, Jay
Was that right when the binding was updated? It gets a historical list on connect and goes through it until it gets to the end.
It actually was . . . good call!
Best, Jay
Yeah binding start has the potential to pull the last event (or set of) as if it happened. I’ll see if I can put something in to ignore those in the future.
hello, is support for ring intercom planed?
I wasn’t aware they even made that. What would the use case be?
For those tracking the battery issue, it looks like it’s unresolved with the last patch. I’m digging through the code now to see why. From what I can tell we are getting the correct json from ring, we just aren’t updating the devices database. Looking to figure that out now.
I pushed an update (127eaa7) that hopefully should resolve the battery issue. From what I can gather, this did not work on the original binding either. I hope that the additional patch should update the data and in turn fix the issue. Please report success/failure. Thanks!
there would be some of usecases.
most important
others:
Can you explain a little more? We don’t have this over in the US and the translation I get on google isn’t great. From what it looks, this box is an interface to the doorbells (e.g. someone rings the doorbell you walk up to it and talk through it). How does this open the door? Does it have it’s own events or is it tied to the events from the doorbell?
Good news! The battery issue looks fixed. There are several instances on there of the battery going down.
The odd news, all of those spikes to 0. Not sure what’s causing that yet. I’ll attempt to get into the code this weekend or early next week to see what’s happening.
Yup, I can confirm that with an email alert about it. Lol
Sent: Wednesday, May 10, 2023 2:11 PM
To: Jay gMail
Subject: openHAB3 - Low Battery Alert!
Battery Levels:
FLRingDoorbellBattery: 0%
** End of Report **
maybe this helps a little bit to understand the system:
the door can be opened with the ring app (ring app → ring intercom → doorbell system/data wire) or with amazon alexa (activated alexa ring skill → ring intercom → doorbell system/data wire)
the connected data wire on the doorbell triggering the ring intercom. ring intercom now activated the ring app/push notification with dialog.
you can now open the door and/or talk to the other person with the ring app or withe the doorbell system.
the ring intercom has no mic/speaker or anything. it only interact with the data line of the doorbell system.
Ah! I see what I was missing. This is for an apartment complex or something similar where someone has to be buzzed up from the front door. I was thinking this was something completely different.
So short answer is yes we can probably add it. As I don’t have one I’ll need some help gathering data. Can you please send me a DM with the JSON messages from the binding? You’ll need to turn trace logging on. I’m specifically looking for the really big one from the account that dumps all of the devices (please sanitize your personal info out) and then the event of someone pushing the doorbell.
