I'm also having som flatlining issues.

I just do not know if it's because of ssh tunnel timeout, or if indi_duino is crashing.
Not sure why it should, as all the values from the sensors are ok. No timeout or anything.

The MinMax error i somtimes have, but other times it's gone....

I now run it separate from the main indiserver

1013 ? S 0:20 indiserver_weather -f /tmp/indi_weatherFIFO -p 7625
1014 ? S 0:07 \_ indi_duino
root@heidenrod-obs:/# ll /tmp/indi_weatherFIFO
prw-rw-r-- 1 heidenrod heidenrod 0 Dec 28 18:08 /tmp/indi_weatherFIFO|
root@heidenrod-obs:/#

And I do not load it up in Ekos, this stops the flat lining, nor do I connect from my mobile phone using the indi app.

I see. You just start indiserver on different port, so you still can start the other drivers on default port?

I am testing with making a script thar runs @reboot via cron. This first starts indiserver with indififo. Then starts meteo, dome, wounderground and duscap. Then it opens a reverse tunnel to my webserver and executes. /startMETEO. sh

I have some scripts that i use to start indiserver with chaning. The server with meteostation is the last in chain, so as long as indiserver is started, those scripts works well.

I have been testing the last day or two. Mine flatlines even if I only connect to meteostation, so I'll have to do some digging

yes I can, the meteo station has it's own FIFO file and I run the server on port 7625.
Also done the following symlink which I use only for the metetostation, and updated the meteoconfig.py file to reflect the new names.

I think I found the issue I'm having.

I did not have correct settings for timeout in sshd_config

I added this

I tells the sshd daemon to send 0 Alive packages, and not to disconnect before atleast 1 Alive package is not returned.
Should keep the tunnel alive until I close it or reboot.

Fingers crossed

Btw. No clouds and no IRRadiance now? @Gonzothegreat

At the time I posted the screenshot, that was 100% correct. It was pitch black and zero clouds.
I had to go out with the family for a dinner, came back thinking I could deal with the polar alignment.... yeah right... clouds are back... typical.
If I cannot polar align the mount by Saturday night, the observatory will be closed for a few more months until I come back.

But I did found an interesting bug, despite the Clouds percentage being at 0 and the graph showing no clouds, there is the orange top light and the bottom bar saying clouds !!!

I've seen that to.

Looks like the flags are sometimes set wrong after a reboot. Not easy to test as my station is remote, and I cannot flash firmware remote.

In the meteosationWEB/mereoRRD_updater.py line 67-70 you haveSo it just checks the flags from the firmware.
Not sure if it's indi_duino or the firmware that sometimes gets this wrong.

At the moment, it does not bother me too much. I go with the percentage bar and the graph. But, once day I'll look into this and see if I can come up with a fix.
So far, this meteostation is a great addition and I believe many of us should have it as it's inexpensive to build.

One think that we could add is an anemometer to the board (like in the screenshot below).

And I still do like this layout but haven't been able to reproduce it:

from indilib.org/forum/general/2614-diy-all-sky-camera.html#19602

Yes. Wind speed would be great, as it can be dangerous for our flip top observatories with high wins!!

ID from weather.uwyo.edu/upperair/sounding.html. Example: my nearest ID is 11747 - Prostejov.

Edit meteoconfig.py:
I incorrectly entered the value of the nearest location (missing digits). When I fix it, she does not write in the log.

This worked on a table with Raspberry Pi 3 + Ubuntu Mate + breadbord.

Min Max Fail is still in the final set Raspberry Pi Zero W + Raspbian Stretch
I'm not doing it, it works too. In addition, there is a poorly readable font in the charts.

I have the same problem.