WXforum.net
Weather Station Hardware => Ambient Weather and Ecowitt and other Fine Offset clones => Topic started by: CColotti on December 27, 2014, 01:56:04 PM
-
Often I look at the remote unit and all things are online except the "server" light. I then get notifications from WUnderground my unit has not reported in. I have very solid internet access on every other device, but what can cause it to disconnect from the server connection?
-
Possible the firewall/router and/or ISP is blocking the port 5000? That is about the only thing that makes sense as to why the server would not be connected. I guess you could also have a bad unit but I would think that other things would show up.
Does your router logs show a connection such as the below? That should be the connection of the IP Observer module. Could also say port 5000 as well.
internal external host or port
192.168.1.15 38.102.136.125 www
-
Nothing outbound is blocked and it works for some time then stops reporting...if it were blocked it would never have connected for sure in the first place i'd think. I control my own firewalls and I don't block anything outbound
-
Run a wireshark capture and see what it says if its actually making it to the server when it says its down.
-
I think that was going to be my next thing for sure...don't want it to keep fluttering
-
This is what I keep getting this message every couple days...
The Weather Underground PWS network has detected that your personal weather station (ID #KTNGREEN16) has not reported to www.wunderground.com in 2 hours hours. Please check that your station is operational by visiting your station's settings here: http://www.wunderground.com/wxstation/signup.html For more details and information about troubleshooting visit our PWS wiki page: http://wiki.wunderground.com/index.php/PWS_-_Personal_Weather_Stations We want to ensure that you are informed on the status of your weather station so you can continue to receive accurate data from Weather Underground. - The Weather Underground Staff
So it IS reporting then quits....very annoying!
I assume all traffic from the IP unit is outbound only...so why does this keep happening?
-
Now the unit has no lights on except the power and link/activity but I cannot get to it and cannot find it with IP tool scanner.....time to call ambient weather I guess and get a replacement.
-
That sucks, hopefully the new one fixes the issue.
-
Well AW helped me re-flash from scratch and it's back...for now...LOL
-
Similar experience.
I've had my WS1400 for about two weeks now, and a day ago I got an email that it is not sending data.
I looked at the LAN unit, all lights looked fine, I tried to access it via IP, no response.
Power cycled, and it could connect, and a while later I could see WUG is again reporting data.
Already running the latest 1.0.9 software.
Any ideas?
P.
-
I've been helping the developers work on this. A firmware update is pending that could solve it. We discovered the device was susceptible to TCP broadcasts on the LAN causing it to go offline when the network it is on is very chatty. Hoping to see the new firmware in a week. They have been very good about using my data collected on my network to find the root cause and reproduce the problem.
-
I just installed the 2.0 firmware, hope it fixes the issue.
-
There is another minor one pending...the unit may have a memory leak they are sending me another to test this week. :)
What I can say is they have been great about listening to the issue....not just saying it's my network.
-
I've been testing the 2.1 updated that is pending and the latency is much improved and I've not seen any disconnects from the servers. Expect another update release, there is a minor UI bug on the station ID screen. I'm just glad their developers LISTENED to me!
-
I just installed the 2.0 firmware, hope it fixes the issue.
It should be better but the 2.1 update will fix a memory leak that was also affecting the connectivity of the unit.
-
I just updated to 2.1,and there is something wrong with the station config.
After update station is blank, I enter station name and password, click save, and then station changes to "0000000000 maxlength="
Reverting to 2.0 fixes the problem.
Anybody else experience this?
-
I have exactly the same issues about the observer IP disconnecting from server. All lights are ON EXCEPT for the SERVER light.
It usually happens about 4 or 5 days of the latest reboot. I've already updated to firmware 2.0 but still same issues.
When tried with 2.1 I saw the same thing as ptr727 after setting the station name and password:
The station name would reset to "0000000000 maxlength=".
Any clues? Is there some issue with firmware v2.1 or a new release date for a stable build of it ?
Regards
Diego
-
AW support told me that the person working on the firmware is on vacation...
-
I just updated to 2.1,and there is something wrong with the station config.
After update station is blank, I enter station name and password, click save, and then station changes to "0000000000 maxlength="
Reverting to 2.0 fixes the problem.
Anybody else experience this?
I set up my WS1400 week before last & had updated the firmware before I saw this.
Mine did the same thing but the station name took the third try & I haven't had any issues since.
-
I lost power to my router and ObserverIP yesterday and couldn't for the life of me get it to link back up. I then flashed it with v. 2.1 and it has been working well since. I'm a little afraid to disrupt the power to check to see if it will boot back up on its own but am hopeful it will. This is the first hiccup with the 1400 but am glad to hear that the Ambient Weather people seem to care. That is a big deal for me!
-
When tried with 2.1 I saw the same thing as ptr727 after setting the station name and password:
The station name would reset to "0000000000 maxlength=".
Make sure you do a reset by pressing the little reset button on the observerIP. I had the same problem as you till I read the instructions again.
On a different note, this changes the update interval to WU from 16sec to 30 seconds. The refresh interval of the observerIP stays at 8 seconds so I wonder why they did that. I wish they would mention things like that in the release notes :roll:. Another thing I have observed is that it takes the observerIP much longer to sync with my indoor and outdoor stations after the update. I might just revert back because I don't see any value in this update so far as I had no connection problems previously.
-
On a different note, this changes the update interval to WU from 16sec to 30 seconds. The refresh interval of the observerIP stays at 8 seconds so I wonder why they did that. I wish they would mention things like that in the release notes :roll:. Another thing I have observed is that it takes the observerIP much longer to sync with my indoor and outdoor stations after the update. I might just revert back because I don't see any value in this update so far as I had no connection problems previously.
Oh ratz.. This explains a lot about why it is taking much longer to update WU with 2.1. Also noticed that it took a LONG time before it finally linked up with my indoor sensors! New and improved isn't always so... :roll:
-
Since it is a windy day here, I was comparing the wind data posted on WU vs the actual live data (which was much higher) & I had a 20+ min drop-out on WU.
On the live data page I happened to notice that my "receiver time" had dropped an hour back & on the "table" version of WU for my data, that time of day had of course, passed. I re-set the time an hour off to get the correct local time & the reports to WU immediately started again. The "daylight savings" button is on. The time has not been reset (by me) since it was set up more than a month ago.
Possible software issue? And maybe related to other's station dropouts?
I am running V2.1 with no real problems so far.
-
I'm late to the party but this problem still exists for me. Using latest firmware version 3.1.
-
You can see what I did here:
http://www.wxforum.net/index.php?topic=29804.msg293360#msg293360
To make a long story, short:
1. I created a telnet batch file which logged in and reboot every xx hours; I used 4 since it only takes the device <30 secs to come back online.
2. I created a couple meteobridge alerts that would send me a text to reboot if it stopped sending data. I have since modified this and added a WeMo switch, and IFTTT which power cycles the device if this occurs.
In the long run it seems the better option is a meteostick, but I am good to go now.
-
I have this problem on 2 different units installed on 2 different routers using 2 different ISPs and 2 different facility carriers. One of the units disconnects from the server at least 3 times a day and the other unit disconnects once or twice a week. I have 2 additional units I have not installed due to the issues I am having on the installed units.
I have the Observer IP Receiver connected wirelessly to my router (approximately 3 feet separate the router and ObserverIP). The ObserverIp Receiver is on release 3.1.0. I have a Meteobridge connected to the router via Ethernet to send the data received to my SQL database. The event log has this entry "child process received timeout signal".
To correct the situation, I power down and up the ObserverIP Receiver and then I restart the data logger in the Meteobridge.
I install and maintain all equipment which includes the routers.
-
I thought I was clever writing a batch file that reset the network interface over the network. It worked great until the problem actually cropped up. I didn't think about the interface not even getting the commands when it was acting up. So I ended up buying a timer to electrically reboot the interface whether it needs it or not. 20 times/day it turns it off then a minute later back on. Works for me.
-
Great idea to restart the power on the ObserverIP! Now I have to figure out how to restart the event logger in the Meteobridge. My plan is to have as many as 15 to 30 weather stations, scattered around the United States, reporting information to my SQL database. If my database does not receive data within 15 minutes, then the database sends an event report to me or someone in my organization. The weather station sites will have people available to do work, at my command, on the weather stations.
I think I really need to have a solution to the problem or choose another, more reliable, weather station.
-
Hmm!now pass 2 weeks with the ip observer 3.1.0 version works so well
A few months ago i used a plug timer to restart the observer but a lot of times the.outdoor sensor signal lost.now 2 weeks ..i only restart the router..and looks i find the solution of my problems...i hope
-
My WS-1400 IP Observer dies for second time in 2 weeks. It runs 3.1.0 firmware and connected to Meteobridge. After the first hung, I put a smart plug on it. Now when I got an email notified the Observer is stopped, I just power cycle remotely.
Thinking of set the timer to do it 3-4 times a day.
Kanok
Sent from my iPad using Tapatalk
-
It is interesting to note that this has been a thread since back 2014. Until Jan 30,2017, I have never had a problem with my unit. Now the server light is out, no reset, repower, nothing will get it to come back on except during power on sequence. I have two units, one is a new one replaced last summer after a hail event here in north Texas. The other one was put in service about three years ago. The older one has v3.0.3 firmware and the newer one has v3.0.5. But they both exhibit the same problem. WXunderground used to email me when I wasn't updating but that did not happen this time. My webcam photo makes it ok, just no wx data. The wx station itself is working fine because I can log into it with the static ip that I have assigned to it. But of course, I can not log in using my "no-ip.org" address. I can log into my security cams remotely using the "no-ip" address.
I am waiting on a call back from Ambient. But I hope someone out there in weather land has the answer.
kentm
-
Hmm i've just read on wikiambientweather ,there a problem with the wunderground server.My ipobserver didn't upload data since 31 january,looks the server problem appears on this day.Now the instructions be use DCHP instead IP static and reboot ip observer and router.This night i hope my ip observer upload again.
-
I updated my ObserverIP FW last week and have been experiencing similar disconnect issues. What's really strange is that the ObserverIP sends data to WU except for my pressure. The pressure data on WU is very sporadic. I do notice the server LED flashing or not on for periods of time.
Then to confuse the issue even more, my WS1001 is consistently connected to WU and sending all data?
-
This is really weird. The Ambient website says they are changing servers and they also tell about changing to DHCP. I tried all that but it still isn't reporting. Stations all around my area are reporting at this very moment but mine is not. Calls to Ambient are unanswered and unreturned. Can some one tell me where to find the 3.1.version of the firmware? I have checked the "downloads" page but I must be overlooking it if it is on that page.
Kent
-
Sorry , but I was overlooking the FW. I have it upgraded but it made no difference whatsoever. Station still not reporting..
-
i update with this las t firmware http://www.ambientweather.com/wswsfiup.html
Yesterday due the wunderground problem i had change the static ip to DCHP of my ip observer,since that upload data without problem.
Sometimes the ipobserver stop for reason that i donīt know,then i use a smart plugg to turn on/off the ipobserver until works ok
-
Hi all - Related server issue perhaps.
I installed my brand new WS-1400-IP over the weekend, registered on WU & put the WU credentials into the interface module, noted the "it will take a day" message on the WU web site for the PWS and WU to get along, have waited over a day, and .... nothing.
All of the lights on the interface module are "on" EXCEPT the server light (is this right?) I am connected to the internet via Frontier (was Verizon) FiOS, kept DHCP on the interface module (Version:3.1.0), status web page looks good on the interface box, and have even set forwarding port 5000 to the interface module.
Does anyone know the WU server address so that I can do a ping / tracert? Anything else to try? Are we all caught in some sort of WU outage?
Thanks in advance!
-
I think we are in the middle of some sort of outage but it is difficult to explain. My newly replaced WS1400 ip quit working on the 30th of January. There is a note on the AMB WX website about WU server issues. Also the note about switching to DHCP which makes no sense to me. I use a static ip so that I can access my station with a "no-ip.org/port" address. If you can't assign a port to a static address, how is it supposed to work. The other weird thing is that other stations in my area are reporting but I don't know what their equipment is. I can't help with an ip for the server as I also thought it would be nice to be able to "ping" it.
Very disappointing..
Kent
-
The last firmware is 3.1.0 ..i hope the next update let us use a static ip instead DHCP..is weird the.problem of the last week....
-
FWIW ... getting a bit of a run-around from Ambient (blames the WU change to AWS) and WU (tells me to contact Ambient). Not a very favorable first impression. My PWS will end up back in the box and sent to Ambient for a refund if not resolved soon. sigh.
-
Of course I had to write something for my status to change ... one thing seemed to work:
I changed the DNS server on my router (over-rode to OpenDNS) - and the server light turned on, and my WU PWS page has started to update for the first time.
So something odd going on in DNS propagation land. I have now turned my DNS back to my Internet Provider ... let's see how it goes.
-
Of course I had to write something for my status to change ... one thing seemed to work:
I changed the DNS server on my router (over-rode to OpenDNS) - and the server light turned on, and my WU PWS page has started to update for the first time.
So something odd going on in DNS propagation land. I have now turned my DNS back to my Internet Provider ... let's see how it goes.
I looked at my router but I can't find any place to change the DNS server. I am using frontier fios as an isp but haven't had any issues until this one with WU. Is your ws1400ip set to DHCP now?
-
I looked at my router but I can't find any place to change the DNS server. I am using frontier fios as an isp but haven't had any issues until this one with WU. Is your ws1400ip set to DHCP now?
- My router has a place to over-ride the ISP DNS server in advanced settings (i do not have the standard frontier router)
- I am frontier FiOS too; maybe there's an issue with the replication in the frontier DNS server
- Yes, my interface module has been set to DHCP the entire time; i re-boot it whenever i change DNS servers
-
- My router has a place to over-ride the ISP DNS server in advanced settings (i do not have the standard frontier router)
- I am frontier FiOS too; maybe there's an issue with the replication in the frontier DNS server
- Yes, my interface module has been set to DHCP the entire time; i re-boot it whenever i change DNS servers
I am still using the Actiontec MI424WR, but I just can't fault that unit for this issue. AMBWX/ WU admits server changes and recommends the use of DHCP but their tips do not work for me. I can not log into my station using my no-ip/port name but I can log into all of my security cams with no problem. It still puzzles me as to why others around me are still reporting.
-
kentm: May want to try this to change to OpenDNS ... then, if your PWS connects to the server, switch DNS back to the Frontier default after a while ... https://support.opendns.com/hc/en-us/articles/228008027--Verizon-FIOS-Actiontec-MI424WR-and-Westell-UltraLine (https://support.opendns.com/hc/en-us/articles/228008027--Verizon-FIOS-Actiontec-MI424WR-and-Westell-UltraLine)
-
Thank you for the information. I have reset the router as per the instructions and set the obersrverIP back to DHCP. Now I will just sit back and see if it ever reports.
Thanks again
-
Still no luck for me. I am about out of ideas. I sent another ticket to AMBwx. I can ping wunderground.com and others with no issue so I just can't imagine what happened here. I still think it remains with the server changeover that occurred at the same time.
"What's a mother to do?"
-
(...) "What's a mother to do?"
Read from this thread down (http://stacjepogody.waw.pl/index.php?topic=2053.msg15603#msg15603)
And here you have a solution (http://stacjepogody.waw.pl/index.php?topic=2053.msg15689#msg15689)
The same problem was above writing user.
This applies to weather station WH2600. It is a twin 1400IP.
She helped only replacement router - as the user wrote.
;)
-
I would love to read this reply but I don't know Polish or how to translate it...
-
I would love to read this reply but I don't know Polish or how to translate it...
Read from this thread down (https://translate.googleusercontent.com/translate_c?depth=1&hl=pl&rurl=translate.google.pl&sl=pl&sp=nmt1&tl=en&u=http://stacjepogody.waw.pl/index.php%3FPHPSESSID%3D837c24172cf811fc049d9619312ad3d6%26topic%3D2053.msg15607&usg=ALkJrhjl-W6lEcPig5yZFalpTfyOsa29_Q#msg15607)
And here you have a solution (https://translate.google.pl/translate?hl=pl&sl=pl&tl=en&u=http%3A%2F%2Fstacjepogody.waw.pl%2Findex.php%3Ftopic%3D2053.msg15689%23msg15689)
May be ? ;)
-
Problem solved. In all this server/transfer ,reboot, update etc. I entered the wrong number in the station settings regarding Station identifier. While it says password, that blank really means "station Key" . I am back on the air now.
Thanks for the complete assistance provided by Ed at AMB WX.
Kentm
-
Version 3.1.2 fixed my problems while working with a static ip address.
From the ambient website, it looks WU switched over to cloud based servers and their may be some stale DNS data.
-
Same for me also. Downloaded and installed 3.1.2
Static IP now working...
-
Updated to 3.1.2 and changed to a static IP. Rebooted, now my server LED isn't on and no data going out?
Also, when set on DHCP, all data is being sent except for my pressure? It appears in my table randomly?
-
Hi all,
I think i may have figured something out (after some WireShark sniffing). My theory: a DHCP refresh does not update the DNS server IP address used by the WS-1400-IP. Static IP should work. If you use DHCP and are having server disconnect issues, try this. In the Local Network tab, set the IP Address pull-down to Static, then fill in the fields as appropriate - Static IP Address is the address shown in your web link, subnet mask should not need to change, default gateway is usually your router IP, and (important) set the Static DNS Server to what your router is using (or your router itself if your router caches DNS). If you don't know your default gateway or DNS server, open a command prompt in Windows, type "ipconfig /all", and look for "Default Gateway" and "DNS Servers". Once entered do Apply, Reboot (maybe not necessary). After reboot go back to the Local Network tab and see that the Static DNS Server value is the one you entered. Re-set the IP Address pull-down to DHCP then Apply, Reboot. If my inkling is correct, all should work. Pls report ...
-
of note: my above condition is claimed to be fixed in firmware update 3.1.6 (have not verified)
-
Hi all,
Have recently purchased a WH2600 PWS from China, (as I live in Australia and the US purchase sites did not seem to do overseas postage). I believe this is the same product as Ambient Weather's WS-1400-IP Station. I have the same server light issues, have followed this entire thread and tried everything suggested to no avail. Have upgraded the IPtools firmware to the latest Ambient Weather observer IP3.1 Version 3.1.6 and have noticed that in the live data tab, the receiver time says: XX:XX 00/00/2000 regardless of what time zone I input in the stations settings tab. and still no server light on the ObserverIP. This is starting to do my head in. Do I contact the supplier and ask for a new ObserverIP device or am I missing something? PS. I have checked my Weather Network details several times to make sure they are right...please help if you can.
-
I've been working with Ambient and Fine Offset on this and other issues.
Your symptoms are indicative of a failed connection to wunderground.com. It means you either did not configure a stationID and password at all, or what you specified is incorrect, or the ObserverIP does not have proper internet access.
Only if there is a successful upload of your data to wunderground.com will the unit's time be updated (and the server light be on). I am working with them to get that changed, but for now you're not getting the correct time indicates exactly what I mention.
The first thing is to check you specified the wunderground stationID and password. If you did not, there is your explanation. Assuming you did, however, a simple way is to go to wunderground.com and confirm there that you are not getting your data uploaded.
If you are convinced setup is OK, and if you really want to know for sure and in detail, you could use a network sniffer (tcpdump or wireshark) and look at http traffic from your ObserverIP. You should then notice that once it connects to wunderground.com the reply, while having status 200, does not include the word "success" but will report "INVALIDPASSWORDID|Password or key and/or id are incorrect". If you don't see the attempt to upload at all, then the Internet connectivity for the ObserverIP is suspect.
-
Thanks Dolfs for you very prompt and detailed reply. It was greatly appreciated.
After I sent my message last night (my time) and having convinced myself that I had checked all the input data countless times I decided to delete the station from WU and create a new instance before retiring for the night. (Reading your message at work today confirmed my decision)
You will be happy to know that my PWS is up and reporting to WU, and has been since shortly before midnight here, but I did not discover this until only a short time ago this evening. The time on the Live Data tab is in sync, so I am quite exited, as you can imagine, and have emailed to my family and friends telling them of my new device. I know, I'm a PWS Newb.
Anyway thank you once again for your help. I wonder now if the IP Observer will be remain stable, as I have noted other posts indicating otherwise after varying periods of time.