Loxone - Doorbird Integration

[Peter]

I recently upgraded to a Gen 2 compact MS and have set up 'remoteConnect' to access the MS (and CCTV cameras) remotely without the need for port forwarding. This works fine, except for my two Doorbird intercoms which are inaccessible via the Loxone app. 

Loxone support have made a few suggestions, which I'd already tried anyway, without success and as a non-Partner they've now disowned me.

I'm fairly certain this is something to do with Port numbers, but unsure how to proceed. The Doorbirds use Port 80 so possibly a conflict with the MS?

I can't imagine I'm the only user to experience this problem?

The alternative is to go back to port forwarding using Manual access and the 'clouddns' placeholder

[Peter]

Any ideas anyone? 

It seems I can revert to using manual external access & port forwarding (as I used to with the Gen 1 MS) however the Doorbirds and CCTV cameras now ask for login details before opening the video stream - something that didn't happen previously. I've tried including the login info within the URL but no success (the details are already included in the config Username / Password boxes anyway).

I've reverted to using 'remoteConnect' which works with the CCTV cameras but as before, not the Doorbirds.

This is driving me nuts!! Any ideas as to a solution would be hugely appreciated!

[Peter]

Bringing this back TTT, just in case anyone has a solution?

It would be helpful to try and understand how the MS resolves external access (remoteConnect) without the need to port forward.

[Jonathan Dixon]

On Sun, 9 Feb 2025, 17:50 Peter, <s69...@gmail.com> wrote:

Bringing this back TTT, just in case anyone has a solution?

It would be helpful to try and understand how the MS resolves external access (remoteConnect) without the need to port forward.

Essentially the miniserver makes an outbound connection to a Loxone cloud service. The app or browser also makes a connection to the same service. The server connects the two together, shunting encrypted data bidirectionally between the two.

It also has an ssh tunnel from miniserver to cloud for some reason 

https://www.loxone.com/wp-content/uploads/datasheets/Loxone_PortsDomains.pdf has a few terse details.

The alternative would have been STUN/ICE protocols to avoid the server in the middle of the data stream but is a lot more work and has much greater compatibility challenges. I don't think Loxone use it, but is commonly used for latency sensitive media streams like video conferencing software.

Sorry can't help with the underlying issue, I've never used Doorbird and there's too many variables to get a feel for what is going on without actually getting hands on with it. 

On Friday, January 24, 2025 at 3:54:23 PM UTC Peter wrote:

Any ideas anyone? 

It seems I can revert to using manual external access & port forwarding (as I used to with the Gen 1 MS) however the Doorbirds and CCTV cameras now ask for login details before opening the video stream - something that didn't happen previously. I've tried including the login info within the URL but no success (the details are already included in the config Username / Password boxes anyway).

I've reverted to using 'remoteConnect' which works with the CCTV cameras but as before, not the Doorbirds.

This is driving me nuts!! Any ideas as to a solution would be hugely appreciated!

On Tuesday, January 21, 2025 at 11:47:42 AM UTC Peter wrote:

I recently upgraded to a Gen 2 compact MS and have set up 'remoteConnect' to access the MS (and CCTV cameras) remotely without the need for port forwarding. This works fine, except for my two Doorbird intercoms which are inaccessible via the Loxone app. 

Loxone support have made a few suggestions, which I'd already tried anyway, without success and as a non-Partner they've now disowned me.

I'm fairly certain this is something to do with Port numbers, but unsure how to proceed. The Doorbirds use Port 80 so possibly a conflict with the MS?

I can't imagine I'm the only user to experience this problem?

The alternative is to go back to port forwarding using Manual access and the 'clouddns' placeholder

--
You received this message because you are subscribed to the Google Groups "Loxone English" group.
To unsubscribe from this group and stop receiving emails from it, send an email to loxone-englis...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/loxone-english/123b0830-f470-4d60-8f8b-4826b8c3c22fn%40googlegroups.com.

[Peter]

Thanks for the reply Jon. 

Out of curiosity what port settings are people using for the Miniserver setup? Whilst I previously used 7777 for my Gen 1 HTTP setting, currently I've got 80 for HTTP and 443 for HTTPs, both of which I believe should be changed to something more random.

Whilst searching the Loxforum for a solution to this problem, I found a post which stated using an external port of 8090 to Doorbirds' internal port of 80. Unfortunately I can't find that post now. And in any event that involves port forwarding on the router which remoteConnect doesn't require.

[Jonathan Dixon]

On Mon, 10 Feb 2025 at 10:51, Peter <s69...@gmail.com> wrote:

Thanks for the reply Jon. 

Out of curiosity what port settings are people using for the Miniserver setup? Whilst I previously used 7777 for my Gen 1 HTTP setting, currently I've got 80 for HTTP and 443 for HTTPs, both of which I believe should be changed to something more random.

The internal port doesn't matter so much - may as well keep with 80 and 443 for convenience. The external port when using port-forwarding can indeed be randomized like this to reduce public port-scanners finding it - this is just a layer of "security through obscurity" but has been useful to reduce noise in my SSL reverse proxy (and thus, I won't share my port numbers here lol). BUT it's only relevant when using port forwarding as you say.

 

Whilst searching the Loxforum for a solution to this problem, I found a post which stated using an external port of 8090 to Doorbirds' internal port of 80. Unfortunately I can't find that post now. And in any event that involves port forwarding on the router which remoteConnect doesn't require.

I agree with the conclusion, and FWIW this is sounding a bit like cargo-culting a solution 

Taking a step back, what is it that's not working - "Picture when ringing", "Video stream" or (2-way) Audio ?

Is it failing when connecting on the local network, externally, or both?

What are your Intercom block settings? are the external URL / hosts matching the port-forward you have configured to the doorbird?

 

To view this discussion visit https://groups.google.com/d/msgid/loxone-english/45982a56-1136-4dcb-89af-39779ab3a0ddn%40googlegroups.com.

[Peter]

Hi Jon

The following works fine:

Picture when ringing = http://'user':'password'@'IP address'/bha-api/image.cgi

URL video stream (Local) = http://'user':'password'@'IP address'/bha-api/video.cgi

This doesn't:

URL video stream (External) = http://remoteConnect:'port number'/bha-api/video.cgi

If I select the "A problem was detected" I get the following:

 http://'user':'password'@'IP address'/bha-api/video.cgi

If I change the http to https (which is what I think it should be) - still doesn't work. If I select the "A problem was detected" I get the following:

https://remoteConnect/proxy/'a stream of code'/bha-api/video.cgi

Username & Password for camera are both entered. I don't use Loxone for the audio

The external URL / hosts are matching the port-forward configured for the doorbirds - yes. Although arguably as port forwarding is not required this shouldn't be an issue?

Quite a lot of info there Jon, hope it all makes sense.

[Nick Barton-Wells]

Could you not create a VPN to connect into your home lan when on 4g/5g and test if that works?