Meteohub and Weather Display

[dpalin]

I have two different Meteohub setups both connected to WMR200 with a few temperature sensors on each. For the most part everything is working with one exception that I have never been able to resolve. I am not sure if it is a weather display problem or a meteohub problem.

My temperature is stuck at 51.3 F, eg my outdoor temperature in Weather Display which stays at this temperature and is always red. I know that Meteohub is getting the temperature from the WMR200 just fine

I suspect there is some mapping in Meteohub or Weather Display that I am missing. Though I have set this in the "WD Data Export" which I had assumed was the correct location.


Any help appreciated.

[skyewright]

I suspect there is some mapping in Meteohub or Weather Display that I am missing. Though I have set this in the "WD Data Export" which I had assumed was the correct location.

If you are using the "logging protocol" based communication between Meteohub & WD, then the "WD Data Export" page is not relevant (that page relates to export of WD style log files).

What sensor names do these sensors have in Meteohub?

When WD reads data via the logging protocol it is looking for th0 as the main outdoor tem/humidity sensor.

That can't be changed at the WD end. If your outdoor sensor does not use th0 in Meteohub then you must either change your sensors ID's, use a virtual sensor or (much more complex) do what I do which is run an Apache server on the WD computer and have a perl script that sits between WD & Meteohub so that I can manipulate the Meteohub output using regular expressions before WD sees it!

Few people would want to go the Apache/perl route nowadays, it was something I set up "in the early days" long before virtual sensors were available.

PS. WD can also recognise th1 to th9 as for other temp/humidity sensors. Temp only senors, e.g. t1 are also recognised, but make sure you do not use both types with the same number, e.g. t1 and th1 as that will cause confusion as WD will log both temperatures as being for the same sensor!
Something else that can cause confusion in WD is if you have th (or t) sensors with numbers > 9, e.g. th10. WD only los at thge first digit so it sees th10 as another th1! It's possible that this may have changed, but I last checked it not very long ago. My workaround for that it is that my perl script removes such sensors from the Meteohub output (that's okay for me as I don't want them logged in WD anyway).