Just a quick update in case it helps someone.

I was reminded that there was a power outage around the same time this 
started happening. Not one to believe in coincidence, I restored the 
database from a backup of the day before the power outage, and filled the 
missing data using wee_import from WU.

So far it has been 2 days since I have experienced the issue. Possibly 
there was some kind of database corruption.

Gary - Thanks for your help, appreciate it.

Adam

On Sunday, 30 August 2020 at 12:14:34 pm UTC+10 YB322 wrote:

> Yes, that is the unit I am using. I use the WS View to configure it, the 
> is no option to update the timezone, it may have been an option when I 
> first setup, it was a while ago I don't remember if it was. I will try a 
> factory rest on the station and re-configure and see if there is.
>
> Thanks again for the help.
>
> On Sunday, 30 August 2020 at 10:11:39 am UTC+10 gjr80 wrote:
>
>> Thought the 9 hour difference seemed familiar but thought it was the 
>> other side of GMT. I'm in Brisbane.
>>
>> That's interesting about no timezone because the WU format packet coming 
>> from your station includes a UTC format date-time string so the station 
>> must somehow know what timezone it is in. Actually, just did a google for 
>> Pantech 2900 on the desktop this time, is it one of these 
>> <https://www.ebay.com.au/itm/PanTech-Weather-Station-Wifi-Wireless-Professional-Solar-Power-UV-WH-WH2900-/263591411133>?
>>  
>> If so do you use the WS View app to configure? I have only used the WS View 
>> app to configure a GW1000 and in the device settings on WS View there is a 
>> timezone.
>>
>> Gary
>> On Sunday, 30 August 2020 at 09:23:49 UTC+10 YB322 wrote:
>>
>>> Thanks Gary,
>>>
>>> Timezone is Sydney\Australia (AEST - UTC+10). The station doesn't have a 
>>> timezone setting just date and time, which does look correct.
>>>
>>> It is really strange the setup had been working well for years and just 
>>> started doing it this week. I created a new server with Ubuntu 20.04 as a 
>>> troubleshooting step, but as you can see the issue came with it.
>>>
>>> Really appreciate you taking the time.
>>>
>>> Adam
>>>
>>> On Saturday, 29 August 2020 at 8:53:09 pm UTC+10 gjr80 wrote:
>>>
>>>> Adam,
>>>>
>>>> Definitely a time issue, what timezone are you in and is the timezone 
>>>> set correctly in you stations console?
>>>>
>>>> Gary
>>>> On Saturday, 29 August 2020 at 20:25:41 UTC+10 YB322 wrote:
>>>>
>>>>> Thanks Gary
>>>>>
>>>>> Appreciate you taking a look. I have stared at the log for the last 
>>>>> week and not noticed that one.
>>>>>
>>>>> I have pasted the debug here  https://pastebin.com/vrsDg0G6 
>>>>>
>>>>> unit is a PanTech WH2900. It does have a time setting, although it 
>>>>> does look correct.
>>>>>
>>>>> Thanks
>>>>> Adam
>>>>>
>>>>> On Saturday, 29 August 2020 at 8:11:44 pm UTC+10 gjr80 wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I’d say you are suffering from a little temporal displacement:
>>>>>>
>>>>>> Aug 29 08:00:38 weewx weewx[2328] DEBUG user.interceptor: raw packet: 
>>>>>> {'dateTime': *1598684400*, 'usUnits': 1, 'rain_total': 0.0, 
>>>>>> 'temperature_in': 64.6, 'temperature_out': 47.7, 'dewpoint': 41.5, 
>>>>>> 'windchill': 46.8, 'humidity_in': 40.0, 'humidity_out': 79.0, 
>>>>>> 'wind_speed': 
>>>>>> 3.4, 'wind_gust': 5.8, 'wind_dir': 267.0, 'pressure': 30.65, 
>>>>>> 'barometer': 
>>>>>> 30.21, 'solar_radiation': 189.98, 'uv': 2.0, 'rain': 0.0}
>>>>>> Aug 29 08:00:38 weewx weewx[2328] DEBUG user.interceptor: mapped 
>>>>>> packet: {'dateTime': *1598684400*, 'usUnits': 1, 'pressure': 30.65, 
>>>>>> 'barometer': 30.21, 'outHumidity': 79.0, 'inHumidity': 40.0, 'outTemp': 
>>>>>> 47.7, 'inTemp': 64.6, 'windSpeed': 3.4, 'windGust': 5.8, 'windDir': 
>>>>>> 267.0, 
>>>>>> 'radiation': 189.98, 'dewpoint': 41.5, 'windchill': 46.8, 'rain': 0.0, 
>>>>>> 'UV': 2.0}
>>>>>> Aug 29 08:00:38 weewx weewx[2328] INFO weewx.manager: Added record 
>>>>>> 2020-08-29 08:00:00 AEST (*1598652000*) to database 'weewx.sdb'
>>>>>> Aug 29 08:00:38 weewx weewx[2328] INFO weewx.manager: Added record 
>>>>>> 2020-08-29 08:00:00 AEST (*1598652000*) to daily summary in 
>>>>>> 'weewx.sdb'
>>>>>>
>>>>>> What station do you have? Does it have a clock and if so is it set 
>>>>>> correctly? Might help to see a wee_debug 
>>>>>> <http://weewx.com/docs/utilities.htm#wee_debug_utility> report. When 
>>>>>> posting the wee_debug report check the content for sensitive info such 
>>>>>> as 
>>>>>> usernames, passwords and API keys before posting, wee_debug should 
>>>>>> obfuscate such data but it’s not perfect.
>>>>>>
>>>>>> Gary
>>>>>>
>>>>>> On Saturday, 29 August 2020 at 19:10:06 UTC+10 YB322 wrote:
>>>>>>
>>>>>>> G'day everyone
>>>>>>>
>>>>>>> I have been experiencing an issue for the last week, and so far have 
>>>>>>> not been able to determine the cause. I was hoping someone may have 
>>>>>>> some 
>>>>>>> ideas.
>>>>>>>
>>>>>>> I am running the interceptor driver (
>>>>>>> https://github.com/matthewwall/weewx-interceptor)
>>>>>>> Weewx 4.1.1 
>>>>>>> SQLite Database
>>>>>>> OS Ubuntu 20.04 (Running as a VM on Hyper-V)
>>>>>>> Station in a Pantech
>>>>>>>
>>>>>>> At random times the system stops entering data into the database. 
>>>>>>> From what I can see in the log the interceptor driver appears to be 
>>>>>>> receiving the data but it isn't processing. The unit uploads data 
>>>>>>> direct to 
>>>>>>> Weather Underground and Weather Cloud, these services continue to 
>>>>>>> receive 
>>>>>>> data during the outage periods.
>>>>>>>
>>>>>>> I have uploaded the log file here: https://pastebin.com/WgNKTKRT
>>>>>>>
>>>>>>> The last successful database update in this log was Aug 29 08:00:38
>>>>>>>
>>>>>>> If anyone has any ideas it would be very much appreciated.
>>>>>>>
>>>>>>> Thanks
>>>>>>> Adam 
>>>>>>>
>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7707e7d8-bca6-4d94-b44a-ac7870d4aef3n%40googlegroups.com.

Reply via email to