meteohub.de

Meteobridge conversion from mm to inches is incorrect. This can be tested during any rain event by entering the following alarm:

RAISE: [rain0total-sum24h] > 0
BODY: [rain0total-sum24h=in.01] should equal {*[rain0total-sum24h]/25.4*}

The result In my case? "2.0 should equal 2.04"

That's the choice you can make as a developer when you move to a subscription model: support existing customers, or require them to pay up to get your bugs fixed. It introduces some interesting financial incentives for developers to introduce annoyances that the customer can only fix by paying - a ...

Last night something happened (still don't know what) to cause the Meteobridge to record the following for about 45 minutes:

Bad th0(0) sensor data, "humidity" (255) out of range [0:100]

The bigger problem is that Meteobridge sent 0°F to WeatherUnderground for temperature and humidity values ...

Pay to get someone to look at bug? No thanks.

Something is unequivocally wrong with [rain0total-sum24h]. It started drizzling about 01:00 (first bucket tip recorded). By 03:34 two more tips were recorded for a total of 3 tips (0.03 inches). At 04:00 I received my email from Meteobridge reporting [rain0total-sum24h]=0.0.

Here is the one-time ...

Rain total from the previous day or the current day is not sufficient for my use case. I need to know, at 4:00 am, whether any rain has fallen in the previous 24 hours, and how much.

If there error were due to timezone I'd have to be living in a timezone with 72 hours in one day.

I'm counting the number of rain bucket tips between 4:00 am and 4:00 am. Besides, there's no way to get it as wrong as it was. The cumulative rainfall over the three previous days was the same as the total reported on the last day for 24 hours.

[rain0total-sum24h=in] can be wildly inaccurate. I have a one-time alarm that triggers every morning at 4:00 am just to email me [rain0total-sum24h=in]. The email value is often wrong. For example, today it reported 1.0, but the actual rainfall recorded by the Meteobridge and the Davis console is 0 ...

I had a power outage this weekend and when everything came back up my license was gone and the license page was telling me that my license had expired two years ago and that I need to pay 19 Euros to continue. I've had at least 6 power outages in the last two years and never received this message ...

If that doesn't help me, I don't know what can. My only concern after that would be tasking Meteobridge with an alarm condition as complicated as:

(((10*(([th0temp-val1=F.1:999]*1)+([th0temp-val2=F.1:999]*2)+([th0temp-val3=F.1:999]*3)+([th0temp-val4=F.1:999]*4)+([th0temp-val5=F.1:999]*5 ...

I am trying to develop a rule that will raise an alarm when the temperature starts climbing from the daily minimum, but I don't want to catch every minor up and down. Ideally I would just take the temperature readings from 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 minutes in the past and use linear regression ...

The raise condition from alarm #1 is pasted to the clear condition of alarm #2 and vice versa. I did discover that the alarm was raised, but for the first time in over 1,000 email messages from meteobridge over the years Google marked it as spam.

I am still having issues with alarms not triggering when they should.

I have two alarm conditions, each compliments of each other. The raise condition on alarm #1 is identical to the clear condition on alarm #2, and vice versa. Whenever alarm #1 is raised, alarm #2 should be cleared at the same ...

This can also be caused by cheap Ethernet cables, especially if they're located near the antenna feed for the radio. If you can locate some shielded cables that may help. Unplugging the Ethernet cable while the meteobridge remains powered on should tell you if it is the culprit.

I downloaded a table of altimeter and SLP pressure readings from a nearby airport and compared them to the values reported from my station by meteobridge to CWOP and WU. If I am correct meteobridge reports altimeter pressure to CWOP and SLP to WU. The problem is that the offset for each is different ...