Cumulus Support

I just upgraded to 3141 and received this message .

Cumulus MX v.3.12.0 build 3141
Working Dir: C:\Program Files (x86)\Wetter\CumulusMX\

Cumulus running at: http://localhost:8998/
http://192.168.2.20:8998/

Open the admin interface by entering one of the above URLs into a web browser.

Today.ini = data\today.ini
Last update=2021-08-04T18:08:00
Connected to station
Failed to discover any AirLink devices
04.08.2021 18:11:14
Type Ctrl-C to terminate
Downloading Archive Data
Downloading Archive Data
Missing AirLink WeatherLink API key/secret in the cumulus.ini file
Connecting real time FTP
Normal running
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei CumulusMX.MqttPublisher.UpdateMQTTfeed(String feedType)
bei CumulusMX.DavisStation.GetAndProcessLoopData(Int32 number)
bei CumulusMX.DavisStation.Start()
bei System.Threading.ThreadHelper.ThreadStart_Context(Object state)
bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
bei System.Threading.ThreadHelper.ThreadStart()
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Press Enter to terminate

Any ideas?

Many thanks
Jochen

jrichert wrote: ↑Wed 04 Aug 2021 6:21 pmMissing AirLink WeatherLink API key/secret in the cumulus.ini file

This?

Have you converted your MQTT template file to the new format as per the instructions?

If so, perhaps post it here so I can take a look?

Meantime, I'll add a catch for MQTT template errors.

No, I have not. Where is that written?
Do you mean this section?
- Change: MQTT now allows multiple topics for both Update and Interval data.
- The format of the MQTT template files has changed to accommodate this
- The template must now be formatted as JSON, however the payload data for each topic can still be in whatever format you like so long as you construct
a valid string - i.e. escape quotation marks
- The default interval template (the update template is similar) now looks like this...
{"topics": [
{
"topic": "CumulusMX/Interval",
"data": "{\"time\":\"<#timehhmmss>\",\"temp\":<#temp rc=y>,\"humidity\":<#hum>,\"wgust\":<#wgust rc=y>}",
"retain": false
}
]}
Where the topic name is "CumulusMX/Interval", and the payload is the string "{\"time\":\"<#timehhmmss>\",\"te...rc=y>}" which is formatted as JSON text
- To create a template with multiple topics, use this format...
{"topics": [
{"topic": "MyName/Topic1", "data": "\"<#timehhmmss>\",<#temp rc=y>", "retain": false},
{"topic": "MyName/Topic2", "data": "<data><humidity><val><#hum></val></humidity></data>", "retain": true}
]}
Where Topic1 is formatted as CSV and is not retained on the server, and Topic2 as XML and is retained
- The Dashboard Internet > MQTT settings have been updated to reflect these changes

I do not understand what exactly to do. There is no new example file in the mqtt folder.
Which files should be updated? DataUpdate.txt and Interval.txt?
Should that file be named in .txt or .xml?

Many thanks for your help.
Jochen

jrichert wrote: ↑Wed 04 Aug 2021 9:34 pm No, I have not. Where is that written?
Do you mean this section?
- Change: MQTT now allows multiple topics for both Update and Interval data.
- The format of the MQTT template files has changed to accommodate this
- The template must now be formatted as JSON, however the payload data for each topic can still be in whatever format you like so long as you construct
a valid string - i.e. escape quotation marks
- The default interval template (the update template is similar) now looks like this...
{"topics": [
{
"topic": "CumulusMX/Interval",
"data": "{\"time\":\"<#timehhmmss>\",\"temp\":<#temp rc=y>,\"humidity\":<#hum>,\"wgust\":<#wgust rc=y>}",
"retain": false
}
]}
Where the topic name is "CumulusMX/Interval", and the payload is the string "{\"time\":\"<#timehhmmss>\",\"te...rc=y>}" which is formatted as JSON text
- To create a template with multiple topics, use this format...
{"topics": [
{"topic": "MyName/Topic1", "data": "\"<#timehhmmss>\",<#temp rc=y>", "retain": false},
{"topic": "MyName/Topic2", "data": "<data><humidity><val><#hum></val></humidity></data>", "retain": true}
]}
Where Topic1 is formatted as CSV and is not retained on the server, and Topic2 as XML and is retained
- The Dashboard Internet > MQTT settings have been updated to reflect these changes

Yes.

jrichert wrote: ↑Wed 04 Aug 2021 9:34 pm I do not understand what exactly to do. There is no new example file in the mqtt folder.

The text above gives examples of the new JSON format (now badly formatted).

The /mqtt folder *does* contain example templates for both Interval and Data Update.
The filenames are "DataUpdateTemplate.txt" and "IntervalUpdate.txt".

jrichert wrote: ↑Wed 04 Aug 2021 9:34 pm Which files should be updated? DataUpdate.txt and Interval.txt?
Should that file be named in .txt or .xml?

