Thanks for the tips, Sebas!sebas wrote:For Dromotica I ran into the same problem with the external ip not being reached from the local network. I ended up implementing two server settings, one local and one remote. Based on the SSID of the Wifi network you're connected to I determine which setting to use. You'll have to add the name of the SSID of your local network in the local settings. I prefill this with the name of the SSID you're connected to when you edit this setting if this has not been set yet.patoo77 wrote:Is there really no other way? Maybe using a NOIP provider?bellissimo wrote:I would like to add another vote for having both 'Home' and 'Away' server settings. The app could detect if wifi was available and use the 'Home' server, or use the 'Away' server otherwise. If you could also manually switch between Home and Away, then this would cover all bases.
In order to be able to access domoticz using a DDNS from within your home network, then your router needs to have a 'NAT Loopback' feature available. Many routers do not have this option. For example, anyone in the UK who has Sky Broadband is forced to use a Sky provided router, which do not have this feature, and there is no straightforward way of getting round this without jumping through hundreds of hoops.
This makes the home and away settings critical for me.
I see how that can be problematic, but this is not something that should be handled in the client side. I am not even sure it's technically possible.
Might work with a combination of WIFI available + checking what WIFI SSID you're connected to... Seems like a hack more than anything else.
Anyone else has an idea?
It kinda sucks to handle it this way, but since many people are concerned, I will give it a look!
A manual button won't work since the app works in the background for location services. It needs to figure out the connection by itself.

Hopefully It won't be that long to implement.