Kiosk Home iOS App

[norcoscia]

I tried with and without the comma, and I tried using your exact code, but other than that, it generates the same error on that line.

Here is the error snippet. Line 3 just has the close bracket...no extra hidden characters.

Code: Select all

Web Server Warning              Error when loading the secrets.json file. No secrets in that file will be validated until you correct the error.
Traceback (most recent call last):
  File "plugin.py", line 557, in startup
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/json/__init__.py", line 293, in load
    return loads(fp.read(),
           ^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 3 column 1 (char 23)

[DaveL17]

It sounds to me like something isn't right with the secrets file. Please make sure that you're using a plain text editor to save the file and that it doesn't include smart quotes or other special (sometimes hidden) characters.

[norcoscia]

That was my initial thinking too, but it is just a plain text file and I looked for hidden characters using BBedit.

[DaveL17]

I haven't been able to find a combination that generates your specific error message. For giggles, replace your secret key with something super simple like "aaa" and then restart the server and see if that clears the error. You may have stumbled on a character that the server doesn't like in the key you're trying.

[norcoscia]

I retyped the file from scratch using BBedit this time, but also used a simple string for the secret key (my previous tests were also simple though, with no special characters).

The original error seems to be resolved (it loaded the secrets.json file successfully), but Indigo is now reporting an XML parse error and failed authentication when the Kiosk client is requesting access.

Code: Select all

Client authentication failed - bad XML received from x.x.x.x (x.x.x.x)
   Client disconnected (x.x.x.x)
   Error                           XML Parse Error: syntax error
   Error                           In client packet stream
   Error                           On character 0 of line number 1.
   Error                           XML Parse Error: syntax error
   Error                           In client packet stream
   Error                           On character 0 of line number 1.
   Error                           XML Parse Error: syntax error
   Error                           In client packet stream
   Error                           On character 0 of line number 1.
   Error                           XML Parse Error: syntax error
   Error                           In client packet stream
   Error                           On character 0 of line number 1.
   Error                           XML Parse Error: syntax error
   Error                           In client packet stream
   Error                           On character 0 of line number 1.
   Error                           XML Parse Error: syntax error
   Error                           In client packet stream
   Error                           On character 0 of line number 1.
   Error                           XML Parse Error: syntax error
   Error                           In client packet stream
   Error                           On character 0 of line number 1.
   Error                           socket client key does not exist

[GlennNZ]

Is there any way to stop any form of scaling?

I have a couple of older iPad Pros wall mounted in the house. I have 2 different control pages that are setup for them that are the correct size width, and then allow scrolling down the page for further options. I'd like it if possible to be set so that 2 finger zoom wouldn't work, so you can scroll up and down the page as normal but not make anything bigger or smaller.

Also would it be possible to get it to automatically return to the top of the page after inactivity of X time?

Try Version 1.8 - pending Store release now.

Changes:

1.8

Change Screen Scaling to a menu - may need to be reselected if not Default- Default, useAlternative, and FitPageWidth.

Stop screen from moving sideways if pulled, remove bounce - fix screen as much as possible

Add Disable Zoom Setting for all scalings

Add FitPageWidth mode - fixes screen x dimension, allows bigger screen in the Vertical dimension to scroll down to. useAlternative still works fine in this mode just resizing background image to fit space. FitPageWidth is more inkeeping with CP editor view.

Redo the Settings Screen (Adds Screen Scaling Setting Default, Alternatve, FitPageWidth). Remove the unneeded toggle settings.

Adds a timer to check every 120 seconds after screen touch, will reset Zoom of screen (incase manually zoomed) and screen position, resetting to 0,0 - 120 seconds after last touch

Skips authenication pop up if for Indigo Server IP address (occasionally would appear if VPN turn on ) (Should not appear if API Key or Local Secret entered correctly(** Yet to be fully tested, as rare event)

Adds version number to Splash Screen


Sent from my iPad using Tapatalk

[DaveL17]

The original error seems to be resolved (it loaded the secrets.json file successfully), but Indigo is now reporting an XML parse error and failed authentication when the Kiosk client is requesting access.

OK, that's progress. I'm not sure how to make Kiosk Home reload credentials when you change the secret key (you did remember to change the secret key in the app as well).

[DaveL17]

@Glenn

Whenever I initially load the app, it loads the screen at minimum brightness--regardless of what I have the dim variable set to (or if I have the dim variable field left blank). If I then manually change the dim variable value, the app takes on that level of brightness. I have default screen brightness set to mid range in the app settings, and all other dim settings are default.

iPhone 16 Pro Max and iOS 18.2.

[norcoscia]

Yes, we changed the credentials inside the IOS settings page, and then restarted the Kiosk app (v1.7).

Also to note that this was on an iPad running 18.2, but we have also just tried it on another iPad running 17.7.3 and it didn't work there either.

The original error seems to be resolved (it loaded the secrets.json file successfully), but Indigo is now reporting an XML parse error and failed authentication when the Kiosk client is requesting access.

OK, that's progress. I'm not sure how to make Kiosk Home reload credentials when you change the secret key (you did remember to change the secret key in the app as well).

[GlennNZ]

@Glenn

Whenever I initially load the app, it loads the screen at minimum brightness--regardless of what I have the dim variable set to (or if I have the dim variable field left blank). If I then manually change the dim variable value, the app takes on that level of brightness. I have default screen brightness set to mid range in the app settings, and all other dim settings are default.

iPhone 16 Pro Max and iOS 18.2.

Hi @DaveL17

Probably you have Dim the Screen at a certain time set - and it is within that time period? If that is the case then is pretty much expected behaviour, and can’t think of any reason it might otherwise do that.

On startup and every 2 minutes or so - it checks to see whether now in a dim time.

Thats the Start Off Start time, and Screen On Start Time - time settings ..

(On another note - probably need a Forum directory here - which I can’t make Thanks Matt/Jay)

[DaveL17]

Probably you have Dim the Screen at a certain time set - and it is within that time period? If that is the case then is pretty much expected behaviour, and can’t think of any reason it might otherwise do that.

Yes, there were values in those fields (as default). I'd recommend setting those fields to null as default.

Cheers!

[GlennNZ]

Probably you have Dim the Screen at a certain time set - and it is within that time period? If that is the case then is pretty much expected behaviour, and can’t think of any reason it might otherwise do that.

Yes, there were values in those fields (as default). I'd recommend setting those fields to null as default.

Cheers!

Hi Dave!

You should be fast asleep - no screen time 3 hours before bedtime - isn’t that the rule??

Also probably need to mock up a iphone sized Demo - the online demo screen isn’t designed at all for iphone sized screens.

Sent from my iPad using Tapatalk

[DaveL17]

LOL. It's 15:00 where I am (although I just did wake up from a nap.....)

[GlennNZ]

LOL. It's 15:00 where I am (although I just did wake up from a nap.....)

Hmmm… I’ll definitely check the defaults - I thought defaulted to 23:00 Off, and 06:00 On…. But will check and update..

Hard to time those nap lengths … to long…horrible… to short … horrible… need to be just right…


Sent from my iPad using Tapatalk

[DaveL17]

I thought defaulted to 23:00 Off, and 06:00 On….

Yes that was the default (and it was dimming) I emptied the fields and now it loads at default dim.