-
-
Notifications
You must be signed in to change notification settings - Fork 32k
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
Ring Door Bell Camera - Not display entity_picture or video_url #10407
Comments
I am also seeing this. Occasionally, I see |
@tchellomello Yes, i'm a premium subscriber. |
I may be in the same boat, I'll have to double check. I'm also Premium. After a bit, I get "Image not available", but if I restart HASS it works as expected. |
Confirmed, 1 hour on the dot and you get the below from the URL, as well as "Image not available" |
@ntalekt could you provide the HASS logs on the issue? |
@thegame3202 @ntalekt did you guys check if the local time of your server is correct? I'm going to verify it tonight |
@tchellomello server time is correct. I'll enable debug logs and see if there is anything. |
@tchellomello Same here, time is correct. It seems like the debug logs think that the video is playing. Not sure what I can post since they have credentials in them:-\ Here is the start of what I believe to be the relevant line: Are you not seeing this on your end? Part of that url is "expires=3600" which is 1 hour in seconds. I'm thinking it expires and doesn't generate a new link? Here is that part: If you want to tell me what to remove, credentials wise, I'm happy to post logs. Thanks! |
I ran in debug for a couple hours. I see ffmpeg snatching a single frame every 3-5 seconds but I don't see the mp4, X-Amz-Credential or the X-Amz-Signature input parameter change.
|
Hello guys, <Error>
<Code>AccessDenied</Code>
<Message>Request has expired</Message>
<X-Amz-Expires>3600</X-Amz-Expires>
<Expires>2017-11-06T23:49:25Z</Expires>
<ServerTime>2017-11-07T02:54:05Z</ServerTime>
<RequestId>064B<REDACTED></RequestId>
<HostId>
7sI7b<REDACTED>
</HostId>
</Error> I'm investigating it now |
Guys, any of you see the entry "Updated Ring DoorBell" on your logs? |
@tchellomello of course I didn't save the log... Running in debug again. I'll update shortly. |
Great news!! Troubleshooting the issue with @ntalekt we were able to find the problem. Actually, there were 3 problems. My apologies for it.
We will be running the test code overnight, however if you want test it you can download it at https://gist.github.com/tchellomello/1197dc38c09c60d6b3922937de4c210f Just create a directory Nov 06 23:50:01 myserver.home hass[31057]: 2017-11-06 23:50:01 DEBUG (SyncWorker_8) [custom_components.camera.ring] Checking if Ring DoorBell needs to refresh video_url
<< went outside to force a new video to be captured... >>
Nov 06 23:51:31 myserver.home hass[31057]: 2017-11-06 23:51:31 DEBUG (SyncWorker_3) [custom_components.camera.ring] Checking if Ring DoorBell needs to refresh video_url
Nov 06 23:51:32 myserver.home hass[31057]: 2017-11-06 23:51:32 INFO (SyncWorker_3) [custom_components.camera.ring] Ring DoorBell properties refreshed Please let me know if the results.. Thank you!! mmello |
@tchellomello It ran clean all night. Thanks for the quick turnaround!
|
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (
hass --version
):0.57.2
Python release (
python3 --version
):3.6.3
Component/platform:
Ring Binary Camera
@tchellomello
Description of problem:
Ring Camera won't display
entity_picture
or playvideo_url
when clicked. After a restart it worked for about an hour. Could the camera not be refreshing the URL before theX-Amz-Expires
expires? When trying to browse thevideo_url
in chrome I get:Expected:
To display image snapshot and video.
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info:
The text was updated successfully, but these errors were encountered: