WL-ip (192.168.0.251) ,=> Meteobridge (192.168.0.48) => :22222 <= Meteohub (192.168.0.50)
Worked for weeks, suddenly, without any manual updates the Meteohub stops getting its data from the Meteobridge as the meteobridge stops reading the WL-IP. The WL-ip then is uploading to WL.com every minute AND is accesible using the Browser.
When removing the Meteohub from Meteobridges port 22222, the Meteobridge resumes reading the WL-IP.
The WL-ip then resumes its uploading every 5 minutes, and is nearly in-accesible by the browser, which is normal
Setting the Meteohub to connect again to Meteobridge:22222 stops the loading the data from the WL-ip again.
and so on, and so on.
Both the Meteobridge and the Meteohub upload no data to the outside world in that situation.
Both devices are rebooted, updated to the latest version, the Meteohub seems to think eevry time that there is a new build, but the number remains 7428
There are strange error is in the Meteobridge log: 192.168.0.50's 2nd request on port 22222 declined
Which results in errors in the Meteohub log: station 0 (Vantage), unexpected 0 bytes. disconnect station 0 (Vantage): response without data
=== meteohub log
logger (22.05.2015 12:46:15): station 0 (Vantage), data gap of 37 minutes, start reading Vantage's internal logger after 2015-05-22 12:05 (Vantage's local time).
logger (22.05.2015 12:46:16): station 0 (Vantage), internal logger provides 97 pages of data.
logger (22.05.2015 12:47:08): station 0 (Vantage), finished reading internal logger, 1 records inserted.
logger (22.05.2015 12:47:22): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (22.05.2015 12:47:22): disconnect station 0 (Vantage): read failed
logger (22.05.2015 12:47:52): connect station 0 (Vantage via TCP/IP).
logger (22.05.2015 12:47:52): station 0 (Vantage), unexpected 0 bytes.
logger (22.05.2015 12:47:52): disconnect station 0 (Vantage): response without data
logger (22.05.2015 12:48:22): connect station 0 (Vantage via TCP/IP).
logger (22.05.2015 12:48:22): station 0 (Vantage), unexpected 0 bytes.
logger (22.05.2015 12:48:22): disconnect station 0 (Vantage): response without data
logger (22.05.2015 12:48:52): connect station 0 (Vantage via TCP/IP).
logger (22.05.2015 12:48:52): station 0 (Vantage), unexpected 0 bytes.
logger (22.05.2015 12:48:52): disconnect station 0 (Vantage): response without data
=== meteobridge system tab log
logger (22.05.2015 12:45:52): 192.168.0.50's request on port 22222 accepted.
logger (22.05.2015 12:47:22): 192.168.0.50's 2nd request on port 22222 declined.
logger (22.05.2015 12:47:51): 192.168.0.50's 2nd request on port 22222 declined.
logger (22.05.2015 12:48:21): 192.168.0.50's 2nd request on port 22222 declined.
logger (22.05.2015 12:48:51): 192.168.0.50's 2nd request on port 22222 declined.
logger (22.05.2015 12:49:22): 192.168.0.50's 2nd request on port 22222 declined.
=== meteohub
Linux Kernel: 2.6.24 997 BogoMIPS, 248 MB RAM, ALIX.1D (500 MHz)
MeteoHub: 5.0i (Build 7248)©2015 by smartbedded UG (haftungsbeschränkt)
System ID: ********* activated
=== meteobridge
Platform:ASUS WL-330N3G (no USB hub)
RAM:29992 kB total, 3800 kB free (87% used)
SW Version: Meteobridge 2.5 (May 1 2015, build 2796), FW 1.0
Uptime:2 hours, 14 minutes Buffer Usage: 2 items (0%)
===
meteobridge does not read from ip logger after meteohub is connected top meteobridge
Sensor data remains the same, signal time increases only
Sensor Signal Metric Data Imperial Data
Outdoor 5 min 18.8°C 52% (dew 8.7°C, heat 18.8°C)65.8°F 52% (dew 47.7°F, heat 65.8°F)
Outdoor T #1 5 min 22.8°C 73.0°F
meteobridge with connected meteohub stops reading the WL-ip
Moderator: Mattk
Re: meteobridge with connected meteohub stops reading the WL
Is there another Meteohub/Meteobridge that tries to connect to the Meteoridge that reads out data from WLIP?
Re: meteobridge with connected meteohub stops reading the WL
There is no other device which want to connect to either the WL-ip or the meteobridge. Removing the meteohub by shutting it down, or giving it another IP address tolisten to, resolves the connection between meteobridge and the WL-ip instantly. When the meteohub is instructed to read from the meteobridge again it attaches, reads tge logger for the missing minutes and after that seems to connect for the second time.admin wrote:Is there another Meteohub/Meteobridge that tries to connect to the Meteoridge that reads out data from WLIP?
Wim
Re: meteobridge with connected meteohub stops reading the WL
i did another test,
1. waited half an hour so that the meteohub wants to read missed data from the logger,
2. then let Meteohub read the Meteobridge from meteobridge at 192.168.0.48:22222
Only Meteohub has the ip address 192.168.0.50 and only Meteohub is connecting to the Meteobridge.
logger (22.05.2015 21:08:10): open named pipe "/dev/meteobridge" failed: No such device or address
logger (22.05.2015 21:34:45): 192.168.0.50's request on port 22222 accepted.
logger (22.05.2015 21:39:01): open named pipe "/dev/meteobridge" failed: No such device or address
logger (22.05.2015 21:39:50): 192.168.0.50's 2nd request on port 22222 declined.
logger (22.05.2015 21:40:20): 192.168.0.50's 2nd request on port 22222 declined.
. . . multiples of the same content . .
logger (22.05.2015 21:42:50): 192.168.0.50's 2nd request on port 22222 declined.
logger (22.05.2015 21:43:20): 192.168.0.50's 2nd request on port 22222 declined.
logger (22.05.2015 21:43:50): 192.168.0.50's 2nd request on port 22222 declined.
And immidiatly when these messages come both Meteobridge and therefor Meteohub also stop receiving data from the vantage.
===
Stopped Meteohub after 6 minutes or so.
Meteobridge displays
ogger (22.05.2015 21:45:20): 192.168.0.50's 2nd request on port 22222 declined.
logger (22.05.2015 21:45:50): 192.168.0.50's 2nd request on port 22222 declined.
ogger (22.05.2015 21:46:19): connection on port 22222 closed.
logger (22.05.2015 21:46:19): unexpected 0 bytes.
logger (22.05.2015 21:46:19): disconnect station 0 (Vantage): response without data
logger (22.05.2015 21:46:21): open named pipe "/dev/meteobridge" failed: No such device or address
logger (22.05.2015 21:46:49): connect station 0 (Vantage via TCP/IP).
logger (22.05.2015 21:46:49): wakeup sent.
logger (22.05.2015 21:46:49): internal logger activated.
logger (22.05.2015 21:46:49): syncing.
logger (22.05.2015 21:46:59): gettime request sent.
logger (22.05.2015 21:46:59): time offset of Vantage: -1 minutes
logger (22.05.2015 21:46:59): eeprom request sent.
logger (22.05.2015 21:47:00): rain collector size 0.2 mm per tick.
logger (22.05.2015 21:47:00): transmitter 1 active as station type (#0) "ISS".
logger (22.05.2015 21:47:00): transmitter 2 active as station type (#1) "Temp Only" mapped to "t1".
logger (22.05.2015 21:47:00): transmitter 3 active as station type (#8) "Leaf/Soil".
logger (22.05.2015 21:47:00): firmware version request sent.
logger (22.05.2015 21:47:01): firmware version 1.90
logger (22.05.2015 21:47:01): no reading of Vantage's internal logger.
And Meteobridge is receiving the data again.
It can be repeated over an over again,
Will test tomorrow if the same situation occurs with shorter times between connect and reconnect when Meteohub does not want to read the logger for missed data.
Wim
1. waited half an hour so that the meteohub wants to read missed data from the logger,
2. then let Meteohub read the Meteobridge from meteobridge at 192.168.0.48:22222
Only Meteohub has the ip address 192.168.0.50 and only Meteohub is connecting to the Meteobridge.
logger (22.05.2015 21:08:10): open named pipe "/dev/meteobridge" failed: No such device or address
logger (22.05.2015 21:34:45): 192.168.0.50's request on port 22222 accepted.
logger (22.05.2015 21:39:01): open named pipe "/dev/meteobridge" failed: No such device or address
logger (22.05.2015 21:39:50): 192.168.0.50's 2nd request on port 22222 declined.
logger (22.05.2015 21:40:20): 192.168.0.50's 2nd request on port 22222 declined.
. . . multiples of the same content . .
logger (22.05.2015 21:42:50): 192.168.0.50's 2nd request on port 22222 declined.
logger (22.05.2015 21:43:20): 192.168.0.50's 2nd request on port 22222 declined.
logger (22.05.2015 21:43:50): 192.168.0.50's 2nd request on port 22222 declined.
And immidiatly when these messages come both Meteobridge and therefor Meteohub also stop receiving data from the vantage.
===
Stopped Meteohub after 6 minutes or so.
Meteobridge displays
ogger (22.05.2015 21:45:20): 192.168.0.50's 2nd request on port 22222 declined.
logger (22.05.2015 21:45:50): 192.168.0.50's 2nd request on port 22222 declined.
ogger (22.05.2015 21:46:19): connection on port 22222 closed.
logger (22.05.2015 21:46:19): unexpected 0 bytes.
logger (22.05.2015 21:46:19): disconnect station 0 (Vantage): response without data
logger (22.05.2015 21:46:21): open named pipe "/dev/meteobridge" failed: No such device or address
logger (22.05.2015 21:46:49): connect station 0 (Vantage via TCP/IP).
logger (22.05.2015 21:46:49): wakeup sent.
logger (22.05.2015 21:46:49): internal logger activated.
logger (22.05.2015 21:46:49): syncing.
logger (22.05.2015 21:46:59): gettime request sent.
logger (22.05.2015 21:46:59): time offset of Vantage: -1 minutes
logger (22.05.2015 21:46:59): eeprom request sent.
logger (22.05.2015 21:47:00): rain collector size 0.2 mm per tick.
logger (22.05.2015 21:47:00): transmitter 1 active as station type (#0) "ISS".
logger (22.05.2015 21:47:00): transmitter 2 active as station type (#1) "Temp Only" mapped to "t1".
logger (22.05.2015 21:47:00): transmitter 3 active as station type (#8) "Leaf/Soil".
logger (22.05.2015 21:47:00): firmware version request sent.
logger (22.05.2015 21:47:01): firmware version 1.90
logger (22.05.2015 21:47:01): no reading of Vantage's internal logger.
And Meteobridge is receiving the data again.
It can be repeated over an over again,
Will test tomorrow if the same situation occurs with shorter times between connect and reconnect when Meteohub does not want to read the logger for missed data.
Wim