meteohub.de

Thanks. Describing the behavior allowed me to mimic that behavior and find the actual problem. Sounds indeed the something changed in my provider because all my FTP paths were setup as absolute (starting with /) and had always worked until then. Removing the initial slash fixed the problem.

I had not paid attention closely so don't know when this started exactly, but I am observing problems uploading files through FTP service. It seems that last successful upload happened on Sep 29.

I noticed this for a configured service to upload a template based file:
Every minute:
- Template: http ...

Come on, when your consumer-market station shows 1234 also 1250 or 1200 can be right for solar radiation (if you are lucky). I can't believe that you really want to discuss rounding vs truncating with me given that error range. :roll:

I do not question the fact that a station may deliver more ...

You conveniently skipped over the truncation vs rounding issue.

As far as usefulness of decimals, that would be a matter of opinion (and therefore perhaps left to the end-user), and you clearly state your's although it is not like rolling dice. These decimals, while arguably insignificant in the ...

I noticed something strange today and investigated. Setup: Ambient ObserverIP connected to MB running 3.2 (latest version of that).

I see that the ObserverIP is reporting solar radiation values in its Live Data page (where MB gets its information) with two decimals and those decimals are often non ...

It happens sporadically enough that even if I would catch it in the act, by the time I would get you alerted and give you access, the situation would be gone again.

You speak of inspecting packets, but as far as I know MB is just "scraping" the live data and station pages. I understand that still ...

I understand that, but it does not seem to show all evaluations, or at least the raise condition is not evaluated as often as the clear condition. Why?

The ObserverIP software uploads directly to WU and, as you already noted, that did not have the problem. It seems you correctly implicated the MB, or at least the interaction from OIP to MB.

Based on my own observations and others who have reported this same problem, I very much doubt this will ...

The full raise condition: I simply left the second part out as it does not seem relevant, but there it is. The log shows that overall raise condition to evaluate to false.

I have created an alarm condition like this to raise: fabs([th0temp-age:999]-[thb0temp-age:999]) >= 100 (don't ask why), and the corresponding condition for clearing the alarm is: fabs([th0temp-age:999]-[thb0temp-age:999]) <= 3

When I go to the "Services" tab and hover over the orange "i" box I see ...

Notice that the temperatures you are seeing are the values you would get if you take your true temperatures (in F) and convert them as if they were in C to F.

I've seen this happen, on occasion, but never for the longer duration, when you change the settings on the ObserverIP from F to C ...

I am logging my values to a personal server every 15 seconds using an HTTP get "service". The lines contain both values from primary sensors (e.g. th0temp-act) as well as averages etc. I see lots of lines that have duplicates as far as primary sensors is concerned.

Does this mean that the "not ...

I think I figured out why I was always getting 600 s when the sensor indicated invalid, and the observations might be helpful for those of you who would like to tinker with alarms on MeteoBridge. If you don't care about the how I discovered it, the conclusions are at the end.

I think MeteoBridge ...

I am not so much interested in the exact format of the strings, but rather what MeteoBridge variables and with what defaults and formatting are being sent for each service. Even if the actual sending is not done using a template, it should be possible for Boris to tell us in the language of the ...

I started logging some of the ages of my sensor data earlier tonight and noticed something peculiar right after I rebooted my ObserverIP (columns are: time, th0temp-age, thb0temp-age, thb0seapress-age, mbsystem-lastdata, mbsystem-lastgooddata):

06:46:12 90 90 90 34 90
06:46:29 9 9 9 9 9
06:46:47 ...