-
Notifications
You must be signed in to change notification settings - Fork 36
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
Camera Feed Help #386
Comments
I took some time to look into this more. There is an api called to get all devices, which I'm sure this project already uses. https://www.alarm.com/web/api/systems/systems/<accountCode?> Then call https://www.alarm.com/web/api/video/videoSources/liveVideoSources/ This will return the proxyUrl to get the video:
|
I created a PR that calls the api to get the proxyUrl from the above api: pyalarmdotcom/pyalarmdotcomajax#140 |
Amazing work, thanks for this! I'll work the changes back into v0.6.0, being tested here. A few questions about consuming the feed:
Thanks again. |
I'm looking at the camera feeds (ADC-V610PT & ADC-V521IR) and there are urls with a token on them. Assuming we can figure out the token and what it means and how to create it, having the camera live view may not be so difficult.
The token does not look to be standard jwt.io there are only 2 sections delimited by a
.
Example of first section base64 decoded: (yes looks like incomplete json data)
The second part after the
.
decoded I can base64 decode it, but I don't think it's correct in ASCII I see a lot of???)Ū(
characters. So it is the second part I fear that will be hard, especially if it is signed with a secret key server-side.The text was updated successfully, but these errors were encountered: