meteohub.de

Actually on Meteohub systems, Heat Index only comes into account if the temperature is at or above 80F/27C and humidity is at least 40%, due to the formula used for calculation (this was a bug fixed in the last Meteohub revision... previously at temperatures below 80F weird negative values would often come up.) If the temperature or humidity is below that threshold, the heat index value is identical to the ambient temperature for that sensor. I'm not sure how WD-Live deals with this -- it might simply ignore any heat index or wind chill that is identical to the ambient temperature, similar to not processing wind gusts when the air is calm.

The Humidex formula works over a wider temperature range, but unless you're in or near Canada it's an unusual term for most people... and it also tends to be warmer than the comparable Heat Index value in warm, humid conditions.

Hi all!

I'm having the same problem with clientraw.txt and dataweather.txt, they are empty with 0 bytes.

I've have reviewed all config screens of Meteohub and didn't find anything wrong. I've the 2.7 version installed.

Looking on the log files I've got this:

mv /data/graphs/clientraw.out "/data/uploads/clientraw.txt")
Sep 18 23:09:01 (none) cron.info /USR/SBIN/CRON[16449]: (root) CMD (sleep 0; /srv/www/meteograph.cgi text all>/data/graphs/all-sensors.txt; /srv/www/cgi-bin/stamp.cgi cp /data/graphs/all-sensors.txt /data/myweb/uploads/dataweather.txt; /srv/www/cgi-bin/stamp.cgi mv /data/graphs/all-sensors.txt /data/uploads/dataweather.txt)
Could not read reply from control connection -- timed out.
ncftpput /data/uploads/dataweather.txt: timed out while waiting for server response.
ncftpput /data/uploads/meteoclimatic.txt: remote host closed control connection.

The strange thing about all this is that the Meteohub is able to create the files dataweather.txt and clientraw.txt on the remote server but they stay with 0 bytes of size. When I test the ftp connection in the "Setup Push Services" the Meteohub returns a success message. I've running the Meteohub since end of July and this never happened before :(

From where I must start to resolve this issue?

you need to click on SAVE with MeteoHubs WD Live page to apply the new settings >>>

No luck at all.
I think this is not an issue only with WD-Live & Dashboard only. I setup the upload of all-sensors file and it goes empty too...

A Google search on the phrase "Could not read reply from control connection" suggests that this is how NCFTPUT relays an error involving the remote host -- it seems as if for some reason your server's FTP client has changed its standards or protocols to an odd form that the Meteohub FTP client does not understand.

Since apparently no one else has reported this error message in the forum, that implies that it is something specific to your hosting provider and I would suggest contacting them to see if something has changed on their end.

Past that there's always the slim possibility of a corrupted installation/upgrade on your Meteohub, and a reinstall or fresh USB stick might be needed.

After some research I changed from one FTP server to another and now everything is OK!
Thanks everyone!