Webremote sessions disconnecting

[Chad Gard]

On 2019-10-26 17:58, James Sentman wrote:

> Are you having these issues with the mobile web remote? Or the desktop version? There was a change in iOS a few versions back that completely hosed up how they were caching web pages. There was no way to "start over" a timed out connection to the web remote. It would just sit there at the "reload this page to restart" message but there was no reload button! I added a reload button to that error page as a response and it lets you reload the interface when it locks itself into this state.

It looks like I'm only having the problem with the web remote.   But it
doesn't matter if I'm using my iphone (iOS 13.1.3) or an the farm's cash
register (iOS 12.1.1 on an old iPad mini), or my laptop (Mojave), or the
xtension mini (High Serra).  Maybe it's a problem with safari,
regardless of OS, instead of iOS).  I don't intend to regularly use the
mobile web remote on a non iOS device.  It was just easier to set up the
user interface I wanted with a bigger screen. 

> There are other timeouts that I can adjust on the remotes. It's on my list to experiment with but there were problems with that in the past as well so I haven't found the energy to break other things by playing with that yet ;) Let me know which one is causing you the problem and I"ll see if I can adjust that. At some point in the future an entirely new web interface will replace this old one. I'm making good but slow progress in rebuilding it from scratch with better tools. It's just a "mature" product so there is a lot of stuff to rebuild ;) I expect few to none of the same issues will be a problem with the new version as I will be in control of everything. Which is good because I can fix bugs that I couldn't directly access with the old one, but also bad in that it's a lot more work for me to make anything happen at all.

I wouldn't want you to spend much time breaking the current one to fix a
problem that is quite tiny, in lieu of slowing down your good progress
on the new interface :).  The timeouts themselves are really not much of
a problem  at present.  It's more the logging that is irritating, as it
gets in the way of stuff I want to see as I implement a bunch of stuff
all at once (usually not a great idea). 

> For the logging, do you just mean that it shouldn't be logged in "red" so that it doesn't show up in the errors part of the log? I can change that easily enough. It might be worth while to add your own logging to the handlers for logging on and failure to log on and ignoring the rest.

It actually shows up in blue ;).  I can fairly easily add my own logging
on the log on/failure handlers, which is probably a good idea.  And, the
time outs could show up in the full log in black (or whatever).  it's
just that, because they're showing up as an exception, so they clutter
the exceptions and user log items display, which I typically want to
focus on. 

Thanks!

-- 
Chad

-What's Cookin' at the Farm?  Recipes, menus, and more at
http://twie.holeinthewoodsfarm.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20191026/420734ba/attachment.html>