Yes the video stream works for my SCD971.
I can confirm adding the SCD921 to Home Assistant using the Tuya integration as described above works partly.
The camera shows up in HA but the video stream is not working.
The following error is thrown:
Error from stream worker: Error opening stream (INVALIDDATA, Invalid data found when processing input, rtsps://:@aws-tractor2.tuyaeu.com:443/v1/proxy/echo_show/{id})
Debug logging did not reveal any other relevant logs.
The camera works in the Tuya app as usual, except the stream is unusably slow. As opposed to the native app, it does not seem to leverage a direct connection and/or STUN properly.
This gist suggests the rtsp url: pcap philips avent · GitHub
rtsp://{ip}:554/av2_0
But I haven’t been able to get that working either
Same for me. Got the SCD971 which works great in HA but is choppy in Safari (thanks Apple). Anyways using the SCD971 with the Tuya app prevents you from using the smart/ai baby monitor thing that “Philips” has baked into the device…
I saw there is an SCD973 type. Since we are thinking about buying a second babyphone, are there any experiences by integrating the SC973 type? The SCD971 seems to be possible to be integrated.
For any other hints regarding a Babyphone like the SCD971, but cheaper, let me know.
Since some of you did not get the video stream working for the SCD921, I stopped investigating here.
I have the new Avent premium. I tried it through Home Assitant but like others mention, it prevents you from using the app, which renders much of the smarts useless.
I love the baby monitor, I just don’t expect this to work with Home Assistant and you are now buying into a partially cloud-dependent device. If Avent ever shuts it down, you’re basically stuck with local only monitoring through the included video head unit. Which, IMO, is fine. It’s unlikely to happen in the timeframe you actually need a baby monitor and the remote monitoring is kinda pointless since we don’t expect to ever use this outside of the house.
Philips Avent SCD973/SCD923 Baby Monitor - Custom Integration + Bridge Add-on
I have a Philips Avent SCD973/26 baby monitor and got tired of being locked into the official app. So I reverse engineered the Tuya Mobile SDK API it runs on and built a proper Home Assistant integration.
I know a few of you have been trying to get these monitors into HA for a while now. The standard Tuya integration doesn’t cut it for these devices - entities show up but controls don’t work, and the video stream is a dead end through normal RTSP. Some of you also found that pairing with the Tuya Smart app kicks you out of the Philips Baby Monitor+ app entirely.
This integration takes a different approach. It talks to the same Tuya Mobile SDK API that the Philips app uses internally, with the same signing keys extracted from the APK. Your monitor doesn’t know the difference. You keep using the Philips app on your phone if you want - both work simultaneously.
What works
- 1080p live video in the HA dashboard via a WebRTC-to-RTSP bridge (direct RTSP on port 554 is locked down, but the WebRTC signaling path through MQTT works fine)
- Room temperature sensor (properly in Celsius, divided by 100 from the raw DPS 207 value)
- Night light on/off + brightness slider (DPS 138/158)
- Lullaby play/pause/stop/next/prev, all 15 tracks, volume control (DPS 201/202/209 via LAN protocol on port 6668)
- Motion and sound alerts as binary sensors with toggle switches (DPS 134/139)
- Privacy mode to disable the camera (DPS 237)
The video problem and how this solves it
As several people in the existing thread discovered, the monitor exposes port 554 but the RTSP stream behind it is not usable in a standard way. The admin + Virtual ID credentials get you authenticated but the stream itself doesn’t play.
The actual video path these monitors use is WebRTC, negotiated through Tuya’s MQTT broker. This integration includes a Go bridge binary that:
- Authenticates with Tuya cloud using the same Mobile SDK API
- Connects to the MQTT broker for WebRTC signaling
- Establishes a peer connection with the camera
- Receives the H.264 RTP stream
- Re-publishes it as a standard RTSP endpoint on your local network
The bridge runs as an HA add-on. The integration writes the credentials, the add-on picks them up and starts streaming. No manual config needed.
The lullaby problem
Lullaby commands are one of the things that don’t work through the standard Tuya cloud API - the device receives them but ignores playback commands that arrive from the cloud. After decompiling the APK I found that the official app sends these through the Tuya LAN protocol (TCP port 6668, frame type CONTROL). The integration does the same, with a cloud fallback for everything else.
Installation
Add the repo to both HACS and the Add-on Store:
https://github.com/thekoma/aventproxy
HACS gives you the integration, the Add-on Store gives you the bridge. There is a stable and a beta channel for the add-on.
Set up the integration first (Settings > Integrations > Add > Philips Avent Baby Monitor), enter your Baby Monitor+ app credentials and the MFA code from your email. The integration discovers cameras automatically.
Tested on
- Philips Avent SCD973/26 (firmware cadv=1.0.1) - fully working
- HA 2026.4 on Yellow (aarch64) and x86 docker
I have not tested on SCD921, SCD923, or SCD971 but they all use the same Tuya platform. If the Philips Baby Monitor+ app works with your model, this integration should too. Would love confirmation from anyone with these models.
Known limitations
- Video takes a few seconds to connect on first load (inherent to WebRTC signaling via MQTT)
- One camera per bridge instance for now
- Session ID expires periodically - the integration re-authenticates automatically but there is a brief polling gap
- Your HA host needs local network access to the monitor on port 6668 for lullaby control to work reliably
For the technically curious
The full reverse engineering process is documented in a whitepaper in the repo, including the API signing algorithm (HMAC-SHA256 with composite key from 4 APK components), MQTT credential derivation, and about 10 documented failures and dead ends.
The signing algorithm is generic to all Tuya Thing SDK apps. If you have a different Tuya whitelabel camera (not just Philips) and want to build something similar, the APK key extractor tool and documentation should get you started.
A note on code quality
Yes, there is a lot of AI-assisted code in here. I am not going to pretend otherwise. But the goal is to meet the same bar as any serious custom integration. The project currently passes the HA Integration Quality Scale at Gold level (reauth flow, diagnostics, options flow, entity tests, translations). Platinum (full type coverage and strict typing) is next on the list.
If you look at the code and something smells off, open an issue. I would rather fix it than ship it.
What I am looking for
- SCD921/SCD923/SCD971 owners to test and report back
- Bug reports, especially around video stability over long periods
- Feedback on the installation flow
- Anyone interested in contributing
1 Like
Oh wow: awesome!
Once we finished moving, I will definitively try your work on our SCD921.
For the second child, I did not buy Philips again, since I do not support such closed platforms. So I only have the SCD921 and no other model.
- What I really would like is that all the very personal video streams can be blocked from being sent to cloud servers, but can be accessed locally via app (and of course via VPN).
Philips sent me a survey some months ago where they did market reseach about what I am willing to pay for AI features analyzing the child. I just thought ****
So next up is adding the cam to frigate, getting a TPU and running it all locally 
- So once you trigger my imagination, other ideas keep coming: the monitor part (portable hardware screen) seems to also have a WiFi connection. Do you think it could be tricked into playing some other video stream, e.g. from an outdoor camera (while children are playing outside)?
Also the whole monitor unit would make up for a great smart home remote control since it has buttons and a microphone for voice control.
I have an SCD921 and will test this in the coming days/weeks!
Very much appreciated. It seems to work for the SCD923 cam.
“One camera per bridge instance for now”
It would be amazing to get this working for the second cam. Perhaps I missed it, but any advice on how to setup a second bridge? Thank you in advance.
Setup is working though I’m not getting a video feed:
Logger: homeassistant.components.stream.stream.camera.name_babycam_camera
Source: components/stream/__init__.py:491
integration: Stream (documentation, issues)
First occurred: 14:31:37 (5 occurrences)
Last logged: 14:33:17
Error from stream worker: Error opening stream (Connection refused, rtsp://localhost:38554/Name)
Logger: aiohttp.server
Source: /usr/local/lib/python3.14/site-packages/aiohttp/web_protocol.py:488
First occurred: 14:35:23 (2 occurrences)
Last logged: 14:35:33
Error handling request from 172.30.33.3
Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/aiohttp/web_protocol.py", line 517, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/aiohttp/web_app.py", line 569, in _handle
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 214, in forwarded_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 90, in ban_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 295, in auth_middleware
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 41, in headers_middleware
response = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 89, in handle
result = await handler(request, **request.match_info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/camera/__init__.py", line 808, in get
return await self.handle(request, camera)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/camera/__init__.py", line 826, in handle
image = await _async_get_image(
^^^^^^^^^^^^^^^^^^^^^^^
...<4 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/components/camera/__init__.py", line 194, in _async_get_image
else await camera.async_camera_image(width=width, height=height)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/camera/__init__.py", line 580, in async_camera_image
return await self.hass.async_add_executor_job(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
partial(self.camera_image, width=width, height=height)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/concurrent/futures/thread.py", line 86, in run
result = ctx.run(self.task)
File "/usr/local/lib/python3.14/concurrent/futures/thread.py", line 73, in run
return fn(*args, **kwargs)
File "/usr/src/homeassistant/homeassistant/components/camera/__init__.py", line 574, in camera_image
raise NotImplementedError
NotImplementedError
I’m trying this from a non LAN network at the moment, HA sits behind a reverse proxy, maybe that’s the issue?
Ehy! Thank you for testing it out. Have you installed the addon?
The custom component needs a “translator” to inject authentication. The error says that the custom_component is not able to connect to it.
If you look at the readme there are the magic buttons to add the repo on the fly.
I suggest to use the stable for now.
Yes, Ive installed both the addon and the custom integration. The add-on doesn’t log any errors at the moment.
In the Config there isn’t any camera entries, do I need to add it manually there as well?
If yes, how do I find the camera id?
EDIT:
Stupid me, the add-on wasn’t running, feed is working now.
I’m only getting video, no audio at the moment.
Right now it seems like a hit or miss with the video too, sometimes it loads, other times it doesn’t.
Some logs:
18:52:08.070 INF New RTSP connection for camera: snip (bf2fac361301276b1ap0t5)
18:52:08.070 TRC Reusing existing stream for camera: snip
18:52:08.070 TRC Cancelled pending shutdown for camera snip - new client connected
18:52:08.070 TRC Sending RTSP response:
RTSP/1.0 200 OK
Server: TuyaIPCTerminal/1.0
Date: Mon, 27 Apr 2026 16:52:08 GMT
Public: OPTIONS, DESCRIBE, SETUP, PLAY, TEARDOWN
CSeq: 1
18:52:08.071 TRC Received RTSP request:
DESCRIBE rtsp://localhost:38554/snip RTSP/1.0
User-Agent: Lavf62.3.100
Accept: application/sdp
CSeq: 2
18:52:08.071 TRC Sending RTSP response:
RTSP/1.0 200 OK
Server: TuyaIPCTerminal/1.0
Date: Mon, 27 Apr 2026 16:52:08 GMT
Cache-Control: no-cache
CSeq: 2
Content-Base: rtsp://localhost:38554/snip
Content-Length: 488
Content-Type: application/sdp
v=0
o=- 1777308728 1777308728 IN IP4 0.0.0.0
s=Tuya Camera Stream
c=IN IP4 0.0.0.0
t=0 0
a=control:*
a=range:npt=0-
m=video 0 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=42001e
a=control:rtsp://localhost:38554/snip/video
a=recvonly
m=audio 0 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=control:rtsp://localhost:38554/snip/audio
a=recvonly
m=audio 0 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=control:rtsp://localhost:38554/snip/backchannel
a=sendonly
18:52:08.072 TRC Received RTSP request:
SETUP rtsp://localhost:38554/snip/video RTSP/1.0
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
CSeq: 3
User-Agent: Lavf62.3.100
18:52:08.072 TRC Setup track - Video: true, Audio: false, Backchannel: false
18:52:08.072 TRC Setup video track - RTP channel: 0, RTCP channel: 1
18:52:08.072 TRC Added TCP RTP client 8c7c75cced837cf4 (video channel:0, audio channel:2, back audio channel:4)
18:52:08.072 TRC Client 8c7c75cced837cf4 setup count: 1
18:52:08.072 TRC Sending RTSP response:
RTSP/1.0 200 OK
Server: TuyaIPCTerminal/1.0
Date: Mon, 27 Apr 2026 16:52:08 GMT
CSeq: 3
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
Session: 8c7c75cced837cf4;timeout=60
18:52:08.073 TRC Received RTSP request:
SETUP rtsp://localhost:38554/snip/audio RTSP/1.0
Transport: RTP/AVP/TCP;unicast;interleaved=2-3
CSeq: 4
User-Agent: Lavf62.3.100
Session: 8c7c75cced837cf4
18:52:08.073 TRC Setup track - Video: false, Audio: true, Backchannel: false
18:52:08.073 TRC Setup audio track - RTP channel: 2, RTCP channel: 3
18:52:08.073 TRC TCP client 8c7c75cced837cf4 already exists, updating channels (video:0->0, audio:2->2, back:4->4)
18:52:08.073 TRC Client 8c7c75cced837cf4 setup count: 2
18:52:08.073 TRC Sending RTSP response:
RTSP/1.0 200 OK
Server: TuyaIPCTerminal/1.0
Date: Mon, 27 Apr 2026 16:52:08 GMT
CSeq: 4
Transport: RTP/AVP/TCP;unicast;interleaved=2-3
Session: 8c7c75cced837cf4;timeout=60
18:52:08.074 TRC Received RTSP request:
SETUP rtsp://localhost:38554/snip/backchannel RTSP/1.0
Transport: RTP/AVP/TCP;unicast;interleaved=4-5
CSeq: 5
User-Agent: Lavf62.3.100
Session: 8c7c75cced837cf4
18:52:08.075 TRC Setup track - Video: false, Audio: false, Backchannel: true
18:52:08.075 TRC Setup backchannel track - RTP channel: 4, RTCP channel: 5
18:52:08.075 TRC TCP client 8c7c75cced837cf4 already exists, updating channels (video:0->0, audio:2->2, back:4->4)
18:52:08.075 TRC Client 8c7c75cced837cf4 setup count: 3
18:52:08.075 TRC Sending RTSP response:
RTSP/1.0 200 OK
Server: TuyaIPCTerminal/1.0
Date: Mon, 27 Apr 2026 16:52:08 GMT
CSeq: 5
Transport: RTP/AVP/TCP;unicast;interleaved=4-5
Session: 8c7c75cced837cf4;timeout=60
18:52:08.077 TRC Received RTSP request:
PLAY rtsp://localhost:38554/snip RTSP/1.0
Range: npt=0.000-
CSeq: 6
User-Agent: Lavf62.3.100
Session: 8c7c75cced837cf4
18:52:08.077 TRC Sending RTSP response:
RTSP/1.0 200 OK
Server: TuyaIPCTerminal/1.0
Date: Mon, 27 Apr 2026 16:52:08 GMT
Range: npt=0.000-
CSeq: 6
Session: 8c7c75cced837cf4
RTP-Info: url=rtsp://localhost:38554/snip;seq=1;rtptime=0
18:52:08.077 INF Starting RTSP stream for client 8c7c75cced837cf4
18:52:08.096 INF New RTSP connection established, session=20c3014b75114644
18:52:08.096 TRC Received RTSP request:
DESCRIBE rtsp://localhost:38554/snip RTSP/1.0
Require: www.onvif.org/ver20/backchannel
User-Agent: go2rtc/1.9.14
CSeq: 1
Accept: application/sdp
18:52:08.097 INF New RTSP connection for camera: snip (bf2fac361301276b1ap0t5)
18:52:08.097 TRC Reusing existing stream for camera: snip
18:52:08.097 TRC Sending RTSP response:
RTSP/1.0 200 OK
Server: TuyaIPCTerminal/1.0
Date: Mon, 27 Apr 2026 16:52:08 GMT
Cache-Control: no-cache
CSeq: 1
Content-Base: rtsp://localhost:38554/snip
Content-Length: 488
Content-Type: application/sdp
v=0
o=- 1777308728 1777308728 IN IP4 0.0.0.0
s=Tuya Camera Stream
c=IN IP4 0.0.0.0
t=0 0
a=control:*
a=range:npt=0-
m=video 0 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=42001e
a=control:rtsp://localhost:38554/snip/video
a=recvonly
m=audio 0 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=control:rtsp://localhost:38554/snip/audio
a=recvonly
m=audio 0 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=control:rtsp://localhost:38554/snip/backchannel
a=sendonly
18:52:08.097 TRC Received RTSP request:
SETUP rtsp://localhost:38554/snip/video RTSP/1.0
CSeq: 2
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
18:52:08.097 TRC Setup track - Video: true, Audio: false, Backchannel: false
18:52:08.097 TRC Setup video track - RTP channel: 0, RTCP channel: 1
18:52:08.097 TRC Added TCP RTP client 20c3014b75114644 (video channel:0, audio channel:2, back audio channel:4)
18:52:08.097 TRC Client 20c3014b75114644 setup count: 1
18:52:08.097 TRC Sending RTSP response:
RTSP/1.0 200 OK
Server: TuyaIPCTerminal/1.0
Date: Mon, 27 Apr 2026 16:52:08 GMT
Transport: RTP/AVP/TCP;unicast;interleaved=0-1
Session: 20c3014b75114644;timeout=60
CSeq: 2
18:52:08.097 TRC Received RTSP request:
SETUP rtsp://localhost:38554/snip/audio RTSP/1.0
Transport: RTP/AVP/TCP;unicast;interleaved=2-3
CSeq: 3
Session: 20c3014b75114644
18:52:08.097 TRC Setup track - Video: false, Audio: true, Backchannel: false
18:52:08.097 TRC Setup audio track - RTP channel: 2, RTCP channel: 3
18:52:08.097 TRC TCP client 20c3014b75114644 already exists, updating channels (video:0->0, audio:2->2, back:4->4)
18:52:08.097 TRC Client 20c3014b75114644 setup count: 2
18:52:08.097 TRC Sending RTSP response:
RTSP/1.0 200 OK
Server: TuyaIPCTerminal/1.0
Date: Mon, 27 Apr 2026 16:52:08 GMT
Session: 20c3014b75114644;timeout=60
CSeq: 3
Transport: RTP/AVP/TCP;unicast;interleaved=2-3
18:52:08.098 TRC Received RTSP request:
PLAY rtsp://localhost:38554/snip RTSP/1.0
CSeq: 4
Session: 20c3014b75114644
18:52:08.098 TRC Sending RTSP response:
RTSP/1.0 200 OK
Server: TuyaIPCTerminal/1.0
Date: Mon, 27 Apr 2026 16:52:08 GMT
Range: npt=0.000-
CSeq: 4
Session: 20c3014b75114644
RTP-Info: url=rtsp://localhost:38554/snip;seq=1;rtptime=0
18:52:08.098 INF Starting RTSP stream for client 20c3014b75114644
18:52:13.111 TRC Received RTSP request:
TEARDOWN rtsp://localhost:38554/snip RTSP/1.0
CSeq: 5
Session: 20c3014b75114644
18:52:13.111 TRC Sending RTSP response:
RTSP/1.0 200 OK
Server: TuyaIPCTerminal/1.0
Date: Mon, 27 Apr 2026 16:52:13 GMT
CSeq: 5
Session: 20c3014b75114644
18:52:13.111 INF Tearing down RTSP stream for client 20c3014b75114644
18:52:13.111 TRC Removed RTP client 20c3014b75114644
The Download Snapshot function doesn’t seem to work, it downloads a 55bytes png file that doesn’t contain picture data, content of the file is
500 Internal Server Error
Server got itself in trouble
To get the audio you have to unmute the video feed.
About the snapshot that’s interesting could you provide a log and more info via GitHub issue?
Also the model of the camera so I can put down a table for supported hardware.
I received the video stream of SCD921 and tested nightlight successfully 
Well done!
Is there a way that the camera runs 100% local?
The audio slider is by default set to max volume, I don’t see any unmute button? I’m on MacOS and Safari if that matters.
By model you mean SCD921?
Not sure where I can find any log related to the downloading of the snapshot, couldn’t see anything in the HA logs.
Hi gon0 no, the authentication happens via MQTT so there is no way (that I found) to talk directly to the cam to gain control.
BUT:
The portable display does talk with the camera and I suspect being able to handshake with private keys.
IMHO there could be a way to extract those infos but it’s OOS for me now.
The streaming and the control does happen 98% locally apart from the MQTT comunication.
1 Like
Hey Skye, glad to hear video is working!
About the audio: that’s a Safari thing unfortunately — Safari’s autoplay policy blocks audio by default until you interact with the page. The volume slider you see controls the
device speaker volume (DPS 209), not the browser playback volume. To actually hear audio from the stream, you need to unmute the video player itself — but Safari hides that button
in some card configurations.
A couple of things you can try:
- Click/tap directly on the video feed — that should trigger the browser interaction Safari needs to allow audio playback
- If you’re using the WebRTC Camera custom card, try right-clicking the video → “Show Controls” to get the native browser audio controls
- Using the HA Companion App on macOS instead of Safari tends to work better since it doesn’t enforce the same autoplay restrictions
- This is not specific to our integration — it’s a well-known Safari limitation that affects pretty much any
camera feed in HA
About the snapshot 500 error: yeah, that’s a known limitation right now — the camera entity doesn’t implement a native snapshot method yet since the stream comes from the RTSP
bridge, not directly from the device. It’s on the list but not a priority at the moment. As a workaround you can grab a snapshot through the HA service camera.snapshot which pulls
a frame from the running stream instead.
And yes, SCD921 is perfect — good to have confirmation it works. I’ll add it to the tested models list!
Let me know if the audio trick works for you.
1 Like
I tried using the iOS companion app, clicked unmute/mute/unmute but still not getting any audio on my iPhone, nor using the clicking on the feed on Safari on MacOS to get audio.
Also another thing I noticed is that the motion detection sensor does not work and the sound detection is behaving very weird:
WiFi signal sensor also is “stuck” at -75dBm, I can’t believe the signal strength doesn’t fluctuate one bit in 24 hours.
The temperature sensor is working fine.
This works great, Thanks!!1! Just got the SCD643/26 in today and got everything up and running within 10 minutes.
One question: you said " 5. Re-publishes it as a standard RTSP endpoint on your local network". I can’t seem to find that url, can you share it? Or where to find it? Thanks again!
Edit: Also: Same Question as Svuo, any advise on how to setup a second bridge?
Hi! I've just installed the integration and the bridge add on, when after entering credentials and then the code I get a cannot connect error but in HA but I get the notification in the Avent App that a new login was attemptemted. I would appreciate some help!
Thanks!