Page 1 of 1

Strange data line in database

Posted: Sat Dec 21, 2019 11:44 am
by magical46
Hi, I am using a "fine offset" type weather station which as with most of these occasionally throws a wobbly and gives me some ridiculous spikes, something I just have to live with. I go into the database editing and delete the affected lines, no problem. However I have noticed recently when doing this that every hour(whether there is a spike or not) there is a line of data on the hour e.g. 08:00:00 followed by a second line of the same data at , for example, 08:00:30. Now if there is a spike on the hour then deleting that line also deletes the hour +30 second line. It doesn't appear to affect anything, I just don't thing the second line should be there.
I do have WD sending a tweet to twitter on the hour but have tried turning that off as I thought that may cause the issue but that made no difference.
Any thoughts?

Re: Strange data line in database

Posted: Thu Jan 02, 2020 1:06 pm
by MonyMony
Hum... besides saying 'that's weird', I'm having a hard time coming up a scenario that would cause this. Meteotemplate should only write to the database every few minutes based off of a cache of data received from the API uploads. My only guess is to check to see if you have any custom scheduled jobs (like a cron job) that might be triggering the database upload but I'm not even sure what to suggest to look for.

Re: Strange data line in database

Posted: Sat Jan 25, 2020 9:55 pm
by magical46
I have WD uploading to twitter every hour, thought that maybe it but I tried switching that off but still got the "spurious" data line

Re: Strange data line in database

Posted: Sun Jan 26, 2020 6:29 am
by Jolumarali
hello
Personally for Twitter I send every hour with Weathercloud.com

José Luis

Re: Strange data line in database

Posted: Fri Jan 31, 2020 1:16 am
by andyk1
Check to make sure you are only updating once. One cron job... etc. Not sure how you have your system setup or how you are feeding your data... Meteobridge or Ecowitt etc.

Strangely, the first time I replied to it didn't work.