-
-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blink alarm_control_panel.blink_sync shows always status disarmed #18341
Comments
Do you have anything in your logs? There were no changes to Blink between 0.80 and 0.81.x |
Hi,
Cannot connect to server with url https://rest.prde.immedia-semi.com/events/network/18390. |
Is that the only error? That is normal to be logged when your token expires and blink needs to reauthorize (it should have never been an error in the first place, that was a mistake in the way the library does its logging). Two follow up questions:
|
Yes, it is the only error related to Blink.
I have created a group to display Blink cameras:
Let me know if you need other details, or to perform any test. |
Thanks for the info! I'm still not quite sure what's going on, so unfortunately I have another request for you. If you go into the states tab under "Developer Info" in the front end (the icon looks lik e
|
Here are the attributes related to blinc_sync, state = "disarmed":
Camera status="Idle":
|
Hmm... all of that looks ok. Perhaps a dumb question, but have you tried restarting home assistant to see if it fixes itself post-restart? That still wouldn't explain why the arm/disarm functions aren't working, but maybe it will work as a temporary solution. |
I restarted few times, no help. :) |
Darn. I'll be honest, I'm pretty stumped. It seems like everything has initialized properly and that you're making the correct service calls. You mentioned that the last working version was 0.80- have you tried reverting to ensure that it works on that old version? Another possibly useful bit of info: do you have and DNS level blockers on your system (such as pihole) that may be denying requests to immedia-semi.com? |
It is strange because other services seems to work just fine:
Indeed I have pi-hole, but I installed it just yesterday. So I don't think it is the issue. What is strange, I haven't seen any request in pi-hole log to "immedia-semi.com", neither blocked or forwarded. Any idea how I can trace this request from Home Assistant ? |
Yeah, the pi-hole idea was just a thought. You would've had to manually add a list containing immedia-semi to actually block it, which I would find strange (although not impossible). I run pi-hole on my network and Blink works just fine, so you should have zero problems out-of-the-box. Given that some of the API calls work, I have a theory (especially based on the comments from this repository which my library is based upon). Basically, Blink implemented their API rather haphazardly, so in Europe not all of the API endpoints are implemented in the same way. Some api calls are to the After I create the issue in the blinkpy repo, it will link here. If you'd like to help with testing (or anyone else reading this that is having a similar issue) just add a comment there (it will involve some command line work). I'll add a list of initial debug steps to try and narrow down what the API calls should be as well. |
Yeah, that was my thought also, that the issue is related to region. At least now you know what is the root cause and could work to fix it. :) |
Seems I found a small bug in the blinkpy api: api.py
Instead of "command_id" in path should be "command" |
I found the issue related to my case. I found it executing Homescreen. I received no info, and I realized it was the info for the last system I created. I removed that system and after that the homescreen endpoint returned correct information about the status of the main system. |
Just found the right API endpoint to check the status of the Network (System): |
Home Assistant release with the issue:
0.81.6
Last working Home Assistant release (if known):
0.80
Operating environment (Hass.io/Docker/Windows/etc.):
Raspberry PI, Hass.io
Component/platform:
Blink component:
https://www.home-assistant.io/components/blink/
Description of problem:
Blink alarm_control_panel.blink_sync shows always status "disarmed". Even if I arm it using service or from Blink mobile application the blync_sync status remains "disarmed". I tried to the service "blink.blink_update", but doesn't help.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):blink:
username: !secret blink_user
password: !secret blink_pass
Traceback (if applicable):
Additional information:
@fronzbot
The text was updated successfully, but these errors were encountered: