cloudy cloudy

Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Win, will it still be possible to produce the Weather34 graphs if one does not use the temporary SQL/database, that is once access to the Weather Underground data becomes inaccessible/unreachable?
12
WD Questions / Re: sun/moon eclipse tag
« Last post by s52sk on Today at 09:17:15 AM »
Hi folks!
Just for info that moon eclipse data have now correct time: 21/januar/2019 06:12 (Local) 120%. At 06.12 is beginning of totality.

CS Marco
13
WD Questions / MQTT Sensors
« Last post by Phoniclynx on Today at 08:19:44 AM »
Does WD happen to read MQTT in as a sensor.. I have a few Shelly H&T sensors that publish to my MQTT server, it would be nice if I could get that data into WD too.
14
. . . shortened . . .
No sense in storing two sets of the same data on the GoDaddy server if I can make do with one!

Thanks for any comments.   Dale
The HomeWaterStation-template for WD (as designed by BrianU @weather34) and maintained by me,  stores during 24 hours the data of that one day in a database table. Nothing is done with that data during the day.
When using the "database" the same uploaded data is also stored in a daily .CSV "results.csv".

At almost the end of the day, a cron-job uses  1 SQL statement to calculate the high-lows of the fields  and those high-lows are added as a new line to two .CSV text-files with "this years"and "this months" data.
Just at the beginning of the day,  all data is removed from the table (truncate) in the database.

So "yes" HWS-WD uses a  SQL table (can be in any database). But inside the table there is no other data then todays uploaded data. Only 1 time / day the sql data is read.
Could easily have been a text file but using a text-file is more "dangerous" when updating and also more cumbersome to calculate the high-lows.

Why
Because around Feb 15, 2019 we will not be able to use our data from the WU servers as we did before.
We used to load "this years" , "this months" and "todays" data from the WU servers, cached those files and generated the graphs from those files.
Last year, @weather34 included this easy to use SQL solution and the two cron-jobs to generate .CSV tables to use for the graphs even after WU data would be un-available.
This was never meant to be a "database with weather-information" such as used in Jachym's MeteoTemplate.
If you do not want to use the graphs, no need to use the SQL/database at all for the HWS-template.

Wim
15
I'm having a problem using wdapi.

It seems to be set correctly, but when I press the test in WD I get "Success: Bad data". and the database does not get updated.
. . .  shortened . . .
Bad Data:
Step 1: save the uploaded data which is put after the URL by WD in the form  URL?d=all_your_data_fields
The first part of the return message "succes" signals that some data  (at least 50 characters) was received  and is saved as a text-string for later use
2. Then the WDapi checks if a database exits "If not" the script ends.
You have set you will use a database so the settings are read to check if WDapi needs to upload to the database
The database name, password a.s.o.  are checked if they are not empty,  if empty the script ends without a message.
Then it checks if "WDapi or the cronjob" must upload. If the cronjob should do it => no message and the WDapi script ends.

3. The WDapi script connects to the database, in your case the connection is OK, otherwise there would have been an error message

