Is there anything wrong with your 0.1 app right now?
I ask as upgrade can be finicky and without any data I would suggest you assume upgrading will require you to re-install or re-discover your devices. Hopefully that isn't the case, but I would assume that before you make the plunge so that you prepare, and are surprised if less breaks then you thought.
I'm still on an older version (one version back) that doesn't have the camera thumbnails, as I really don't need to upgrade until I add more/new Ring devices, as I'm assuming I'll need to re-install or re-discover devices... that;s just me being both cautious and lazy.
And as other have suggested, make sure you do a backup so you can revert back if needed.
Out of curiosity why are the snapshots only available on the local network?
The snapshots provided by this app will only work when accessing them locally. The image thumbnails cannot be made available via the cloud for several reasons which will not be discussed here. If you try to access the dashboards with these images they will only display locally (when on the same network as the hub).
From what I can see, the snapshots are saved directly on the Hubitat Hub, and shared via their local web address. If you have a VPN, you can see them remotely. (I have done this.)
Hi,
When arming through the Ring app and you have any open doors/windows, it shows the open sensors and asks if you want to bypass and arm anyway. Is there a way to bypass when arming through this integration? I didn’t see any questions related to this yet in the thread. Thanks
What I have seen is the same. There doesn't appear to be an option with this integration to arm with bypassing a sensor.
What I have done is to write a RM rule that will wait until all the doors are closed to arm at that point. Probably not what you are looking for, but it works in cases where you just need to arm when you have left and closed the door.
Is anyone having issues with Locking and Unlocking door locks through Ring after updating to 2.2.4?
I have a hub with 2.2.3 and it works perfectly. However, on my hubs with 2.2.4.141 (same on 2.2.4.139) when I either try to Lock or Unlock my locks through Ring, I temporarily lose access to my base station on the app, and on the web site, I see the following occur:
Just to make sure I understand, you have the locks directly paired to Ring, and you are using this Ring integration to expose the locks so HE can also see them, and completely independent of HE, when you lock/unlock via the Ring app it doesn't work? Or is the issue trying to lock/unlock from HE on 2.2.3.x vs 2.2.4.x?
Or are you using HE in any of those scenarios?
Either way, Ring's own backend and website contacting it's own hub shouldn't be affected at all by HE and this integration.
That is the correct scenario. When I try to lock/unlock from HE on 2.2.4.X, it does something that seems to crash something in Ring. It is then unavailable to the web site or to the app until it comes back on-line several seconds later. I also get a notification e-mail from Ring that my alarm is off-line. It's like it does something to its ability to connect to the wifi or internet.
That's super weird. Good news is it seems like you isolated the issues to a change between 2.2.3.x and 2.2.4x, but who knows what that could be. Do you see anything different in your logs when you turn on debug? (I'm not a developer, so just asking questions to see if we can tweak something, I also have my two Schlage locks paired directly to HE instead of Ring. With Ring I have only paired directly a few contact sensors, 2 montion detectors and two smoke/CO detectors)
I might need to pair my locks to HE if I can’t find another solution... (but then I lose the ability to lock through Ring...) either that or setup a second hub with only Ring Connect on it, leaving it with 2.2.3 and using HubConnect to share the lock... both non ideal scenarios...
Thanks for asking about the logs! Initially, nothing came up, but I gave up too quickly... after a few seconds, I get this:
It looks like there were a few z-wave lock updates in 2.2.4 and a change in a few of the lock drivers. @bcopeland - Any idea what could have changed between 2.2.3 and 2.2.4 here?
@Sebastien - If you still have 2.2.3 running, one thing you could look at in the logs to compare 2.2.4 and 2.2.3 is if anything changes in the info sent from line 65 here (e.g. the values in zid, dst or data) which routes through the simpleRequest in line 4150 here .
(On a total side note, it's super concerning from Ring that potentially a malformed lock command push could knock the Ring Alarm of off it's connectivity)
My sweet wild-■■■ guess is perhaps there was a change in 2.2.4 that changed some of the properties and/or paramaters passed through slightly changed. As this app is constructing the webhook call to the Ring Alarm base the same way, so I'm imagining something in the actual content/data must have changed.
Interesting, could you turn tracing on?
From the simpleRequest method on line 1450, there is both logging for the simpleRequest call and a tracedebug for the data. I'm really suprised you aren't getting that as the lock and unlock commands in the Ring Lock driver call that method.
I'd love to do this, but I'm not sure how to do it... Been at this for more than a year now and still I feel like I am learning something new every couple of days!
In the early 2.2.4 betas, I couldn't send "mode" commands to ring from the Hub (e.g., Disarm, Home, Away). I could READ them, but not set them. All my Door Contact sensor readings, smoke alarm readings, motion sensor readings--all that was working fine. Just sending the arming requests was a problem.
The symptoms were exactly as described here: the Ring Hub went nuts.
Actually, about the first time I saw it, the Ring Hub was like totally hosed. I had to unplug it from the wall AND pull the battery to get it completely powered down. It was 100% non-responsive before that. Then, after that, it would generally just drop off for a few moments at every command.
However, somewhere about the release of .139, it started working for me OK.
Not sure what the deal is.
I also do seem to recall there was SOME discussion (heaven knows were) about something related to HTTP (maybe?) stuff creating problems over time that was supposed to be fixed in 2.2.4. Seemed like the Beta Chromecast integration was triggering that bug (among various, other apps).
I'm still on the ".1" version of the Ring App (it was working--and the migration looked to be painful).
Huh, so if that's the case then my wild guess is probably totally wrong then. Granted, if @Sebastien sees that exact same things coming from this app in both 2.2.4 and 2.2.3 then it's definitely something else going on.
It could also be changes on Ring's side. Who knows.
I know the dude that re-published the app hasn't figured it all out (some pretty complex reverse engineering of Ring's IFTTT implementation) and doesn't have time to get that deep into it now.
That might be the issue - I enabled logging on the app, but not the device. I’ll see what it does this evening when I enable it in both on both the 2.2.3 and the 2.2.4 hubs.
Well, it works on the hub with 2.2.3 while at the « same » time, it doesn’t on the one with 2.2.4, so I think we can eliminate that.
I’ll be curious to know if anyone else that has 2.2.4 with locks integrated through Ring has the same issue! I assume everyone will based on my huge 2-hub sample size...
) either that or setup a second hub with only Ring Connect on it, leaving it with 2.2.3 and using HubConnect to share the lock... both non ideal scenarios...
