Challenges upgrading to the latest blinkpy, v5 endpoint

[swerb73]

@fronzbot, I've been working to upgrade to the latest version of blinkpy, converting to the asyncio, await, etc... I think I have the code setup correctly per the documentation and am always getting:

Connection error. Endpoint https://rest-prod.immedia-semi.com/api/v5/account/login possibly down or throttled.
Login endpoint failed. Try again later.
Cannot setup Blink platform.
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x10b7d2990>

Here's my code:

import asyncio
from aiohttp import ClientSession
from blinkpy.blinkpy import Blink

async def start():
blink = Blink(session=ClientSession())
await blink.start()
return blink

blink = asyncio.run(start())

[fronzbot]

That looks right to me (@mkmer do you agree?).

I've noticed an increase incidence of users reporting the same "endpoint" down issue. So I suspect it's a Blink problem- just a question of intermittent server problems or a new login endpoint being rolled out. I also noticed my Blink app updated recently which makes me worried they're mucking with the endpoints again 😨

[swerb73]

Thanks. I was running 0.19 before upgrading this morning and it worked fine in the non-async variation. If I fail back to it all is good, but as soon as I head to 0.22.3 with async code then it fails?

[mkmer]

Code looks correct to me as well. Maybe your missing the blink.auth config? I have a "blinksync" program in the repo that you could compare to:
https://github.com/fronzbot/blinkpy/blob/a9c7c407790807dd086a32fa5353ca53ecdbfb05/blinksync/blinksync.py
The unclosed client session is just a bit of missing code when the program exits.
Hopefully it's on the Blink side :)

I too noticed the updated phone app - changed around how we enable/disable motion detection per camera (in a less user friendly way). Boo.

[swerb73]

Hey guys, thanks for the help... I've not copied in the instructions from the home page and tried with/without username/password passed and still getting the same error.

I had thought the blink.auth config was it since I didn't have that but no change when putting that in. I'm on a Mac with Python 3.11.4 in case that matters?

[swerb73]

Anything else I can do to log/debug?

[fronzbot]

I'm on a Mac with Python 3.11.4 in case that matters?

It shouldn't- the library is platform agnostic. I can't think of any reason the async would fail but the old code works. For now, I'd say just stick with the old pre-async version. I'm going to turn this into an issue so we can better track it

[swerb73]

OK, which version do you recommend I use, would that be 0.21.0?

[fronzbot]

Yeah, that should be fine

[swerb73]

OK, confirmed, reverted back to 0.21.0 and my old code worked. Is this using the v5 endpoint?

[fronzbot]

Yeah login endpoints are the same in 0.21.0 and 0.22.0

[swerb73]

@fronzbot - can you let me know if you want me to test anything implemented to help with the issue here? Happy to help.

[fronzbot]

Honestly, I don't even know where to begin with that debug.

[mkmer]

I suppose you could run full debug and see if the trace gives anything interesting... My debug looks like this:

INFO:blinkpy.auth:Token expired, attempting automatic refresh.
INFO:blinkpy.auth:Attempting login with https://rest-prod.immedia-semi.com/api/v5/account/login
DEBUG:blinkpy.helpers.util:Setting base url to https://rest-u034.immedia-semi.com.
DEBUG:blinkpy.blinkpy:Initialized last_refresh to 1700430596 == 2023-11-19 16:49:56
DEBUG:blinkpy.api:Making GET request to https://rest-u034.immedia-semi.com/networks
DEBUG:blinkpy.api:Making GET request to https://rest-u034.immedia-semi.com/api/v1/camera/usage
DEBUG:blinkpy.sync_module:Initializing the sync moduler

Looks like your stuck on step 2 with a timeout, Maybe aiohttp is missing some component? Maybe try pip install aiohttp
I fire up logging like this: (also in blinksync.py example)

if __name__ == "__main__":
    logging.basicConfig(level=logging.DEBUG)
    loop = asyncio.get_event_loop()
    loop.run_until_complete(main())

Also, aiohttp is more strick on https - if you have some sort of unsigned or invalid ssl cert in there, aiohttp will complain where requests doesn't. There is a way to tell aiohttp not to validate the certs, if that turns out to be the problem. I think it tells you explicitly when the certs are invalid - at my office they have a MITM firewall that I had to accept unknown certs.