Page 1 of 1
Dashboard fails after upgrade to builds 3190, 3190a & 3191
Posted: Wed 06 Jul 2022 5:22 pm
by kaygee
Hi all,
After upgrading to builds 3190, 3190a or 3191 my dashboard fails, I cannot access it at all. I get the message "This site can't be reached" in Chromium and the message "ERR_CONNECTION_REFUSED".
This happens on localhost and the same if I use the explicit IP address. I have to revert back to build 3184 and all is fine again.
Any idea what may be causing this issue?
If you want diags, let me know but all seems to be OK in the console log and in the system log.
Thanks in advance.
Re: Dashboard fails after upgrade to builds 3190, 3190a & 3191
Posted: Thu 07 Jul 2022 7:48 am
by HansR
I guess the log would be of use. Switch debug and data logging on, restart, wait ten minutes and post it.
Re: Dashboard fails after upgrade to builds 3190, 3190a & 3191
Posted: Mon 11 Jul 2022 10:20 am
by Tigro11
Hello, I don't know if I'm in the right section,
I just wanted to ask how I have to set Cumulus MX to get the data in memory once you have run out of my Davis Vancege Pro2 station.
Thank you
Re: Dashboard fails after upgrade to builds 3190, 3190a & 3191
Posted: Mon 11 Jul 2022 11:17 am
by HansR
You could have started a new topic as it seems to be much different from the subject of this thread.
Having said that: could you elaborate a bit more precise of what it is that you want or what goes wrong?
Could you post the logfile (with debug and data on for some 10 minutes)?
Re: Dashboard fails after upgrade to builds 3190, 3190a & 3191
Posted: Mon 11 Jul 2022 12:24 pm
by Tigro11
Sorry again, nothing goes wrong, only that Davis's memory is not emptied once the data is downloaded.
I have to start WeatHerlink in order to delete Davis's memory.
I wanted to use Cumulus MX to empty memory.
Re: Dashboard fails after upgrade to builds 3190, 3190a & 3191
Posted: Mon 11 Jul 2022 12:31 pm
by mcrossley
@Tigro11...
The Davis logger memory does not "fill" as such, it is what is called a circular buffer. When it reaches the last available memory location it just starts back at the beginning, overwriting the oldest record.
There is no need to "clear" the logger memory - indeed the only way of doing so that I know of is to change the logging interval to a different value and then change it back again.
As far as I know, the WeatherLink software does not "delete" the memory either, all you are doing is updating the record the WeatherLink software has of the last data it read from the logger memory. This of course will not be changed by Cumulus, only when you run the Davis software.
Re: Dashboard fails after upgrade to builds 3190, 3190a & 3191
Posted: Mon 11 Jul 2022 12:39 pm
by Tigro11
Then I think I have a problem with WiFi Logger 2, every about 2-3 weeks I have to erase the memory of the Davis, athtiments both the wind speed and the rain stop working.
I try to see if I find another method
Re: Dashboard fails after upgrade to builds 3190, 3190a & 3191
Posted: Mon 11 Jul 2022 1:30 pm
by PaulMy
As Hans indicated, would be better if Tiggro11 posted this in a new thread on the "both the wind speed and the rain stop working"...
mcrossley wrote:
There is no need to "clear" the logger memory - indeed the only way of doing so that I know of is to change the logging interval to a different value and then change it back again.
And the simplest way to do that is by CumulusMX Station settings > Davis Advanced Options - Logger interval
Code: Select all
Set the Davis Logger interval to match Cumulus MX interval
[i]WARNING: This will clear all data from your logger if it is invoked.
If the Davis logger interval does not match the Cumulus interval, set it to match.
Requires a restart of Cumulus MX[/i]
Tiggro11 wrote:
Then I think I have a problem with WiFi Logger 2, every about 2-3 weeks I have to erase the memory of the Davis, athtiments both the wind speed and the rain stop working.
I try to see if I find another method
As Mark mentioned you shouldn't need to do that, but WiFiLogger also allows you to change the logger archive interval, which then also deletes the logger memory. From WiFiLogger settings:
Code: Select all
Setting new archive interval will automatically erase whole memory.
Do it?
Enjoy,
Paul