Category:Cumulus MX: Difference between revisions

From Cumulus Wiki
Jump to navigationJump to search
m
 
=== Internet Settings ===
This has a lot of similarities with the [[Cumulus_Screenshots#Sites.2FOptions_Tab|Cumulus 1 settings]], except that this screen only covers what was on the main tab in Cumulus 1. Again there are hints, MX has more options than Cumulus 1 had, and some defaults are different in the two flavours. WindyNo hassettings take effect until '''Save''' button pressed. In Cumulus 1, you had beenone addedsetting to upload the externalstandard webfiles sitesand that canincluded beweb automaticallypages, updatedmoon image, and the graphs. NoMX has separate selection settings takefor effectthe untiluploading '''Save'''the buttonstandard pressedfiles (web pages), the include graph files (JSON files used by charts) [[File:Include graph data files.PNG]], for generating the moon image, and for uploading the moon image.
 
Windy has been added to the external web sites that can be automatically updated. No settings take effect until '''Save''' button pressed.
The main new feature within this settings page is a '''Custom Http''' section. Within here you can define commands to be executed either at some multiple of seconds interval, and/or at a selected intervals in minutes, and/or at end of day (in [[#MX_End_of_Day_Process|EOD sequence shown below]], the Custom HTTP is run before external programs are run, and that is before upload of Extra Files at EOD). In each of these you can use web tags to supply values for parameters to the command. Typically this would be used to send information to a remote web server. Here is a Custom HTTP example <pre>https://the_URL_here/your_api_here?winddir=<#avgbearing>&windspeedmph=<#wspeed>&windgustmph=<#wgust>&tempf=<#temp>&rainin=<#rhour>&baromin=<#press>&dewptf=<#dew>&humidity=<#hum>&uv=<#UV>"</pre>
 
You need to turn on enhanced debug logging to see any confirmation that the http has run:
The main new feature within this settings page is a '''Custom Http''' section. Within here you can define commands to be executed either at some multiple of seconds interval, and/or at a selected intervals in minutes, and/or at end of day (in [[#MX_End_of_Day_Process|EOD sequence shown below]], the Custom HTTP is run before external programs are run, and that is before upload of Extra Files at EOD). In each of these you can use web tags to supply values for parameters to the command. Typically this would be used to send information to a remote web server. Here is a Custom HTTP example <pre>https://the_URL_here/your_api_here?winddir=<#avgbearing>&windspeedmph=<#wspeed>&windgustmph=<#wgust>&tempf=<#temp>&rainin=<#rhour>&baromin=<#press>&dewptf=<#dew>&humidity=<#hum>&uv=<#UV>"</pre> No settings take effect until '''Save''' button pressed. You need to turn on enhanced debug logging to see any confirmation that the http has run:
<pre>
2018-07-21 16:05:00.821 Custom HTTP Minutes update
5,838

edits

Navigation menu