You should first try it on your desktop and debug there.
It’s strange to me that the first popup shows an error. It’s just a picture-elements card using the reolink doorbell fluent entity (should use that entity) with some overlay icons.
What version of browser-mod are you using? It might be that you have an older version?
The picture-elements card uses a bit of a hack. It sets the image like:
so it might be conflicting. You can try to “Take control” of the automation and try to put a local image there.
If that doesn’t work, you can try to remove some other properties of the card
The popup not appearing might be because browser mod is interpreting the different domains (local IP vs NabuCasa URL) as different browsers. You should check that (in the browser-mod tab in HA) when switching the URL.
Just to be clear, the 2 way audio will only work with HTTPS.
Thank for the reply.
you were right about the reason why the pop up didn’t work, I had to register the browser again with the public URL. The 2 way audio is still not working though. With the public address I know see the green dot on the top right of the screen showing a little mic icon with the camera icon. With the local url I had only the camera icon.
About the first pop up error, I still get it. I tried to “take control”, but I’m quite new to this and I don’t see what could be wrong. I saw the line you pasted, but I can’t understand if I need to change the ID somewhere to fix it. I’d post the code but I’m having a hard time to get how to do it properly, to not paste it here as plain text. I’ll try further tomorrow. I’ll let you know
I just copy pasted your code, replaced my browser- mod browser, visitor and camera fluent entities and it works good. I can see the video feed in the first popup without any error.
I would say it’s a problem with browser mod. Can you paste a screenshot of the Perform an action: Browser mod popup action’s top content? Where you select the browser.
I’m not really sure I understand what you’re telling me to do, but these are the screenshots of that part of the automation with some features selected and the code
That’s it! Now it’s fixed! Thank you…
Now I need to understand why I can’t hear on the camera when I press the green button. I’ll try again later, after fixing the first pop up
Hey all. Looks like everyone going well here regarding Browser Mod. Just FYI that 2.5.1 now will go to a full interaction mode on browser first refresh if the Browser is picky with interaction requirements, usually with playing audio automatically. This has surprised some users who this is likely not important. However for the use case here, it takes the last piece of guesswork out of the Browser blocking based on user interaction requirements.
The next most reported issue I see is networking (secure v non-secure) and CORS. Both usually addressed by paying particular attention to cloud and local URLs, and setting as manual if needed. Devices that stay local are usually easy to work out. I am not sure how the camera streams work in the mix, but you may need to add them as a CORS allowed URL if the stream comes directly from the camera.
CORS is Cross-Origin Resource Sharing. Basically it is a mechanism where the current server tells the Browser what is OK to load, apart from itself. In its simplest form, if you are Browsing at www.somewhere.com but a resource on the page uses the server IP address instead, unless the page’s CORS is set to allow all, or the IP address specifically, then the resource will be blocked.
Whether you need to use will be down to your network setup. Usually it will be the last thing needed to correct an issue, and more due to the unique nature of a setup. e.g. I use in my development environment. The Home Assistant documentation is HERE.
Browser Mod v2.5.2 released which makes the Full user interaction opt in. Too many users were impacted by the user interaction which is not required if you are not using popups with media. Anyhow if the 2.5.1 feature helped you then in 2.5.2 you will now need to set the Frontend setting to get the feature.
Nothing, it’s still not working.
Two things came to mind, I have integrated the doorbell via the recorder, so the ip I’m using is the recorder ip address. I thought that was not a problem, because changing the “01_sub” in other numbers “02_sub” etc. make me see every camera without issue. Now I have a doubt, can it be the reason why it’s not working?
Moreover, I added a user specifically for HA in the reolink app, when it was possible, and as user and password I’m using those credentials, should I be using the Admin credentials instead?
Lastly, now when the pop up comes out the audio keeps playing even after it’s closed. So I guess it has something to do with what @dcapslock was saying, but I didn’t understand what needs to be done to fix it
If you are able to see the stream in the second popup and you hear the audio but the microphone is not working it can be because of 2 things:
you are not using HTTPS
your go2rtc config is incorrect
If you can’t even see the video in the second popup, it’s definetly something between the doorbell or the recorder and go2rtc. I can’t help with that because I connect to the doorbell directly.
You can try to debug it using the go2rtc addon.
Open the web interface:
Click on the links anchor under the Commands column in your stream row
At the bottom of the page, you will see a section called “WebRTC Magic”. Select the video+audio+microphone option and you can test both local and exteral players opening the webrtc.html (for local) and copy link and paste it in another tab (for external).
If anything is not working, then the problem is in your go2rtc configuration. Because maybe as you mentioned you are using the RTSP stream from your recorder instead of the camera itself.
Do you think the I need to add them as CORS to make it works? And most of all, what is CORS?? 
