Can't change debugging to any other then silent.
after changing and storing debugging is back to silent
Settings >> others >> dzVents debugging (3.8072)
Moderator: leecollings
-
jkimmel
- Posts: 129
- Joined: Monday 25 November 2013 17:51
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2021.1
- Location: Mallorca
- Contact:
Settings >> others >> dzVents debugging (3.8072)
Rfxcom
Raspi 4
Raspi 4
-
dannybloe
- Posts: 1355
- Joined: Friday 29 August 2014 11:26
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Ermelo
- Contact:
Re: Settings >> others >> dzVents debugging (3.8072)
Perhaps clearing your browser cache helps. Does changing other settings work?
Creator dzVents - RPi3, loads of zwave devices, esp8266, evohome.
-
jkimmel
- Posts: 129
- Joined: Monday 25 November 2013 17:51
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2021.1
- Location: Mallorca
- Contact:
Re: Settings >> others >> dzVents debugging (3.8072)
Clearing browser cache did not help.
Can change other settings except both dzVents settings.
Can change other settings except both dzVents settings.
Rfxcom
Raspi 4
Raspi 4
-
dannybloe
- Posts: 1355
- Joined: Friday 29 August 2014 11:26
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Ermelo
- Contact:
Re: Settings >> others >> dzVents debugging (3.8072)
Which browser are you using?
Creator dzVents - RPi3, loads of zwave devices, esp8266, evohome.
-
jkimmel
- Posts: 129
- Joined: Monday 25 November 2013 17:51
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2021.1
- Location: Mallorca
- Contact:
Re: Settings >> others >> dzVents debugging (3.8072)
I'm using Chrome Version 59.0.3071.115 (Offizieller Build) (64-Bit)
MS Edge is working
MS Edge is working
Rfxcom
Raspi 4
Raspi 4
-
dlefol
- Posts: 35
- Joined: Monday 21 December 2015 16:35
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Settings >> others >> dzVents debugging (3.8072)
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.
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.
-
dannybloe
- Posts: 1355
- Joined: Friday 29 August 2014 11:26
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Ermelo
- Contact:
Re: Settings >> others >> dzVents debugging (3.8072)
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.
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.
- Attachments
-
- Screen Shot 2017-07-17 at 08.29.02.png (126.67 KiB) Viewed 1449 times
Creator dzVents - RPi3, loads of zwave devices, esp8266, evohome.
-
BakSeeDaa
- Posts: 485
- Joined: Thursday 17 September 2015 10:13
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
Re: Settings >> others >> dzVents debugging (3.8072)
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.
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 1 guest