Page 8 of 12

Re: Toon mobile access

Posted: Tue Nov 02, 2021 3:50 pm
by TheHogNL
Ron_nl wrote:I've noticed something strange since the last update.

I made some changes to lighttpd.conf to disable the login and saving them ofcourse and rebooted. (like I always do)
A few minutes later all my changes are being reversed, the time stamp of lighttpd.conf has also changed.

Are these files being "refreshed" continually since this last version?

Ron.
If the mobile app is updated from TSC the tsc scirpt updates it on your toon and then also replaces the lighttpd.conf. Probably that happened to you also just after the reboot.
If you keep a lighttpd.conf.orig file in the same location the .conf file wil never be replaced anymore.

Re: Toon mobile access

Posted: Tue Nov 02, 2021 4:56 pm
by Ron_nl
TheHogNL wrote:
Ron_nl wrote:I've noticed something strange since the last update.

I made some changes to lighttpd.conf to disable the login and saving them ofcourse and rebooted. (like I always do)
A few minutes later all my changes are being reversed, the time stamp of lighttpd.conf has also changed.

Are these files being "refreshed" continually since this last version?

Ron.
If the mobile app is updated from TSC the tsc scirpt updates it on your toon and then also replaces the lighttpd.conf. Probably that happened to you also just after the reboot.
If you keep a lighttpd.conf.orig file in the same location the .conf file wil never be replaced anymore.
Actually it was a pushed update.
I have the lighttpd.conf.orig at the same location and made the changes there too, but that didn't help. lighttpd.conf is changed back again.
I have also a custom logo.png, that is also changed back to the original.

Re: Toon mobile access

Posted: Tue Nov 02, 2021 7:23 pm
by TheHogNL
Ron_nl wrote:
TheHogNL wrote:
Ron_nl wrote:I've noticed something strange since the last update.

I made some changes to lighttpd.conf to disable the login and saving them ofcourse and rebooted. (like I always do)
A few minutes later all my changes are being reversed, the time stamp of lighttpd.conf has also changed.

Are these files being "refreshed" continually since this last version?

Ron.
If the mobile app is updated from TSC the tsc scirpt updates it on your toon and then also replaces the lighttpd.conf. Probably that happened to you also just after the reboot.
If you keep a lighttpd.conf.orig file in the same location the .conf file wil never be replaced anymore.
Actually it was a pushed update.
I have the lighttpd.conf.orig at the same location and made the changes there too, but that didn't help. lighttpd.conf is changed back again.
I have also a custom logo.png, that is also changed back to the original.
Yes a toon firmware update will revert it back also

Re: Toon mobile access

Posted: Tue Nov 02, 2021 8:37 pm
by Ron_nl
TheHogNL wrote: Yes a toon firmware update will revert it back also
It was only the mobile update which was pushed to the Toon (versie 1.0.24) . Not a firmware update.
And I have changed my lighttpd.conf for over 4 times now and it still changes it back. Same for the logo.png in the images dir.

Re: Toon mobile access

Posted: Tue Nov 02, 2021 11:50 pm
by oepi-loepi
Sorry, it was indeed an update of the /mobile app i did. It now also shows smoke detectors (if you have them).

What i simply do when i am testing or developing is that i do all in a different folder /mobile2. If you do you custom modifications you can copy the folder /mobile to /mobile2 and do your modifications there. This new folder will not be updated.

Re: Toon mobile access

Posted: Wed Nov 03, 2021 12:09 am
by Ron_nl
oepi-loepi wrote: What i simply do when i am testing or developing is that i do all in a different folder /mobile2. If you do you custom modifications you can copy the folder /mobile to /mobile2 and do your modifications there. This new folder will not be updated.
Ok, that is a good idea. 8)
But what do I have to do to protect my lighttpd.conf?
Or is it possible to add a toggle switch to switch off the login in a next version?

Re: Toon mobile access

