-
Notifications
You must be signed in to change notification settings - Fork 82
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
Cannot start stream on Wireless Video Doorbell 2k #1014
Comments
I'm seeing this same behavior with this device and version 0.8.1.9. Also saw it with the previous version. Model info, firmware, etc. same as above. Updating this post to note that I can successfully play the last recorded event, just not the live view. Card configuration is simple:
|
@Deltus7529 Firstly, thank you for posting a decent bug report, most of the ones I get are "it doesn't work" with no other information, so that makes a nice change. Arlo does some weird things with the streams, it returns a You can see the details here: https://github.com/twrecked/hass-aarlo/blob/master/README-advanced.md#user-agents |
@twrecked Thanks for your help. I tried different user_agent and config but I'm just able to get the lastImage and not the live-stream. Logs
Then I click on stop :
And the lastImage get updated (but not always). For the reference, here's my configuration.yaml. I forgot to post it. Maybe I screwed on something. configuration.yaml
And the card :
Tell me if you need different logs or testing. :) |
From my testing, the stream url only works when it looks like:
But not working when it's from vzmodulelive
Whenever I try to stream from this vzmodulelive url with ffmpeg, Im getting:
I've tried using different |
@yongfg for me, it always return the vzmodulelive, regardless of the user agent I choose. Tried in the card config & in the configuration.yaml
I've sort of given up and now using browser_mod to display MyArlo in a new PopUp window, with the Ding event, and Puppeteer to autostart the stream (trigger a click on the play button) and clean some DOM elements. |
Hello,
I've got the Wireless Video Doorbell 2k without a subscription. I tested it for 2 weeks and everything seems to be working fine but not the live stream view.
I didn't find my device in the compatibility list, so I hope I can help you to support this new model.
I tried various configuration to start the stream on the glance card, but it never start. The card is able to get the lastIlmage if I start the stream from the Android or Web App. I don't have the paid subscription so I cannot test the recording or snapshots.
Home Assistant version
Arlo Model info :
Log
ERROR (stream_worker) [homeassistant.components.stream.stream.camera.aarlo_sonnette] Error from stream worker: Error opening stream (INVALIDDATA, Invalid data found when processing input, rtsps://arlostreaming19879-z1-prod.wowza.arlo.com:443/vzmodulelive/AGG141BM00AC5_1732204683134?egressToken=8742ca04_109d_446f_94ea_7bf640e9ede6&userAgent=iOS&cameraId=AGG141BM00AC5_1732204683134&optimization=false&txnId=FE!f4d7fa32-265f-4654-8ab9-6d93bcce5e9e)
Reverse engeneering
I've found this endpoint when starting the stream from the webapp.
I hidded things who looks linked to my account with [xxx]. If not sensitive and needed, tell me :)
eventId
is changing to each new stream.uniqueId
is always the same to each new stream.Headers
Request URL:
https://myapi.arlo.com/hmsweb/users/devices/sipInfo/v2?cameraId=AGG141BM00AC5&modelId=AVD4001A&uniqueId=[xxx]&eventId=FE!effab55f-3b7d-491d-a5fc-00320f01ba1f&time=1732207639600
Payload
cameraId=AGG141BM00AC5&modelId=AVD4001A&uniqueId=[xxx]&eventId=FE!effab55f-3b7d-491d-a5fc-00320f01ba1f&time=1732207639600
Preview
{ "data": { "from": "[xxx]_server", "to": "[xxx]", "action": "is", "resource": "sipDetails", "transId": "[xxx]", "sipCallInfo": { "id": "Conference_[xxx]", "calleeUri": "sip:AGG141BM00AC5_1732209201071_ee6cc1b8f77e48b3ad58e30c0c96f825D@livestream-z1-prod.arlo.com:443", "domain": "livestream-z1-prod.arlo.com", "port": 443, "conferenceId": null, "password": "[xxx]", "deviceId": "AGG141BM00AC5" }, "iceServers": { "uSessionId": "[xxx]", "data": [ { "port": "19302", "domain": "relay02-z1-prod.ar.arlo.com", "type": "stun" }, { "credential": "[xxx]", "port": "443", "domain": "relay02-z1-prod.ar.arlo.com", "transport": "tcp", "type": "turn", "username": "1732209211:[xxx]" }, { "credential": "[xxx]", "port": "443", "domain": "relay02-z1-prod.ar.arlo.com", "transport": "udp", "type": "turn", "username": "1732209211:[xxx]" } ] } }, "success": true }
The text was updated successfully, but these errors were encountered: