Indigo Domotics

Hey Zach. Great job on the plugin! I love it.

Recently I've been getting authentication errors and I can no longer log in.

A few things for you to know:
1) I do not use 2FA.
2) I did try to downgrade the plugin and that wasn't successful.
3) I can successfully use those credentials to log in through the web and the ring app.
4) the doorbell device is no longer listed in the dropdown in the ring plugin device (this may be obvious) but the attributes of the account and doorbell are still listed in the device from the last successful GET

Code: Select all

Jan 11, 2020 at 10:57:57 AM
   Reloading plugin "Ring 1.7.0"
   Stopping plugin "Ring 1.7.0" (pid 12343)
   Stopped plugin "Ring 1.7.0"
   Starting plugin "Ring 1.7.0" (pid 12408)
   Started plugin "Ring 1.7.0"
   Ring                            Attempting to connect to Ring.com API and login as xxxxxxxxxx@gmail.com
   Ring Error                      Login error - please go to the Ring plugin's 'Configure...' menu to update credentials
   Ring Error                      Login error - please go to the Ring plugin's 'Configure...' menu to update credentials

Jan 11, 2020 at 10:58:36 AM
   Ring                            Retrieving all available devices from Ring.com (this may take a moment, please be patient)
   Ring                            Connection to Ring.com API down; can't print devices to Event Log
   Ring                           
   Ring                            Done printing all available Ring devices to Event Log

Thanks for the note! The short version is that Ring temporarily blocked the underlying python library due to some bugs, but the awesome folks who developed the library worked over night to fix it. Ring themselves were friendly about the whole thing, but a fix was definitely needed so as not to hammer their API. I'm working to port to the new version of the library today.

(Temporarily marked this thread as an "announcement" to catch people's attention while the fix is being worked)

Just a quick update - the changes to the underlying python library are going to take a little bit of time to adapt to; hoping to have something up and running later today.

I've just pushed out version of 1.7.1 of the plugin, which should fix this.

Thanks for the huge effort Zach! I'm happy to test for you if you need it.

ryanbuckner wrote:

Thanks for the huge effort Zach! I'm happy to test for you if you need it.

Yes, please! Let me know how it goes.

Thanks Zach!

Operating just fine on two separate Indigo servers.

Many thanks for the prompt action.

mclass


Sent from my iPad using Tapatalk

mclass wrote:

Operating just fine on two separate Indigo servers.

Great!

I'm back baby!

Small errors remain:

Code: Select all

 Ring Error                      exception in deviceStartComm(Front Doorbell): year=1899 is before 1900; the datetime strftime() methods require year >= 1900


ryanbuckner wrote:

I'm back baby!

Small errors remain:

Code: Select all

 Ring Error                      exception in deviceStartComm(Front Doorbell): year=1899 is before 1900; the datetime strftime() methods require year >= 1900


Oh, ha, localizing the default date of January 1 1900 puts some people back in 1899. At least that one is an easy fix!

ryanbuckner wrote:

Code: Select all

 Ring Error                      exception in deviceStartComm(Front Doorbell): year=1899 is before 1900; the datetime strftime() methods require year >= 1900


Just fixed this in version 1.7.4

jut upgraded. Still getting error:

Code: Select all

Jan 12, 2020 at 8:22:59 PM
   Reloading plugin "Ring 1.7.4"
   Stopping plugin "Ring 1.7.4" (pid 6802)
   Stopped plugin "Ring 1.7.4"
   Starting plugin "Ring 1.7.4" (pid 6890)
   Started plugin "Ring 1.7.4"
   Ring Error                      exception in deviceStartComm(Front Doorbell): year=1899 is before 1900; the datetime strftime() methods require year >= 1900
   Ring                            Attempting to connect to Ring.com API and login as ryanbuckner@gmail.com
   Ring                            Connection to Ring.com API successful


ryanbuckner wrote:

jut upgraded. Still getting error:

Ah - I failed to account for previously existing states still set to the initialization default of January 1, 1900. I'll get this fixed. Fortunately, this is largely a cosmetic issue, so everything should continue to function, just a couple of device states won't be properly initialized to default values.

ryanbuckner wrote:

jut upgraded. Still getting error:

Please try version 1.7.5, which I just released, when you have a moment.