CumulusMX shows 32 F and other default values after a few hours

[popsicleorama]

Current setup is an ambient weather WS2095 tied to a RPi 2 running Cumulus MX 3041 using the autostart scripts

System was working fine for almost a year, about a month ago I had an issue that required the base station to be reset multiple times. Every other day the station would lose connection from the RPi and then its buffer would fill up requiring me to pull the batteries in the base and reset the RPi) I decided to update the CumulusMX version to 3038 which was the newest version at the time. I extracted the zip over the previous install (if anyone was wondering it was originally a clean install and not upgrade from a prior Cumulus version) the station was up for about 10 days and then I noticed on wunderground that it was reading 32F flat line along with every other value like wind speed, direction, pressure flat lines at some default value. Cumulus was continuing to show a connection and reporting. When I looked at the base station it was reporting an accurate outside temperature and other readings on the screen. I reset the station and Cumulus and it worked for another day and a half and then repeated the same issue so I disconnected the PI. Today I started from a clean raspbian image and reinstalled everything using 3041 and a clean cumulus.ini file, replaced batteries and reset everything. It started working fine, but after an hour it flat lined again.

Is the WS2095 the culprit? is there a way to debug the messaging to make sure?

Is there any known issue like this that I missed in the forums?

If it is the WS2095 base station I am in the market to get a new weather station to use with CumulusMX and the RPi (I need local values for some other home automation purposes)

Any recommendations on stations under $250? (my threshold for buying/ripping apart the sensors on the 2095 and building my own)

I'm completely confused by the need on the newer ambient weather stations why they can't provide local connectivity and still amazed that Davis hasn't come out with something to replace its antiquated connectivity setup...

[ConligWX]

Best to zip up the \MXdiags\ folder (and contents) and post it here for Steve to take a look.

[popsicleorama]

Reset the station and turned on Logging=1 in the .ini file. I will post the mxdiag files once the error occurs again

Here is what I get in the logs if I don't reset the station (station console has good values throughout)

2016-09-10 20:39:45.879 Fine Offset station found
2016-09-10 20:39:45.953 Stream opened
2016-09-10 20:39:45.954 Reading pressure offset
2016-09-10 20:39:49.150 The operation has timed-out.
2016-09-10 20:39:49.151 Error reading data from station - it may need resetting
2016-09-10 20:39:52.152 The operation has timed-out.
2016-09-10 20:39:52.152 Error reading data from station - it may need resetting
2016-09-10 20:39:55.153 The operation has timed-out.
2016-09-10 20:39:55.153 Error reading data from station - it may need resetting
2016-09-10 20:39:58.154 The operation has timed-out.
2016-09-10 20:39:58.154 Error reading data from station - it may need resettin

[steve]

That looks like the usual Fine Offset USB lockup. Are you using the setting to synchronise Fine Offset reads?

Re your question about using your sensors with another setup, you could look at Weatherduino.

[popsicleorama]

I have had the fine offset synch option set in the past, it doesn't seem to make a difference (the below logs may not have it set)

Station finally flat lined, but the console is still communicating and showing valid data. I think the station USB may be done unless there is some sort of full factory rest that could be done there isn't a lot of options to fix it.

[steve]

It seems to be returning bad data occasionally, but most of the time nothing at all, rather than it being a complete lock up. I'm not sure what to suggest; I don't think it's a problem with Cumulus - you could perhaps try a different USB cable (one with ferrite chokes) if you haven't already.