Is anybody else getting a ring error message?

Is anybody else getting a ring error message? The credentials are confirmed to be correct, but I'm not getting the 2FA popup asking for credentials, could this be freezing me out of the account or has something changed within the past 2 days that has started to bring up this error message?

Ring Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
Ring Error Maximum retries reached - please go to the Ring plugin's 'Configure...' menu to update credentials
Ring Error plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
Ring Error Connection error - pausing for 30 seconds before retrying (error: 'NoneType' object has no attribute 'get')

Thank you,
Daniel

I'm getting the same errors.

Well that's a relief - then this most likely is a backend change on ring's side!

Yup, getting this too. Disabling plugin for now. But I do hope it's working again. Some of my most important triggers are based on this plugin

Started working again:

Code: Select all

   Ring                            Attempting to connect to Ring.com API and login as xxxxxxxxxxx@gmail.com
   Ring                            Connection to Ring.com API successful

Now I get this error a few times a day:

Code: Select all

Jun 14, 2023 at 10:29:51 AM
   Ring Error                      Connection error - pausing for 30 seconds before retrying (error: 404 Client Error: Not Found for url: https://api.ring.com/clients_api/doorbots/252900495/health?api_version=9)

Jun 14, 2023 at 10:30:22 AM
   Ring Error                      plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)


Now getting this..... Hope it fixes itself again

Code: Select all

 Ring Error                      plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
   Ring Error                      Maximum retries reached - please go to the Ring plugin's 'Configure...' menu to update credentials
   Ring Error                      plugin runConcurrentThread function returned or failed (will attempt again in 10 seconds)
   Ring Error                      Connection error - pausing for 30 seconds before retrying (error: time data '2024-03-26T15:40:50.975Z' does not match format '%Y-%m-%dT%H:%M:%S.000Z')
   

dang, such a small change broke it too.

The timestamp '2024-03-28T02:36:56.462Z' does not match the format string '%Y-%m-%dT%H:%M:%S.000Z'. The the issue is just the milliseconds part of the timestamp, where .'462Z' does not match .'000Z'.

If someone could just switch it to ''%Y-%m-%dT%H:%M:%S.%fZ'" we'd be back in business.

If someone could just switch it to ''%Y-%m-%dT%H:%M:%S.%fZ'" we'd be back in business.

At this point, this plugin is dead as well as several others I have used over the years. Not hopeful this will be resolved even for a seemingly trivial update. Every platform and end device update, more plugins stop working.

I've been using the platform for many years and willingly accepted the annual subscriptions assuming the plugins would be supported, but looks like most of the 3rd party developer community has left. As of right now, only 4 of the 15 or so plugins I once used still work with no replacements in sight. Half my triggers / automations are now disabled and I get less and less value from this platform every update.

Indigo is charging us annual subscriptions for continued use of the platform, but since they rely on 3rd party developers for 90% of the value (plugins) their platform brings, it begs the question...is it time to explore alternatives???

ALSO...DO NOT apply update 2023.2 or else you will be fully out of luck and not just a date parsing issue. As of the 2023.2 update the plugin will not even run or install.

Guess it really is time to explore alternative solutions to Indigo. Quick check on other platforms and they still support many of the devices that are no longer supported here. Guessing thats where the 3rd party development community went.

[jay (support)]

The vast majority of users have successfully upgraded, either through plugin updates or by finding alternatives to plugins which the original developer is no longer active. It is truly unfortunate that you have so many plugins that were abandoned and we feel your pain. Our active 3rd party developers went through a process of upgrading many plugins which were abandoned but which 1) had an appropriate open source license attached to them and 2) which had supported APIs (where appropriate).

Unfortunately, for this specific plugin, the latter is the issue: Amazon has no official Ring API so all other integrations are either via reverse engineering (which will likely break over time) or are using some private API that Amazon only publishes to specific vendors. Because of this kind of scenario, several plugins which were reverse engineered have failed over time as the undocumented connection methods changed on the backend. There is nothing we can do about that.

Indigo is a very small platform: there are only 2 of us working on it full time. We added plugins to allow a more rich 3rd party environment to grow and support things which we just didn't have the time to do ourselves. This has by and large been quite successful. But as you point out the downside is that sometimes developers leave the platform or something else changes out of their control to break a plugin.

We also have to make sure that the software that we deliver is secure and reliable. We had no choice but to upgrade to Python 3 (we delayed the upgrade well past EOL for python 2) because there would be no more security updates to Python 2, an there was no compiled distribution of Python 2 available for Apple Silicon Macs. So we had to do the upgrade for your security as well as Indigo's stability moving forward. Unfortunately, that required that developers update their plugins to Python 3 as it's not backwards compatible in some aspects. Many plugins were updated quickly because the change was minor, and a few took a lot more effort because of underlying dependent library updates.

I'm not writing this as an excuse, but only to summarize where we've been and where we are now. We understand that some users may wish to find other solutions, and we wish you well on your journey. We are doing everything we can to keep Indigo rock-solid, secure, and useful in our ever-changing market.

[jay (support)]

As of right now, only 4 of the 15 or so plugins I once used still work with no replacements in sight. Half my triggers / automations are now disabled and I get less and less value from this platform every update.

Feel free to post the exact plugins which haven't been upgraded on this forum and see if anyone else has found an appropriate substitute or alternate approach.

We are doing everything we can to keep Indigo rock-solid, secure, and useful in our ever-changing market.

Much appreciated.


Sent from my iPhone using Tapatalk

Indigo is a very small platform: there are only 2 of us working on it full time. We added plugins to allow a more rich 3rd party environment to grow and support things which we just didn't have the time to do ourselves. This has by and large been quite successful. But as you point out the downside is that sometimes developers leave the platform or something else changes out of their control to break a plugin.

Jay. My apologies that this came off as a knock against you both. What you two have accomplished is/was amazing. If all the various plugins worked and the 3rd party development community was thriving like it once was, no doubt I would be in HA bliss.