Domoticz

sorry but I doubt any open source android developers are interested in buying a windows phone.. I think its safe to presume there are no plans for that.

After some feedback I just released a new version with a clearer unit of measurement on the geofence radius (it is in meters) and a extra button to get and enter the current gps location into the latitude and longitude fields.

When my wife is calling, the app thinks she is leaving the perimiter and the app sends a "leave" message. Do you know how this is possible and can you solve this?

ErwinH wrote:When my wife is calling, the app thinks she is leaving the perimiter and the app sends a "leave" message. Do you know how this is possible and can you solve this?

Not sure but maybe when she is calling, she gets 'assigned' to another gsm-tower and Google Play might think her location has changed. What you could try is to see in the location history ( https://maps.google.com/locationhistory/b/0 ) and see if it changes when she is calling. If not let me know and I will try to investigate further.

Don't work for me, not http, not https.
Testet JSON on google chrome on mobile, that works. Domoticz V2.4538

Can you try setting http ? Usually https is used with port 443 and http with 80 (or 8080)

Appesteijn wrote:Can you try setting http ? Usually https is used with port 443 and http with 80 (or 8080)

error on http also

Could you try with your server's internal ip (when your connected to your wifi) and then http + port 8080 and https + port 443 ?

Appesteijn wrote:Could you try with your server's internal ip (when your connected to your wifi) and then http + port 8080 and https + port 443 ?

https+443 giv the same error as in image 3 (just with https and 443 in text)

Ok I think I see what is going wrong, at your domoticz server under 'Settings', it should look like in the screenshot ("Basic-Auth"). Then http + 8080 should work. If you want httpS work you should forward a port (eg 8080) to internally 443.

Port used doesn't dictate protocol used.
One can run HTTPS fine on port 80 and HTTP on 443.
It just isn't what is specified by the standard...

True, but if you forward port external_ip:8080 to interal_ip:8080 it will not work with https, right? Domoticz https will listen (as default) on 443.

changed to Basic-Auth and now it works with http


(What is Basic-Auth btw?)

Basic auth is that your username and password are included in the message that is send to your server. If you go to your domoticz server with your browser you will get a different username/password pop-up.

Now you could try to forward the https port and use that one in the app. The port number is (on domoticz) 443.

Appesteijn wrote:True, but if you forward port external_ip:8080 to interal_ip:8080 it will not work with https, right? Domoticz https will listen (as default) on 443.

Yup, SSL/HTTPS will not work on 8080.

worked fine, but the last days it don't work anymore, it only send json if i manual klikk the send button in the app...
Any ideas?

Happend after a reboot of the phone.
(tryd have the app open in backround, don't work)

Evelen wrote:worked fine, but the last days it don't work anymore, it only send json if i manual klikk the send button in the app...
Any ideas?

Happend after a reboot of the phone.
(tryd have the app open in backround, don't work)

Try to remove the geofence and re-add it.

The app listens to a possible reboot of your phone and tries to add an existing geofence, but sometimes the Google client isn't ready yet.

Appesteijn wrote:

Evelen wrote:worked fine, but the last days it don't work anymore, it only send json if i manual klikk the send button in the app...
Any ideas?

Happend after a reboot of the phone.
(tryd have the app open in backround, don't work)

Try to remove the geofence and re-add it.

The app listens to a possible reboot of your phone and tries to add an existing geofence, but sometimes the Google client isn't ready yet.

Did not work
EDIT: Well, it sendt a "home" massange now, after 15min+ home...

after restarting your phone indoors it can take a while for your phone to get a GPS fix it knows is accurate..

Evelen wrote:
Try to remove the geofence and re-add it.

The app listens to a possible reboot of your phone and tries to add an existing geofence, but sometimes the Google client isn't ready yet.
Did not work
EDIT: Well, it sendt a "home" massange now, after 15min+ home...

If you use WiFi your phone should get a fix within a few minutes max. Do you live remotely? That might influence how fast you get a location fix.