Meteotemplate Forum

Thank you sir! This worked perfectly. Sorry for huge delay in responding!

Maybe I'm mistaken. Maybe these warnings are related to temperature warnings? What triggers these?

I don't get why, but my MT install (18.0) shows a red exclamation warning below the temperature, feels like, and dew point. Then a brown warning below pressure. What do these mean? I thought it meant the data was stale, but from what I can tell, everything is updating, I'm pushing data via the API e...

In my case, it's because I had converted the DB to innodb. Every 5 minutes is how often MT writes to it's DB. the every 30 seconds, or minute, etc just update the live data, but don't get archived. So the timeout is the fact the API is taking too long to respond back from the DB write. I'm just usin...

fwiw, my proposed fix didn't work. Created a new column "ID" set to autoincrement. Changed the primary key to it. Then moved table to InnoDB. Inserts still taking longer than 14 seconds.

Not sure why. For now, remaining on MyISAM seems like the only option. =/

Hmm, interesting. are you able to see any log data from Weather Display? Do you know how to enable slow query logging for MariaDB? I'd also look at the apache logs and see if you're seeing Weather Display hit the API as expected. That should eliminate one half of the equation (if WD is hitting the A...

Could I ask that we alter the database schema so the primary key is a normal row number rather than the date, and then convert to InnoDB? MyISAM is deprecated as of MySQL 8, and InnoDB does not like arbitrary primary keys (makes inserts take a significant amount of time).

Any hope of this getting fixed in the next version @Jachym? I'd like to move back to InnoDB... MyISAM is deprecated as of MySQL 8.0...

What format is your database? InnoDB or MyISAM?

Quick question. What format is the database? MyISAM or InnoDB?

slight tangent, but you want to make sure database ends up MyISAM and not InnoDB. Meteotemplate uses non-numbers for the primary key, and InnoDB hates it... inserts take multiple tens of seconds vs MyISAM which doesn't seem to care, and does normal insert speeds (less than a second).

andyk1 wrote: ↑Sun May 26, 2019 9:31 pm
Hello!!!

Out of curiosity, what block or plugin are you using to adjust the rain totals in your screenshot?

Sorry for huge delay. I didn't use anything to edit rain totals within MT. I just adjusted my import files and reimported (after nuking database).

Hi all,

Any input on this? I'd really like to see this be able to move to InnoDB...

kk. I figured out my issue (probably not related).

Thanks!

So I think I found the issue. I think. It's the DB design, and my fault. Here's what MT does for the DB: CREATE TABLE `$dbName`.`alldata` ( `DateTime` datetime NOT NULL , `T` decimal( 4, 1 ) DEFAULT NULL , `Tmax` decimal( 4, 1 ) DEFAULT NULL , `Tmin` decimal( 4, 1 ) DEFAULT NULL , `H` decimal( 4, 1 ...

It is bypassed. That’s the “nocache” subdomain.

Host is qth.com. Never had any issue. I do send MB data to several other locations, never an issue (unless I save right after it updates and hit a API limit). I'm pushing to my api via a cloudflare bypassed host. So the normal host is https://www.staze.org/meteo/ but for my MB, it's pushing to http:...

trying to wade through api.php and see if maybe it's not returning any response when doing a DB update (and therefore MB is timing out)... but it looks like it should be returning a "Success".

Finally found a lot of when it's timing out. 2019-04-15 12:45:44 Error: 2019-04-15 12:45:31 Read error (Operation timed out) in headers. (no more tries) 2019-04-15 12:40:39 Error: 2019-04-15 12:40:25 Read error (Operation timed out) in headers. (no more tries) 2019-04-15 12:35:14 Error: 2019-04-15 1...

I don't think it's my server, honestly. I don't know what the issue is. It's behaving better since I have it updating once per minute rather than once every 5 minutes... but is still occasionally failing. And Boris has no helpful input on trying to troubleshoot. And not getting really any assistance...

mchd17 wrote: ↑Sat Apr 13, 2019 12:35 am sorry for late response, using mb to push to mt

sorry, I mean, are you using the weather networks function (in meteobridge) to push to API, or are you using a service (in meteobridge) to push?

Are you using the Meteotemplate "Weather Network" to push, or are you using a service?

running two nanos here, no problem. you sure you have api url correct? pw correct? maybe, disable mt upload, save, reboot nano. enable mt upload, save, see what happens. just saying things i would be trying. API is correct. PW is correct. It works "MOST" of the time, but randomly fails. I...

Can you elaborate anymore?

Hi All, I have a question that I've been working on for a bit and can't figure out. I'm using a Meteobridge Nano to update Meteotemplate. For months now, my MB has been throwing an error randomly saying "timeout in headers" for the API update (which happens every 5 minutes). I don't see an...