Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
XAP Data transmission
- pete_c
- Posts: 228
- Joined: Wed 12 Oct 2011 11:22 pm
- Weather Station: Davis Vue-Pro2 - Fine Offset
- Operating System: W2003-XPSP3-Linux
- Location: Time Traveler
XAP Data transmission
Steve,
Just curious if more data could be added to the XAP transmission?
I currently upload the standard web server stuff to a separate web page, upload to Weatherunderground and take the data via XAP and insert it into a database for additional graphing. It would be nice to include the additional data provided by Cumulus to XAP. I am currently testing both the Davis Vantage Vue and the Fine Offset weather stations in two instances of Cumulus and both offer similiar data.
Just curious if more data could be added to the XAP transmission?
I currently upload the standard web server stuff to a separate web page, upload to Weatherunderground and take the data via XAP and insert it into a database for additional graphing. It would be nice to include the additional data provided by Cumulus to XAP. I am currently testing both the Davis Vantage Vue and the Fine Offset weather stations in two instances of Cumulus and both offer similiar data.
You do not have the required permissions to view the files attached to this post.
- Pete
Automator
Automator
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: XAP Data transmission
It would be possible, yes, but isn't there supposed to be some sort of standard? I think Cumulus already implements everything that it can that's in the standard. I don't really want to start throwing extra stuff in there if it breaks the standard. Having said that, I think I did add the 'Rain' item which isn't in the standard.
Steve
- pete_c
- Posts: 228
- Joined: Wed 12 Oct 2011 11:22 pm
- Weather Station: Davis Vue-Pro2 - Fine Offset
- Operating System: W2003-XPSP3-Linux
- Location: Time Traveler
Re: XAP Data transmission
Hello Steve,
Yes its here:
http://www.xapautomation.org/index.php? ... her_Schema
Yes its here:
http://www.xapautomation.org/index.php? ... her_Schema
I've been doing much XAP stuff lately and request a change to the "weather report" schema to include both rain and humidity.Weather.Report
Class=weather.report
weather.report
{
UTC=(Time of report in hh:mm format using utc time zone)
-- mandatory
DATE=(Date of report in YYYYMMDD format)
-- mandatory
WindM=(Value of wind in mph or "Gusty" if gusty)
-- optional
WindK=(Value of wind in kph or "Gusty" if gusty)
-- optional
WindGustsM=(Value of wind gusts in mph)
-- optional
WindGustsK=(Value of wind gusts in kph)
-- optional
WindDirC=(Compas heading of wind N|NE|E|SE|S|SW|W|NW)
-- optional
WindDirD=(Compas heading of wind in degrees)
-- optional
TempC=(Temperature in centigrade)
-- optional
TempF=(Temperature in fahrenheit)
-- optional
DewC=(Dew point in fahrenheit)
-- optional
DewF=(Dew point in fahrenheit)
-- optional
AirPressure=(Air pressure in hPa)
-- optional
Cloud=(Overal cloud cover currently only "Clear Skies")
-- optional
CloudM.X=(Cloud type and height in miles ie "Overcast at 5.4M. X increments on each cloud layer)
-- optional
CloudK.X=(Cloud type and heightin kilometers ie "Overcast at 5.4Km. X increments on each cloud layer)
-- optional
Icon=(The name of the picture to use, icon names from kweather http://www.kde.org. File names below)
-- optional
Error=(Download errors either "NoData" if last connection failed or "StationNotFound" if ICAO code isn't valid)
-- optional
}
- Pete
Automator
Automator
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: XAP Data transmission
If the protocol spec is enhanced, I can certainly look at adding the necessary changes to Cumulus, assuming it has easy access to the data for any new parameters.
Steve
- pete_c
- Posts: 228
- Joined: Wed 12 Oct 2011 11:22 pm
- Weather Station: Davis Vue-Pro2 - Fine Offset
- Operating System: W2003-XPSP3-Linux
- Location: Time Traveler
Re: XAP Data transmission
Steve,
The weather dot report xAP has been updated.
Discussion here about it:
http://www.automatedhome.co.uk/vbulleti ... php?t=3300
http://www.xapautomation.org/index.php? ... her_Schema
The weather dot report xAP has been updated.
Discussion here about it:
http://www.automatedhome.co.uk/vbulleti ... php?t=3300
Draft Weather Schema
As descibed in the protocol definition, the message body will be preceded by a header, eg
{
v=12
hop=1
uid=FF400200
class=weather.data
source=vendor.weather
}
In the message body below, most keys are optional.
Keys for which data is not available from the data source in use should not be included.
To reduce the message complexity, message size, and to remove data that the end user will not use, the vendor may consider allowing the user to disable keys or key pairs, even if data is available
For example :
if WindDirD was not required because, for instance, it was non-numeric it would not be included
if TempF was not required because temperature in fahrenheit was not appropriate to the localisation it would not be included
If the Indoor Humidity and temperature were not required then all 3 could be omitted
Previous schema included keys for AirPressure and actual implementations included Rain, but this was not in keeping with the overall approach of the schema. Vendors may wish to keep these keys in the short term for compatibility, but both users and vendors are encouraged to use the format below for these keys.
weather.report
{
UTC=(Time of report in hh:mm format using utc time zone)
-- mandatory
DATE=(Date of report in YYYYMMDD format)
-- mandatory
Station=(Station code or identifier eg EGNJ)
-- optional
Location=(location, city, town, village)
-- optional
WindM=(Value of wind in mph or "Gusty" if gusty)
-- optional
WindK=(Value of wind in kph or "Gusty" if gusty)
-- optional
WindGustsM=(Value of wind gusts in mph)
-- optional
WindGustsK=(Value of wind gusts in kph)
-- optional
WindDirC=(Compass heading of wind N|NE|E|SE|S|SW|W|NW)
-- optional
WindDirD=(Compass heading of wind in degrees)
-- optional
TempC=(Temperature in centigrade)
-- optional
TempF=(Temperature in fahrenheit)
-- optional
DewC=(Dew point in centigrade)
-- optional
DewF=(Dew point in fahrenheit)
-- optional
RainM=(Rainfall since midnight in mm)
-- optional
RainI=(Rainfall since midnight in inches)
-- optional
Humidity=(Relative Humidity as %)
-- optional
AirPressureP=(Air pressure in hPa)
-- optional
AirPressureH=(Air pressure in inHg)
-- optional
AirPressureI=(Air Pressure Indication Rising/Steady/Falling)
-- optional
VisibiltyM=(visibility in meters)
-- optional
VisibiltyY=(visibility in yards)
-- optional
Cloud=(Overall cloud cover eg "Clear Skies")
-- optional
CloudM.X=(Cloud type and height in miles ie "Overcast at 5.4M. X increments on each cloud layer)
-- optional
CloudK.X=(Cloud type and heightin kilometers ie "Overcast at 5.4Km. X increments on each cloud layer)
-- optional
WindchillC=(Windchill Temperature in centigrade)
-- optional
WindchillF=(Windchill Temperature in fahrenheit)
-- optional
InTempC=(Indoor Temperature in centigrade)
-- optional
InTempF=(Indoor Temperature in fahrenheit)
-- optional
InHumidity=(Indoor Relative Humidity as %)
-- optional
Picture=(url to weather/webcam picture)
--optional
Icon=(The name of the picture to use, icon names from kweather http://www.kde.org. File names below)
-- optional
Error=(Download errors either "NoData" if last connection failed or "StationNotFound" if ICAO code isn't valid)
-- optional
}
Possible icon names, higher number signifies more clouds
cloudy1
cloudy2
cloudy3
cloudy4
cloudy5
dunno (usually with "error=nodata")
fog
hail
light_rain
mist
overcast
shower1
shower2
shower3
sleet
snow1
snow2
snow3
snow4
snow5
sunny
tstorm1
tstorm2
tstorm3
The Wiki here will be updated shortly.
http://www.xapautomation.org/index.php? ... her_Schema
- Pete
Automator
Automator
- pete_c
- Posts: 228
- Joined: Wed 12 Oct 2011 11:22 pm
- Weather Station: Davis Vue-Pro2 - Fine Offset
- Operating System: W2003-XPSP3-Linux
- Location: Time Traveler
Re: XAP Data transmission
The xAP weather report wiki has been updated now "officially". Here is the link.
http://www.xapautomation.org/index.php? ... ather.data
http://www.xapautomation.org/index.php? ... ather.data
- Pete
Automator
Automator
-
Maze42
- Posts: 3
- Joined: Sat 17 Jul 2010 9:17 am
- Weather Station: EasyWeather
- Operating System: WinXP
Re: XAP Data transmission
I would love to have the new xAP Schema added to Cumuls. Now I have to use two extra RH sensors and software to make the weather data for my house automation system complete.