Version 2.6 intermittent loss of signal **solved**

[steve-invest]

I moved my meteohub, which caused a reboot and an upgrade to version 2.6. Soon afterwords I noticed intermittent periods on Wunderground where there was no data coming in, lasting in periods from 5 to 20 minutes. At first I thought is was because I moved the unit, but it looked like a better spot than the old one and was close to the Davis console that gets the signal quite well. I looked at the log and I was getting this message during the same times that meteobridge was not recording ISS data.

(Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory

I went back to version 2.5 and the problem disappeared. I think there is a bug in 2.6, or there is a parallel upgrade to the meteostick interface that I don't know about.

[admin]

I have 2.6 running fine with the current Meteobridge image. Could you please
enable remote access as described here: viewtopic.php?f=57&t=9885

Please send URL and password to "info(at)meteobridge.com".

[steve-invest]

I will try it again and see if happens again. My first inclination is not to send passwords to something connected to my network. If the problem returns, I will go back to version 2.5 and wait for 2.7. Either way, I will post the result of my experiment, for the enlightenment of others.

[admin]

My first inclination is not to send passwords to something connected to my network.

My idea was more that you set it temporarily and set it back when my inspection is done.
But it is also totally OK not to give me access to your Meteobridge. That's your free decision...

I just just wanted to help and having access to your Meteobridge makes this so much easier instead of guessing around based on some symptom descriptions

[steve-invest]

I appreciate that. I switched back to version 2.6 and it worked fine for several hours, but then the problem started up again. We switched back to version 2.5 and the problem went away. For now, I will just stay with 2.5 and look for further updates. I posted this in case I am not the only one with the problem and I can help someone else.

[steve-invest]

Maybe it was a coincidence, because it ran for 11 days on version 2.5, and now is not picking up the outdoor signal at all for long periods of time. At this moment, it is, but a few minutes ago it was not. I moved the version back to 2.6, since 2.5 didn't seem to be helping.
I would send you password info, as you requested, but I see that that service seems to be down.

Right now it is getting this. (Maybe the signal data might help)
Live Data
Sensor Signal Metric Data Imperial Data
Indoor 3s 44.1% 18.8°C 30% 1000.5hPa (957.1hPa) 65.8°F 30% 29.55inHg (28.26inHg)
Leaf #16 29s -78db 0.0°C 0wet 32.0°F 0wet
Soil #10 43s -89db 8.7°C 21cbar 47.7°F 21cbar
Soil #11 8s -81db 0.0°C 29cbar 32.0°F 29cbar
Soil #12 6s -80db 0.0°C 0cbar 32.0°F 0cbar
Leaf #15 1s -86db 8.7°C 0wet 47.7°F 0wet
Soil #13 3s -85db 0.0°C 0cbar 32.0°F 0cbar
Rain 3m -87db rate 0.0mm/h rate 0.00in/h
Outdoor 59s -87db 4.4°C 89% (dew 2.7°C, heat 4.4°C) 39.9°F 89% (dew 36.9°F, heat 39.9°F)
Wind 20s -90db 3.8m/s (avg 6.8m/s) 0° N 8.5mph (avg 15.2mph) 0° N

Also here are the most recent system messages since the last time I rebooted. Any suggestions?

netd (11.11.2015 20:20:05): process started.
logger (11.11.2015 20:20:08): Historical data loaded (47 records).
logger (11.11.2015 20:20:08): data logger (version 5.0l, build 7564) started.
logger (11.11.2015 20:20:09): connect station 0 (Meteostick Vantage via USB serial).
logger (11.11.2015 20:20:10): transmitter 1 registered as ISS
logger (11.11.2015 20:20:10): transmitter 2 registered as Leaf/Soil
logger (11.11.2015 20:20:10): Meteostick Version 2.3b2
logger (11.11.2015 20:20:10): debug off
logger (11.11.2015 20:20:10): verbose off
logger (11.11.2015 20:20:10): output raw (8 bytes)
logger (11.11.2015 20:20:10): output raw (10 bytes)
logger (11.11.2015 20:20:10): filter on
logger (11.11.2015 20:20:10): rx threshold set to -90db
logger (11.11.2015 20:20:10): listening to transmitter 1 2
logger (11.11.2015 20:20:10): bandwidth narrow
logger (11.11.2015 20:20:11): chip authentication ok: 40
logger (11.11.2015 20:20:11): frequency band 915MHz (US)

[admin]

When you reboot again, Meteobridge will load a new SW version which should allow me to login (having URL and password).

[steve-invest]

Well, I was successful in destroying my entire system . I changed the password, but have no idea what the user ID is. It doesn't respond to the default value, and it doesn't respond to the same user ID as the password. Either that, or somehow typed the new password in the same wrong way twice.

[admin]

Wiki explains in "Getting Started" section near the end how to set it back to default password. User is always "meteobridge".

When you have misconfigured the network or system password in a way that you can't no longer reach Meteobridge, you can revert the system back to defaults by pressing the button on the top of TL-MR3020 / WL-330N3G or on the side of DIR-505 or the reset button of TL-WR703N / TL-MR3040 at the back behind a pin hole. By pushing these buttons (during normal Meteobridge operation, not during boot) you can revert to defaults in three ways.

1) Reset to default network operation is done by pressing the button and keeping it pressed until LED goes on again for the first time. Now release button and system will restart with default network configuration, which is LAN DHCP client mode. Network settings done before are still stored inside Meteobridge when unit has started in LAN DHCP client mode, but these will need additional "Save" clicks to be made active again.