The default files in the /mqtt folder are the default names used by Cumulus MX. But you can name them whatever you want so long as you change the configuration under Internet Settings | MQTT.

It seems, I managed it myself Copied it 1:1 from the readme and added my data section.

Now I have only these two error messages:
Failed to discover any Airlink devices and
Missing Airlink Weather API key/secret....

I am using a Weatherduino AQM III, which is compatible to Davis Airlink.
https://www.meteocercal.info/forum/Thre ... I-Overview

They wrote:
On CumulusMX go to Air Quality settings, add AirLink as Air Quality sensor.
On the AirLink config, just fill the IP address of your AQM III device. Left everything else blank.


BTW AQ data is seen in cumulus...

Jochen

jrichert wrote: ↑Wed 04 Aug 2021 9:53 pm Now I have only these two error messages:
Failed to discover any Airlink devices and
Missing Airlink Weather API key/secret....

Yeah that's normal for a direct IP Airlink config.
Would good to see that message suppressed if possible when an Airlink is configured as IP standalone & not being associated with WeatherLink.

Next Problem....

Error opening serial port - not enough system resources to run the service...
2021-08-04 22:14:05.939 Starting on Windows
2021-08-04 22:14:05.943 Running interactively
2021-08-04 22:14:05.945 Creating Windows Exit Handler
2021-08-04 22:14:06.133 Creating main MX log file - MXdiags\20210804-221406.txt
2021-08-04 22:14:06.137 Cumulus MX v.3.12.0 build 3141
2021-08-04 22:14:06.137 Working Dir: C:\Program Files (x86)\Wetter\CumulusMX\
2021-08-04 22:14:08.248 http://192.168.2.20:8998/
2021-08-04 22:14:08.249 Open the admin interface by entering one of the above URLs into a web browser.
2021-08-04 22:14:08.278 Today.ini = data\today.ini
2021-08-04 22:14:08.283 Last update=2021-08-04T21:28:00
2021-08-04 22:14:10.208 Connected to station
2021-08-04 22:14:13.393 Failed to discover any AirLink devices
2021-08-04 22:14:20.478 Missing AirLink WeatherLink API key/secret in the cumulus.ini file
2021-08-04 22:14:20.480 Connecting real time FTP
2021-08-04 22:14:20.969 Normal running
2021-08-04 23:03:32.909 Error opening serial port - Nicht genügend Systemressourcen, um den angeforderten Dienst auszuführen.

2021-08-04 23:03:32.909 Will retry in 30 seconds...
2021-08-04 23:54:32.709 Error opening serial port - Nicht genügend Systemressourcen, um den angeforderten Dienst auszuführen.

2021-08-04 23:54:32.709 Will retry in 30 seconds...
2021-08-05 00:45:45.679 Error opening serial port - Nicht genügend Systemressourcen, um den angeforderten Dienst auszuführen.

2021-08-05 00:45:45.679 Will retry in 30 seconds...
2021-08-05 01:36:48.476 Error opening serial port - Nicht genügend Systemressourcen, um den angeforderten Dienst auszuführen.

2021-08-05 01:36:48.476 Will retry in 30 seconds...
2021-08-05 02:27:49.898 Error opening serial port - Nicht genügend Systemressourcen, um den angeforderten Dienst auszuführen.

2021-08-05 02:27:49.898 Will retry in 30 seconds...
2021-08-05 03:18:53.837 Error opening serial port - Nicht genügend Systemressourcen, um den angeforderten Dienst auszuführen.

2021-08-05 03:18:53.837 Will retry in 30 seconds...
2021-08-05 04:09:55.790 Error opening serial port - Nicht genügend Systemressourcen, um den angeforderten Dienst auszuführen.

2021-08-05 04:09:55.790 Will retry in 30 seconds...
2021-08-05 05:00:55.307 Error opening serial port - Nicht genügend Systemressourcen, um den angeforderten Dienst auszuführen.

2021-08-05 05:00:55.307 Will retry in 30 seconds...
2021-08-05 05:51:57.729 Error opening serial port - Nicht genügend Systemressourcen, um den angeforderten Dienst auszuführen.

2021-08-05 05:51:57.729 Will retry in 30 seconds...
2021-08-05 06:27:00.425 Cumulus terminating

I will go back to 1331

Phil23 wrote: ↑Wed 04 Aug 2021 10:58 pm Yeah that's normal for a direct IP Airlink config.
Would good to see that message suppressed if possible when an Airlink is configured as IP standalone & not being associated with WeatherLink.

Standalone AirLinks will still be associated with WeatherLink.com?

The status message is just saying that no details were entered, so we/I know that historic data catch-up is not possible, nor the fetching of system health data on network stats, WiFi signal strength, system uptime, and firmware version.