Page 1 of 1

Settings >> others >> dzVents debugging (3.8072)

Posted: Thursday 13 July 2017 6:05
by jkimmel
Can't change debugging to any other then silent.
after changing and storing debugging is back to silent

Re: Settings >> others >> dzVents debugging (3.8072)

Posted: Thursday 13 July 2017 7:14
by dannybloe
Perhaps clearing your browser cache helps. Does changing other settings work?

Re: Settings >> others >> dzVents debugging (3.8072)

Posted: Thursday 13 July 2017 11:13
by jkimmel
Clearing browser cache did not help.
Can change other settings except both dzVents settings.

Re: Settings >> others >> dzVents debugging (3.8072)

Posted: Thursday 13 July 2017 11:21
by dannybloe
Which browser are you using?

Re: Settings >> others >> dzVents debugging (3.8072)

Posted: Thursday 13 July 2017 17:46
by jkimmel
I'm using Chrome Version 59.0.3071.115 (Offizieller Build) (64-Bit)

MS Edge is working

Re: Settings >> others >> dzVents debugging (3.8072)

Posted: Sunday 16 July 2017 21:21
by dlefol
Hello,

i have the same problem, but it seems to me that the log level change based on what I have selected in the web interface. However the web interface always display silent as log level. Could it be a problem of displaying the right information in the web interface ?

refreshing the page / clearing the cache does not help for me either.

Re: Settings >> others >> dzVents debugging (3.8072)

Posted: Monday 17 July 2017 8:33
by dannybloe
Ok, I do think it is a cache issue. Clearing the cache doesn't always work as expected. What does work for me (in Chrome that is) is this:

Open the console (F12 on Windows, alt-cmd-j on Mac, or any other way that works). Select the network tab in the dev panel and then go to the settings page in Domoticz (or reload the page if it was already there). Then in the list you should see setup.html and SetupController.js. Right click on each of those and select Clear Browser Cache. Then reload the page. Always worked for me.

Re: Settings >> others >> dzVents debugging (3.8072)

Posted: Friday 21 July 2017 20:10
by BakSeeDaa
FWIW I tried Domoticz 3.8102 today and had the same problem on Chrome on Ubuntu 16.04. Nor Emptying the cache or following the suggestion mentioned by dannybloe did any difference. Switching to Firefox solved the problem but FF was prune to get stuck in "script timeout errors" It wasn't my day really.