I’m using my NS Panel Pro to run my Home Assistant dashboard, which has streams from my Reolink cameras embedded, including my Reolink doorbell.
It’s frustrating because I really wanted to be able to talk back through my NS Panel Pro when someone rings the doorbell, but I’ve never managed to achieve that.
I spent days creating different versions of my dashboard and ended up with two different versions that work on my phone and desktop, using the Frigate custom card and the WebRTC custom card. However, none of them work when using the Home Assistant app installed via F-Droid. I also tried Web Kiosk, but the result is the same.
When using Frigate, the stream is very slow and the microphone icon doesn’t appear. When using the WebRTC custom card, the stream doesn’t load at all.
Could you please provide the exact model name of your Reolink cameras embedded (including my Reolink doorbell)? Could you also tell me how these devices are integrated with Home Assistant? HA’s Reolink integration?
Also, when using the native Picture Entity card, the NS Panel Pro cannot display the Reolink stream with the native Reolink integration. I have to configure a lower stream resolution in order to view the stream properly on the dashboard.
The NSPanel Pro 120 type has a display resolution of 750x1334 (roughly 720p), but the 86 type’s display resolution is only 480x480 (320p). If the media (stream) resolution is higher than the display resolution, then the media could not be played by default.
We are working on it.Please allow us some time to debug it. I am pretty sure that the Home Assistant companion app on NSPanel Pro could support it.
Note: Home Assistant companion app downloaded through F-Droid is the minimal version, not the full version. But according to the official Feature overview, minimal version should also support 2-way audio if it works in full version on Android or iOS.
Regarding the two-way audio (2-way talk) issue you mentioned, we have done a full technical investigation and end-to-end validation.
We have successfully verified the complete two-way audio workflow using the following setup, and it works correctly on NSPanel Pro:
Frigate Integration (HACS)
Frigate Add-on
Advanced Camera Card (HACS)
Note that the Web Kiosk app you mentioned is not viable, as it restricts access to multimedia hardware.
Regarding your mention of using go2rtc, I haven’t verified it myself, mainly because the project is relatively old and its technical implementation approach is similar to Frigate.
Below are the prerequisites, configuration, and step-by-step instructions we used for validation. Please compare them with your setup.
1. Prerequisites (Important)
(Required) The camera must natively support two-way audio
(RTSP backchannel / ONVIF two-way audio),
(Required) Home Assistant must be accessed via https in the Companion Mobile App
If http is used, WebRTC cannot request microphone permission, and two-way audio will not work.
(Recommended) Enable hardware acceleration in the Frigate Add-on
(Recommended) Use a sub-stream (lower resolution / bitrate)
NSPanel Pro has limited performance and may stutter or show a black screen with the main stream.
mqtt:
enabled: true
host: core-mosquitto
port: 1883
user: frigate
password: "1"
topic_prefix: frigate
ffmpeg:
# Enable hardware acceleration (recommended)
hwaccel_args: preset-rpi-64-h264
go2rtc:
streams:
reolink_sim:
# ① Stream for WebRTC live preview
# Audio is re-encoded to Opus for browser/WebRTC compatibility
- "ffmpeg:rtsp://192.168.50.74:8554/stream#video=copy#audio=copy#audio=opus"
# ② Stream for two-way audio (RTSP backchannel)
# MUST be a direct RTSP stream (no ffmpeg here)
- "rtsp://192.168.50.74:8554/stream"
webrtc:
# WebRTC ICE candidates
candidates:
- 192.168.50.52:8555
- stun:8555
cameras:
reolink_sim:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/reolink_sim
input_args: preset-rtsp-restream
roles:
- record
- detect
detect:
enabled: false
version: 0.16-0
After starting the add-on, please verify in the Frigate Web UI that the camera is marked as supporting two-way audio. （Sorry, the image content is in Chinese. I haven’t found a way to switch it to English for now.）
What Home Assistant Server URL are you using on the NSPanel Pro? Is it an HTTPS address?
Additionally, is your HTTPS address provided by Nabu Casa Cloud? If convenient, could you please share the URL with me so I can take a look?
Additionally, you can follow the verification steps I provided in section 2.2 on the NSPanel Pro to check in the Frigate add-on whether the requirements for two-way audio are met.
We can first rule out some environmental factors. Below is a checklist:
The screenshot you shared shows the web interface. What I’d like to confirm is the situation on the NSPanel Pro itself. You can refer to my video for comparison.
I’ve received your URL. If you’re using DuckDNS, then we can rule out the possibility that the issue is related to a self-signed HTTPS certificate.
Software version differences.
Frigate add-on: 0.16.3
Frigate integration (HACS): 5.14.1
Advanced Camera Card: 7.26.0
Another key point is to confirm that your card configuration is the same as mine, or please share your configuration.
frigate add-on: 0.16.3
frigate integration (HACS): 5.14.1
Advanced Camera Card: 7.26.0
Another key point is to confirm that the Card configuration is the same as mine, or please share your configuration.
Home Assistant version installed via F-Droid. 2025.11.5-MINIMAL
I watched your video and everything does seem to be working as expected. I also tested with NSPanel Pro 120 on my side, and two-way audio works normally there as well.
Based on our testing, the NSPanel Pro system and hardware appear to support this feature as expected. Since the behavior you’re seeing doesn’t seem to be easily reproducible on our side, it may be related to a specific software configuration or integration detail. To move this forward more efficiently, I’d suggest opening an issue on Frigate’s GitHub repository, where the maintainers and community can take a closer look and help investigate the root cause.
