Blink auth email returns |DEVICENAME|
See original GitHub issueDescribe the bug With latest 0.15.0-rc versions, the device name returned by the blink servers is populated with |DEVICENAME| rather than the actual device name being send. We should double check we’re not sending bad data and causing that problem.
Expected behavior
Should return the device_id
parameter we initialize Blink with.
Home Assistant version (if applicable): <HA Version Number>
blinkpy
version (not needed if filling out Home Assistant version): 0.15.0-rc1
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Managing mobile devices with access to your Blink account
Use this article to understand how to login and manage your Blink account across multiple mobile devices with the Blink app. To ensure...
Read more >New Login Method - blinkpy will stop working May 11th unless ...
I noticed in the api.py file that you're specifying Blinkpy for both the identifier and the name. I wonder if that *|DEVICENAME|* value...
Read more >Blink Camera's discontinuing "legacy" login
Received a nastygram from Blink today titled “Disabling Unauthorized 3rd Party Automation Scripts” (Text of email below).
Read more >Additional Devices & Preferences - UCSD Blink
Learn how to re-name existing devices or add new ones, and tell Duo your preferred method of completing two-step login.
Read more >Authentication methods - Blink The Frontline App
There are a variety of different authentication methods available on Blink, and it's important ... Switching from Email/SMS code to Password.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, thanks for replying. P
Ok, the problem is the v3 login endpoint (seems to not be fully implemented which may explain random issues with logging in). The v4 login endpoint I had was missing some info. After fixing that I not only get the correct device name in the email, I also received an actual 2FA code to use. This is being fixed in PR #261 (along with a ton of changes to the libray). Just FYI