2) Reset password is done by pressing button and keeping it pressed until LED goes on for the second time. Meteobridge will reboot and will be available with default password via ssh (user root, password meteobridge) and http (user meteobridge, password meteobridge).

3) Reset to factory defaults is done by pressing the button and keeping it pressed until LED goes on again for the fifth time. This will delete all user settings changes made to the file system of the unit. Stored historical data will be erased. License will remain untouched. Unit will reboot automatically with default network settings and password.

[steve-invest]

Thank you, I appreciate that. One thing I should note in the directions is that the light turns on before 10 seconds. The button is a WPS button unless it is pushed for 10 seconds. After I found that out, I was able to reset it, although I am not sure why I hadn't been able to use my new password. Oh well.


This is now a poorly named topic. I agree that it doesn't have anything to do with v 2.6. It was just a coincidence that my problem started at the same time that I updated to 2.6. The problem went away for about 10 days, but now it is to the point that the loss of signal is not intermittent, the signal itself is now intermittent. I continually get the following error:

logger (14.11.2015 09:30:45): restart meteostick (332 secs no valid rf signal)
logger (14.11.2015 09:35:46): restart meteostick (301 secs no valid rf signal)

I have now put it back it the same place that it worked for over a year, but no better results. Maybe there is a hardware problem with the meteostick.

If I can figure out how to make the login from the internet work, I will send you the info.

[steve-invest]

I was given some advice to raise the noise threshold. The problem slowed down (much more up time than down), and now seems to have gone away.

[admin]

A location away from all the other IT stuff also helps to ban RF noise.

[iatros]

Hello all
I'm new to meteohub and have the problem that temperature und humidity graphs (and only those!) often are showing gaps in the signal transmission, cf screenshot.
I do not see this problems on the console, and I changed the place of the MeteoStick xesveral times without improvement.
Do you need more indications to help me?
thanks in advance
Martin

PS: The gap in pressure graph is due to a change of place of the MeteoStick

[chrysnic]

Hi all,

I also have the same gap problem (as user iatros above) with the temperature and humidity graphs on Meteoplug. The gaps appeared when I started using a Meteostick attached to my Meteobridge (before that, the Meteobridge was configured to read the data directly from the WeatherLink IP module over the network).

I have recently upgraded to a Meteobridge PRO (red), and I get the same gaps when using the built-in RF receiver.

I am not sure, but this may be a reception issue with the th0() sensor (which reports the outdoor temperature and humidity), because there are, indeed, missing th0() values when I inspect the data on Meteoplug.

Any help would be appreciated.

Thanks,

Chrys

[chrysnic]

Update: After updating to the latest version of the system software, the gap issue has been fully resolved. I have been using the latest version for the past 48 hours, and there are no gaps in either the temperature, or the humidity, on Meteoplug.

Thanks for resolving this issue.