Anybody else noticed Fully Kiosk REST commands LESS reliable on recent version?

A year or so ago, my REST commands were 100% reliable. Now, the command I use is often ignored by the tablet. The WiFi is stable. Any ideas??

screen_on: method: GET url: "http://192.168.0.x:2323//?cmd=screenOn&password=x"

I assume you’ve just copy/pasted this onto a single line from your config which should have each key on its own line with correct indentation:

screen_on:
  method: GET
  url: "http://192.168.0.x:2323//?cmd=screenOn&password=x"

As your connection is not https you could try adding the configuration variable: verify_ssl: false as this is true by default.

I’m not sure this would really make any difference, but as you’re not looking to return any data, you should probably use the POST method.

And you don’t need the double // before ?cmd, just one / will do - although again I tested this on my setup and found it made no difference.

What version of the Fully Kiosk Browser app are you running? We’re up to 1.52 now. Is Android System Webview up to date on the tablet? I’ve found this can sometimes make a difference.

You could try the core integration if you are not already using it - it creates a screen on/off button for you (amongst other things), although it also just uses the same REST api interface underneath, so again might not make an actual difference.

Finally, you could try playing around with the Power Settings within the FKB app on the tablet itself - it may be going to sleep and disconnecting - read the information under ‘Prevent from Sleep while Screen Off’ setting to see if it applies to your tablet.

Otherwise, I’m afraid I’ve no further suggestions.

yes, sorry, think the indentation got messed up during the copy/paste and I didn’t notice as was in a bit of a rush

I’ll check - I think actually now you mention it these problem probably started after I updated Android webview or Fully Kiosk. It was super reliable until a few months ago and that probably coincided with an update.

Thanks, I will