Belchertown Skin and MQTT after power outage

[Chris P]

Would anyone have any idea why the Data Received no longer displays the date and time correctly?  I had everything setup perfectly last night, had a storm roll through and lost power, and ever since, the display shows Connected to weather station live. Data received Invalid date.  I cant seem to pinpoint how i would be able to fix this, since there are no errors in the syslog.

[gjr80]

Hi,

Impossible to say anything without more info. The log may well have no errors but it can still tell us a lot. I suggest you edit weewx.conf, set debug=1, save weewx.conf then restart WeeWX. Let WeeWX run for at least three report cycles then post a log extract from when you restarted WeeWX through until the three report cycles have completed. Don't edit the log extract.

Gary

[Pat]

Chris, pretty tough to know without more information. Try Gary's suggestion to see what's in the system log. Seems like there's something with weewx and the MQTT extension (not necessarily the skin). 

But in addition let's try this:

1. Use Chrome or Firefox and open their developer tool panel. 
1. Chrome is under Menu > More Tools > Developer Tools
2. Firefox is under Menu > Web Developer > Toggle Tools
2. Then open the Console tab and browse to your website with /?debug=true at the end of your website address. 
3. Then inside that Console window will be a lot of information. Hopefully you're on skin 1.0.1 because that skin version shows MQTT debug data very easily.

Inside that data stream should be the timestamp from weewx under "dateTime". Here's an example of my station with the timestamp bolded. What does yours show? 

{"UV": "0.0", "barometer_inHg": "30.0435346853", "outHumidity": "72.7", "maxSolarRad": "0.0", "dewpoint_F": "57.7446963505", "cloudbase_foot": "2488.02355671", "heatindex_F": "66.8", "altimeter_inHg": "30.0418515007", "dayRain_in": "0.01", "outTemp_F": "66.8", "appTemp_F": "68.1374342821", "windchill_F": "66.8", "hourRain_in": "0.01", "humidex_F": "73.179781909", "rainRate_inch_per_hour": "0.0", "pressure_inHg": "29.5869803759", "usUnits": "1.0", "txBatteryStatus": "0.0", "windSpeed_mph": "2.0", "rain24_in": "0.01", "dateTime": "1560216168.0", "windDir": "159.04743083", "radiation_Wpm2": "0.0"}

if you browse to your website in Chrome, then go to Chrome 

[Pat]

Forgot to add that if you're not on 1.0.1, then you'll need to connect to your MQTT broker to check the payload data.

[Chris P]

Ok I subscribed to my broker and I am seeing that the time is being sent.

{"sensor_id": "3384.0", "hourRain_in": "0.0", "windSpeed_mph": "0.0", "rxCheckPercent": "100.0", "maxSolarRad": "0.0", "rainRate_inch_per_hour": "0.0", "dateTime": "1560217427.0", "dayRain_in": "0.0", "usUnits": "1.0", "sensor_battery": "0.0", "rain_in": "0.0", "outTempBatteryStatus": "0.0", "rain_total": "21.1074", "rain24_in": "0.0", "channel": "3.0", "rssi": "3.0"}

I was not on 1.0.1 yet, but have now updated to that.  I have since updated to newest version.  Will post debug =1 log.

[Pat]

Ok. If the time is there, then perhaps it is a skin issue. Are you FTP'ing the skin to a remote server? Have all files been updated recently? 

I'm curious what the /?debug=true would show as well. Or if you want, send me your site URL and I can look when I have a chance too

[Pat]

Thanks. Nothing standing out. You can delete it if you want since it's so long. I'll take a look to see what I can find.

[Pat]

I'm still looking and not seeing much. The only thing that stands out right now is the topic you're subscribed to. Change weather/kwimosin16/# to be weather/kwimosin16/loop

When I set my development site up to use your mqtt broker's information on that /loop topic, it's working for me. Give that a try?

[Chris P]

Thank you so much for your help Pat!   That appears to be the trick.  The date is now displaying.  Im assuming if I use aggregation = aggregate in my mqtt conf settings, then it wouldn't send all the readings individually, that must be what the websocket is trying to read that its not getting the data stamp.