Attempting to save Geofence locks DomoticsPad

duanel
Posts: 23
Joined: Mon Apr 09, 2012 8:23 pm

Attempting to save Geofence locks DomoticsPad

Post by duanel »

Lat and long are populated automatically and after entering a name and radius, I click the checkmark to save the geofence. The cursor stops blinking and application becomes unresponsive EXCEPT the keyboard will allow me to continue typing on the last edited field (if I haven't closed the on-screen keyboard) and the UI starts responding again.. However, whenever I attempt to save the geofence, the app locks up again.

I'm using a Galaxy S22 Ultra that is paired with the plugin. Status updates are enabled. Location permissions are allowed when using the app and I don't have an option to enable them all of the time. I've noticed that the latitude, longitude and locationFixTime are all blank values in indigo.
duanel
Posts: 23
Joined: Mon Apr 09, 2012 8:23 pm

Re: Attempting to save Geofence locks DomoticsPad

Post by duanel »

I'm also seeing errors for "undefined page for request /AndroidClientHelper/getDeviceHistory from 192.168.0.***" in the logs after attempting to view device history in the Android app. Lastly, device history is showing "The Domotics Pad Mobile Client plugin is missing or mis-configured on the server". I've confirmed that AndroidClientHelper is in the Web Assets/plugins/ directory.
User avatar
RogueProeliator
Posts: 2538
Joined: Tue Nov 13, 2012 3:54 pm
Location: Baton Rouge, LA

Re: Attempting to save Geofence locks DomoticsPad

Post by RogueProeliator »

I'm also seeing errors for "undefined page for request /AndroidClientHelper/getDeviceHistory from 192.168.0.***" in the logs after attempting to view device history in the Android app. Lastly, device history is showing "The Domotics Pad Mobile Client plugin is missing or mis-configured on the server". I've confirmed that AndroidClientHelper is in the Web Assets/plugins/ directory.
That sounds like either using an older version of Domotics Pad with a newer Indigo installation or the newest Domotics Pad with an older version of Indigo. Neither scenario will really work as there were some changes to Indigo that required equivalent changes to the application.

What versions are you running? I need to check the published version of Domotics Pad too now that I think about it, but let's start with your current versions.
duanel
Posts: 23
Joined: Mon Apr 09, 2012 8:23 pm

Re: Attempting to save Geofence locks DomoticsPad

Post by duanel »

Happy New Year!

Thanks for your help. I'm using Indigo 2023.1.1, Domotics pad clients 2023.11.0(ish) and Domotics Pad v2.0.0.
Indigo version
Indigo version
Screenshot 2024-01-03 at 5.19.25 PM.png (198.85 KiB) Viewed 4814 times
Domotics Pad Clients version
Domotics Pad Clients version
Screenshot 2024-01-03 at 5.19.11 PM.png (62.35 KiB) Viewed 4814 times
Domotics Pad version
Domotics Pad version
Screenshot_20240103_172107_Domotics Pad Medium.jpg (37.58 KiB) Viewed 4814 times
duanel
Posts: 23
Joined: Mon Apr 09, 2012 8:23 pm

Re: Attempting to save Geofence locks DomoticsPad

Post by duanel »

For what it's worth, I'm still having the same issue. Whenever I load a page in the Domotics Pad, I see this undefined page request for an API call:

Web Server Warning undefined page for request /api/webhook/7b5029ca101a58f4266978962e8ee4c4686633c196ce470bf4b73df6f8ae5f43 from {client IP address}

I'm using version 2.0.0 Ultimate Edition of Domotics Pad and v2024.3.0 released on March 17, 2024 of the Domotics Pad Mobile Client.
Sofabutt
Posts: 15
Joined: Mon Feb 12, 2018 2:46 pm

Re: Attempting to save Geofence locks DomoticsPad

Post by Sofabutt »

I've been trying to add a geofence for the past two days. When I clcik on the checkmark the app wigs out, the keyboard blinks and after about 30 seconds the app exits back tot he Android main screen. I am using thelatest Android app and plugin. Anyone have any ideas what the problem is?

I have experienced the same issues before, years ago, and I forgot what the fix was.
User avatar
RogueProeliator
Posts: 2538
Joined: Tue Nov 13, 2012 3:54 pm
Location: Baton Rouge, LA

Re: Attempting to save Geofence locks DomoticsPad

Post by RogueProeliator »

Can you double check that Domotics Pad has location permission? And are you using the latest in the App Store or the apk build I posted in here that has the latest libraries? I can dig around and find it if you aren't to try.
Sofabutt
Posts: 15
Joined: Mon Feb 12, 2018 2:46 pm

Re: Attempting to save Geofence locks DomoticsPad

Post by Sofabutt »

I have enabled all permissions. I re-installed the app from the Store (version 2.0.0). I cleared the app cache and data and re-entered the server settings.

I am using a ZFold 5 with OS 14 and One UI 6.1, Indigo version 2023.2.0 and Domotics Pad version 2024.3.0

Thanks for your help in looking in to this.
Sofabutt
Posts: 15
Joined: Mon Feb 12, 2018 2:46 pm

Re: Attempting to save Geofence locks DomoticsPad

Post by Sofabutt »

I've IMed the author of this plugin a few weeks ago and have not heard back.

I was able to restore the old geofences I had running by moving data from my old cellphone to the current cellphone, but the geofences still don't work, and the app still locks up when trying to activate the already activated geofences.

All but the Camera permission is enabled. I am using the current version of Indigo as well as the plugin.

Does anyone have any other ideas that might help?
duanel
Posts: 23
Joined: Mon Apr 09, 2012 8:23 pm

Re: Attempting to save Geofence locks DomoticsPad

Post by duanel »

I've been having this issue for nearly 2 years. This may be due to Samsung not allowing location permission access all of the time, but I've tried just about everything. You may also note that the lat and long are never populated in the device data in DomoticsPad or in Indigo.

The undefined page request I posted about in this thread on Jul 8 may have been due to some settings cached somewhere that I can't change. The extra logging showed that DomoPad was trying to use a custom port for Indigo that I stopped using months ago. When I changed my Indigo config to use the custom port again, the error went away.
Post Reply

Return to “DomoPad Android Client”