pcap philips avent

pcap philips avent.txt

OPTIONS rtsp://192.168.85.42/av2_0 RTSP/1.0
CSeq: 34
User-Agent:.aQ.E..d.{..FrB.=

RTSP/1.0 200 OK
CSeq: 34
Date: Mon, Sep 12 2022 15:17:41 GMT
Public: OPTIONS,DESCRIBE,SETUP,PLAY,PAUSE,TEARDOWN

DESCRIBE rtsp://192.168.85.42/av2_0 RTSP/1.0
CSeq: 35
User-Agent: sky-light (ysp20200805)
Accept: application/sdp

RTSP/1.0 200 OK
CSeq: 35
Date: Mon, Sep 12 2022 15:17:41 GMT
Content-Type: application/sdp
Content-length: 415
Content-Base: rtsp://192.168.85.43/av2_0/

v=0
o=StreamingServer 3331435948 1 IN IP4 192.168.85.43
s=RTSP Session
c=IN IP4 0.0.0.0
t=0 0
a=control:*
a=range:npt=0-
m=video 0 RTP/AVP 96
a=control:trackID=0
a=rtpmap:96 H264/90000
a=fmtp:96  packetization-mode=1; profile-level-id=4D0033; sprop-parameter-sets=J00AM+dAPAET8s1AQEB8AAADAAQAAAMAyMQAAfoYAAF7k///wKA=,KO48gA==;
m=audio 0 RTP/AVP 97
a=control:trackID=1
b=as:32
a=rtpmap:97 L16/16000/1
SETUP trackID=0 RTSP/1.0
CSeq: 36
User-Agent: sky-light (ysp20200805)
Transport: RTP/AVP/TCP;unicast;interleaved=0-1

RTSP/1.0 200 OK
CSeq: 36
Date: Mon, Sep 12 2022 15:17:41 GMT
Transport: RTP/AVP/TCP;unicast;destination=192.168.85.43;source=192.168.85.43;interleaved=0-1
Session: 1546;timeout=65

SETUP trackID=1 RTSP/1.0
CSeq: 37
User-Agent: sky-light (ysp20200805)
Transport: RTP/AVP/TCP;unicast;interleaved=2-3
Session: 1546;timeout=65

RTSP/1.0 200 OK
CSeq: 37
Date: Mon, Sep 12 2022 15:17:42 GMT
Transport: RTP/AVP/TCP;unicast;destination=192.168.85.43;source=192.168.85.43;interleaved=2-3
Session: 1546;timeout=65

PLAY rtsp://192.168.85.43/av2_0/ RTSP/1.0
CSeq: 38
User-Agent: sky-light (ysp20200805)
Session: 1546;timeout=65
Range: npt=0.000-

RTSP/1.0 200 OK
CSeq: 38
Date: Mon, Sep 12 2022 15:17:42 GMT
Range: npt=0.000-
Session: 1546
RTP-Info: url=rtsp://192.168.85.43/;seq=0

$../....N..LE..	'Q_0....Tn...l........22 .(`.o%....$.......E.......zlm............#$.......N..LE..	(.<.$....`..N..LE..	<....P:...*1..g|....$.^.U..\...g.&v|..)...NoX.z..""....u........}...u..k....	...[..c...	I.......D..b......z(l.gCzC..........l..C..F...#.~+C...<g$.F}...o.. ........9......a ......n)Jd....+.7[.+P........C.vG....$..T.>. .......
oW...i..."B.Qj.....`.4.O.x..G;v.,...u.....|5P.....d..u$.4#?..A......%O	.!..Wt.....I#O.."m;,A[a...b......;.QV...12j]..N....8.....J+...G$;.xi.....ts.._3d.l[B.).0W:.ls.4^.p.p.E....}CL....E...........	.m.d....n..
...F2T...w^OCvGJ..N...P..K	b..S.Z..:...$..<.c.c.Z.......`PbZ..Q.;.
.....U7`..j..?....z$..w....*......Vo.YK .......$.....t...-...T.<....$...I.xFA. ....$K.4..n...[R$>...\...v9w.p.....Fe.H..y!E..h1.q........Ik\H...:...^...D..]#...A+4..k.E..............{a.3..6.X.=.`=.f~,MB.A...i.v..6.8o.G....I3v.1.U.	F.].HNy3.+.'_.>...7Gn*....j.W..
.~.k;...6M/1rSb{.....v^g-....I
.Q.....r..P...+. .).....<.....0...^&..
.I..L.......}`Q.v.....4...8.j.:TX...].g..I.Y.7..zq3.n...~v..&-.7[.....>....'.!jx.h<..,.5..A.c*.........w"e..................VO?.dld.....
).7A....q......rFf..q..2.w.....;W.6 .%.Av.a.....4\$h...L...>.b..]L.}..l..t.".@5....tYuuQ.?./....PG.S...f.*T.8.t.2eQH.0:N.u..6m...X.8..}2...w.\...p.M^......q...<w.....q^....P....*.m..VJ.F.7h~.ul..\'U'j...V..W*...V......7R.I&c.e.z......}..'...bM..J.-PA..=0..Ad.B....'......J........./&[... .$.I =..._z;..+S...P..a....pOgzP..........B.., ..s.e....,B	.P....-....`.......
s.e...zi #:.b/w.x.S.W"...A+..K..I.. ..!...p....p...7...-X.....\Y$....`..N..LE..	<...L^Ek.........H.@m.WQH.!5_w.-.eJ"[..$
..-...:Dc.K!.m..v......U.n6.@Pb9......s.=z..4.....a.
:._....+...R.Up....b....2...,.c.g.N....r.......Y..8-*.!...T..Vf?....r.....O(x.......p........v..4JV{..g.
..j!...r.A.14.	.yAx...
.e(....y...c.?.`A.paj
O.-$.&-..%.R..4.W:.%jN..al
.......	.....G..Z..../Z...5.....&.*
.......\Q..-....p.F.....;..........1.f`.....b....B+......l4.|..]e.jf .,....n.?......|......
.......l..Q...0...mU.+.!wRD.HQ.Q.....!...J...
....Y....3.{.....VD./...>R..6.-..KfD.2K.. ..p...^...Zr.!..a......{.VD;..r-...t~......:.p..s..G...uN.........NB..j.....H.".........kt.......{v}.....!y.;a.6.....35...v.Q.#...r8.....y... ...guaF...x....`.

Force the connection between between monitor and camera do be via WIFI. I did it moving into a room where RF did not come but wifi did.

Anyway it's a white label tuya environment. pretty nasty to hack

I'm trying this with tcpdump on my router, but was unable to capture anything useful. Which type of Philips Avent Baby Monitor did you use to capture these packets? Did you see/use any credentials for the rtsp stream?

Some of the forum people over at homeassistant have parts of this issue figured out.
Haven’t tested any of this myself yet.
https://community.home-assistant.io/t/philips-avent-scd921-connected-videophone-accessing-rtsp-stream-user-password-unknown/641344

Some of the forum people over at homeassistant have parts of this issue figured out. Haven’t tested any of this myself yet. https://community.home-assistant.io/t/philips-avent-scd921-connected-videophone-accessing-rtsp-stream-user-password-unknown/641344

No they have not. They connected via Tuya, not directly. I came here via the link in that topic.

Some of the forum people over at homeassistant have parts of this issue figured out. Haven’t tested any of this myself yet. https://community.home-assistant.io/t/philips-avent-scd921-connected-videophone-accessing-rtsp-stream-user-password-unknown/641344

No they have not. They connected via Tuya, not directly. I came here via the link in that topic.

So yes, they have in fact figured out parts of the issue. (I never claimed they solved the full problem)
But good to know this is now going in a circle and people coming to this thread now know that both posts/threads are looking for the same solution.

I would like to solve it as well somehow to keep the original monitor and the app working.

This gist shows a pcap of the RTSP stream of a Philips Baby Monitor, not anything Tuya related. Please keep the Tuya/app discussion in the Home Assistant topic and focus on the RTSP stream here.

Do you have any idea how to figure out the username and password for the RTSP stream?

https://github.com/thekoma/aventproxy took me some time. I need beta testers.

https://github.com/thekoma/aventproxy took me some time. I need beta testers.

@thekoma Amazing! Just trying to install it, but the button for installing the WebRTC integration does not seem to work: "Error loading apps - Unknown command.":

I can only find the Avent integration, but not the WebRTC integration on HACS. I don't know how to add subfolders in monorepos to HACS. What am I missing?

https://github.com/thekoma/aventproxy took me some time. I need beta testers.

@thekoma Amazing! Just trying to install it, but the button for installing the WebRTC integration does not seem to work: "Error loading apps - Unknown command.":

I can only find the Avent integration, but not the WebRTC integration on HACS. I don't know how to add subfolders in monorepos to HACS. What am I missing?

Ah, sorry, just noticed that this is an addon, not a HACS integration. My bad. Not using home assistant OS, so will figure out how to add this to my dockerized setup.

Update: made it work with my docker compose setup by adding this as a service:

services:
  aventproxy-bridge:
    image: ghcr.io/thekoma/aventproxy-bridge:latest
    container_name: aventproxy-bridge
    restart: unless-stopped
    network_mode: host
    environment:
      # We set this to true so it waits for the HA integration to generate the file
      - WAIT_FOR_CONFIG=true
    volumes:
      # Map your Home Assistant config folder to /config in the bridge
      # Replace the left side with the actual path to your HA config
      - /share/Container/homeassistant:/config:ro

Works great so far!

@thekoma Thanks a lot for this - it's very stable, I have not identified any bugs so far, all works like a chance. Any chance respiratory rate and sleep detection can also be exposed as a sensor (awake, light sleep, deep sleep) or even cry interpretation? Or are they somehow handled by the client?