Posted: Wed Nov 03, 2021 2:49 pm
by Ron_nl
Ron_nl wrote:
oepi-loepi wrote: What i simply do when i am testing or developing is that i do all in a different folder /mobile2. If you do you custom modifications you can copy the folder /mobile to /mobile2 and do your modifications there. This new folder will not be updated.
Ok, that is a good idea. 8)
But what do I have to do to protect my lighttpd.conf?
Or is it possible to add a toggle switch to switch off the login in a next version?
Correct me if I'm wrong, but my guess is the files are checked remotely for deviations and the original file(s) are pushed back to the Toon again.
Something which never happened before in previous versions..

Re: Toon mobile access

Posted: Wed Nov 03, 2021 4:25 pm
by Toonz
Ron_nl wrote:Correct me if I'm wrong, but my guess is the files are checked remotely for deviations and the original file(s) are pushed back to the Toon again.
Something which never happened before in previous versions..
It always happened when the ../mobile website was updated (including lighttpd.conf).
It might has been less visible as we didn't have much developments going on for quite some time.
Just recently we had a lot of activity with adding additional devices to the website (smoke detectors).

Re: Toon mobile access

Posted: Wed Nov 03, 2021 7:05 pm
by oepi-loepi
you can also change your local version to 99.99.99 in version.txt . Nothing will be updated unless we get to that version also.

Re: Toon mobile access

Posted: Wed Nov 03, 2021 11:08 pm
by Ron_nl
oepi-loepi wrote:you can also change your local version to 99.99.99 in version.txt . Nothing will be updated unless we get to that version also.
Tried this option, but still within about 10 minutes lighttpd.conf is changed back to the original file.
Also just tried the same with my spare Toon 1, and the same happens here.

Re: Toon mobile access

Posted: Thu Nov 04, 2021 8:34 am
by oepi-loepi
Also when you increase the version in the origina /HCBv2/www/mobile/version.txt ? This is the file checked and emits replacements if there is a new version available.

Re: Toon mobile access

Posted: Thu Nov 04, 2021 11:00 am
by Ron_nl
oepi-loepi wrote:Also when you increase the version in the origina /HCBv2/www/mobile/version.txt ? This is the file checked and emits replacements if there is a new version available.
Yes, and to make it even more exciting within 10 minutes it is changed also back to version 1.0.24
So something happened between this and the previous version.

Re: Toon mobile access

Posted: Thu Nov 04, 2021 11:42 am
by TheHogNL
Ron_nl wrote:
oepi-loepi wrote:Also when you increase the version in the origina /HCBv2/www/mobile/version.txt ? This is the file checked and emits replacements if there is a new version available.
Yes, and to make it even more exciting within 10 minutes it is changed also back to version 1.0.24
So something happened between this and the previous version.
Can you post the /var/log/tsc log file?

Re: Toon mobile access

Posted: Thu Nov 04, 2021 11:43 am
by TheHogNL
oepi-loepi wrote:you can also change your local version to 99.99.99 in version.txt . Nothing will be updated unless we get to that version also.
This is not the case I am afraid. It only checks if it is different.

Re: Toon mobile access

Posted: Thu Nov 04, 2021 12:52 pm
by Ron_nl
TheHogNL wrote: Can you post the /var/log/tsc log file?
Starting TSC support script (version 2.58)
04/11/2021 09:52:08 Running 5.33.9 on a nxt
04/11/2021 09:52:08 Allowing SSH in firewall rules INPUT table
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 2: parse error
sh: invalid number ''
sh: invalid number ''
04/11/2021 09:56:59 Checking for updates
04/11/2021 09:57:00 Running 5.33.9 on a nxt
04/11/2021 09:57:01 New version of Toon Mobile Web app found (1.0.24), installing...
04/11/2021 09:57:03 Installed toon mobile web app...
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 2: parse error
sh: invalid number ''
sh: invalid number ''
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 1: parse error
(standard_in) 2: parse error
sh: invalid number ''
sh: invalid number ''