Pocket PWS and Readings

[txweather]

I been using Pocket PWS for a while with Cumulus.
After switching to CumulusMX the output of Pocket PWS template is not correct.
Not sure how to fix it.
If this is an author problem please let me know and ill be gald to report it.

Please see the attached cumulus.xml for the templete file and the cumulus_andr.xml for the outoput file.

[txweather]

By the way the temp readings and the rain are the ones not right.

[steve]

I can't see anything wrong with the xml template, and all of those web tags are common ones, and they are working OK in MX. I've just tried the template, and it works fine for me, as far as I can tell. If the values in there are not correct for you, the only explanation I can suggest is that they are not correct in MX itself either. It's possible the processing of the file stopped working for some reason, but that would be reflected in the date and time in the processed file if that were the case.

All of the highs and lows in your file are the same as the 'current' figure, which suggests that at the time the file was processed, MX had only had one reading for today.

What settings do you have for this file in the 'extra web files'? What values do the standard web site files contain, in comparison?

[freddie]

I been using Pocket PWS for a while with Cumulus.
After switching to CumulusMX the output of Pocket PWS template is not correct.

I use Pocket PWS on My Cumulus MX output, and I don't have problems. If it helps, you can look at my output at http://www.hosiene.co.uk/weather/cumulus.xml. You could also try pointing your Pocket PWS installation at this URL to enable you to rule out problems with your installation (of pocket PWS)

[txweather]

Thank you all for the help.

Well after checking this AM the issue it seems that CumulusMX had stop getting data:

Code: Select all

2016-01-05 00:00:00.368 Writing yesterday.ini                                                             
2016-01-05 00:00:00.392 Written yesterday.ini                                                             
2016-01-05 00:00:00.394 === Day reset complete                                                            
2016-01-05 00:00:00.397 Now recording data for day=5 month=1 year=2016                                    
2016-01-05 00:00:00.401 Reset sunshine hours, yesterday = 0                                               
2016-01-05 00:00:00.403 Writing yesterday.ini                                                             
2016-01-05 00:00:00.417 Written yesterday.ini                                                             
2016-01-05 00:00:00.420 *** Data input appears to have stopped                                            
2016-01-05 00:00:00.427 Writing log entry for 1/5/2016 12:00:00 AM                                        
2016-01-05 00:00:00.431 Written log entry for 1/5/2016 12:00:00 AM                                        
2016-01-05 00:00:00.447 Writing today.ini, LastUpdateTime = 1/5/2016 12:00:00 AM raindaystart = 45.2 rain counter = 45.2                                                                                            
2016-01-05 00:00:00.452 Creating backup folder backup/daily/20160105000000/                               
2016-01-05 00:01:00.087 *** Data input appears to have stopped                                            
2016-01-05 00:02:00.132 *** Data input appears to have stopped                                            
2016-01-05 00:03:00.184 *** Data input appears to have stopped                                            
2016-01-05 00:04:00.236 *** Data input appears to have stopped                                            
2016-01-05 00:05:00.294 *** Data input appears to have stopped                                            
2016-01-05 00:05:00.303 Writing log entry for 1/5/2016 12:05:00 AM

Not sure why this happen. My site continued to get live data and meteohub had no issues.
So you guys are righ the info its there and fine.
I do have a question I have funky characters on my display for the temp unit and when I look on the output I have:

Code: Select all

<data units="tempunit">Fￜ</data>

Any ideas how to fix that?

Steve to answer your question: I have Process, Realtime, and FTP checked. UTF8 is unchecked and BINARY is unchecked.

Thanks for the help!

[steve]

I do have a question I have funky characters on my display for the temp unit and when I look on the output I have:

Code: Select all

<data units="tempunit">Fￜ</data>

Any ideas how to fix that?

It's a known issue in the latest code - see the 'known issues' post.

There is also a known issue where reading of archive data stops after the end of day reset (the logger times out and stops sending the data). That's when yours stopped, but it wasn't reading archive data. I'm not aware of anyone having the issue with 'live' data when connected directly to a logger. Could be another timing issue when going via the meteohub.

[txweather]

I do have a question I have funky characters on my display for the temp unit and when I look on the output I have:

Code: Select all

<data units="tempunit">Fￜ</data>

Any ideas how to fix that?

It's a known issue in the latest code - see the 'known issues' post.

There is also a known issue where reading of archive data stops after the end of day reset (the logger times out and stops sending the data). That's when yours stopped, but it wasn't reading archive data. I'm not aware of anyone having the issue with 'live' data when connected directly to a logger. Could be another timing issue when going via the meteohub.

Interesting.
It died right at midnight "log rollover".

Ill continue to monitor and report back.

Thanks!

[steve]

If you still have data logging on, the diags file might be interesting.

[txweather]

If you still have data logging on, the diags file might be interesting.

They are attached.

[steve]

Unfortunately you don't have either debug logging or data logging turned on:

2016-01-04 13:20:18.640 Debug logging is disabled
2016-01-04 13:20:18.640 Data logging is disabled

One thing I do see is that when you restart MX, you are getting the entire contents of the logger every time. This because your console clock is a couple of minutes behind your computer clock:

2016-01-04 13:20:39.221 Console clock: 1/4/2016 1:18:35 PM

So when MX asks for archive data from a time which the console thinks is in the future, the console decides to send everything it has.

[txweather]

Unfortunately you don't have either debug logging or data logging turned on:

2016-01-04 13:20:18.640 Debug logging is disabled
2016-01-04 13:20:18.640 Data logging is disabled

One thing I do see is that when you restart MX, you are getting the entire contents of the logger every time. This because your console clock is a couple of minutes behind your computer clock:

2016-01-04 13:20:39.221 Console clock: 1/4/2016 1:18:35 PM

So when MX asks for archive data from a time which the console thinks is in the future, the console decides to send everything it has.

Thank you for this information.
I set CumulusMX to set my console time.
I enable both logs and if it dies tonight ill come and update this thread with the logs.

Thanks again for the help!

[txweather]

Just wanted to report that CumulusMX didnt die today at 12AM.
All looks good.

Thanks!

[txweather]

If you still have data logging on, the diags file might be interesting.

Steve,

It died today.

Logs are attached.

[steve]

You don't have data logging turned on. If you're turning it on via the UI, that only affects the current session (to avoid it being left on long term unintentionally). So you either need to turn it on every time you start up, or edit Cumulus.ini to set DataLogging=1.

[txweather]

If you still have data logging on, the diags file might be interesting.

Steve,

It died today.

Logs are attached.

Well crap lol
Ok. I just add it that to the ini file.