4. The fields for the database are created from the text string
AND NOW the data is inserted in the database
Code: [Select]
$result = mysqli_query($conn,"INSERT INTO weatherstation(time, outsideTemp, barometer, raintoday, UV, windgust, windSpeed, radiation, dewpoint, rainrate, direction, date, lightning)
VALUES('$updated', '$temp', '$barometer', '$raintoday', '$uv', '$windgust', '$windspeed', '$solar', '$dewpoint', '$rainrate', '$direction', '$date', '$lightning')");
if ($result == false)
     { die ('Bad Data: '. mysqli_connect_error()); }


The only thing which does not works is the insert, probably the credentials for the userid are set to low.
I will read the documentation to find a better clue what is wrong, as the error message displayed is empty, try the attached replacement script
Use PHPADMIN or your cPanel and give this weather34 user all credentials possible.
===
Check http://wd34.weather-template.com//documentation/WD34-SQL-2019-01.pdf point 2.1: you could try load some data with PHPadmin, just to see  if there is an error message.
===
When you use the WDapi in your browser you get those messages as the fields are not available URL?d=all_your_data_fields


16
WD Questions / Re: weather display not responding
« Last post by bonko on Today at 05:54:16 AM »
doesn't work on start up,went to action extract date from davis datalogger set time data downloads to wd
17
WD Bug Reports / Re: Main screen data missing
« Last post by pmeehan on Today at 05:51:40 AM »
If I run V 10.37S B72, all runs well and the full data is displayed on the main screen .GIF and displays on my website.  have gone back to that version and all good.

I first noted the anomaly when I attempted to upgrade the WD version (unknows Build vewrsion) in late Oct or Nov 2018.   The issue has occurred all versions I have tried incl 10.37S Build 87 downloaded earlier today.  See file CamborneWeather.GIF uploaded with first post.
18
I'm having a problem using wdapi.

It seems to be set correctly, but when I press the test in WD I get "Success: Bad data". and the database does not get updated.


This is what I get when I manually execute wdapi:

Notice: Undefined variable: file_contents in C:\Abyss Web Server\htdocs\pwsWD\w34_WDapi.php on line 71

Notice: Undefined offset: 2 in C:\Abyss Web Server\htdocs\pwsWD\w34_WDapi.php on line 74

Notice: Undefined offset: 10 in C:\Abyss Web Server\htdocs\pwsWD\w34_WDapi.php on line 75

Notice: Undefined offset: 9 in C:\Abyss Web Server\htdocs\pwsWD\w34_WDapi.php on line 76

Notice: Undefined offset: 39 in C:\Abyss Web Server\htdocs\pwsWD\w34_WDapi.php on line 77

Notice: Undefined offset: 6 in C:\Abyss Web Server\htdocs\pwsWD\w34_WDapi.php on line 78

Notice: Undefined offset: 5 in C:\Abyss Web Server\htdocs\pwsWD\w34_WDapi.php on line 79

Notice: Undefined offset: 41 in C:\Abyss Web Server\htdocs\pwsWD\w34_WDapi.php on line 80

Notice: Undefined offset: 4 in C:\Abyss Web Server\htdocs\pwsWD\w34_WDapi.php on line 81

Notice: Undefined offset: 8 in C:\Abyss Web Server\htdocs\pwsWD\w34_WDapi.php on line 82

Notice: Undefined offset: 7 in C:\Abyss Web Server\htdocs\pwsWD\w34_WDapi.php on line 83
Bad Data:
19
WD Bug Reports / Re: Main screen data missing
« Last post by Weather Display on Today at 03:37:46 AM »
What version/ build
20
So far, I've been able to implement (using the textbook approach and line by line instructions) to get WD to provide data as needed for a bare bones display for Weather34.

In Weather34 there are instructions about setting up an SQL database on my server (GoDaddy is who I use) which would allow the W34 to display historic data, if I understand it correctly.  since I'm more of what is it like now kind of guy, I've not implemented the SQL option.

I got thinking, since I also have Jachym's excellent Meteotemplate running, which has it's own SQL taking in data uploaded by WD with it's MeteoAPI, is there some way to tell Weather34 to go look at the SQL I've already set up for Meteo, and save uploading BOTH data streams?  Or is there a different sequence and naming convention and so on in the Meteo database that means it would be able to extract the data that it needs and I really would need to set up both?  I am obviously a real neophyte on these things.  Sounds like it could work, but maybe too many things stand in the way.

As I said, I'm pleased that they both work, and that to see what is happening in real time for W34 and also in Meteo is fine, and if I really want to go back in time, I can tell Meteo to do so and see all those nice graphs and stuff.

No sense in storing two sets of the same data on the GoDaddy server if I can make do with one!

Thanks for any comments.   Dale
Pages: 1 [2] 3 4 ... 10
cumulus