Topic: Intermittant pressure WS-1400-IP

[btw-nc]

What would cause this problem?  I have a solid blue "Indoor" light on the receiver, and the display on the pressure unit seems normal.

[zedrad1]

I am getting the  same thing. I was having trouble with the dew point being off and the humidity was going from 1% to 99%. I talked to ed at AW and they are sending me a sew sensor pack. Then this same thing started happening to the pressure. I am hoping it is just this sensor pack with a lose connection or WU dropping info.

[btw-nc]

Now my "Indoor" light is flashing, even though the units are only about 28 inches apart   

[zedrad1]

I believe flashing is "something happening" there is data exchange. I noticed when I was having connection issues with the sensor I didn't have a blue light for >20 min.

[Rychu]

What would cause this problem?  I have a solid blue "Indoor" light on the receiver, and the display on the pressure unit seems normal.

Check that the sensor lights up every 60 seconds icon antenna of reach - in the upper left corner.

[btw-nc]

I have reset the sensor unit by removing a battery. I've also reset the IP unit.  This was yesterday.  This morning, the "indoor" indicator was blinking at a slow steady rhythm.  Now, about 90 minutes later, it's lit solidly.  I still have a very broken pressure graph on WU.

[Rychu]

Status of the LED for the internal sensor:

Solid light: the device properly record the internal sensor
Off: the device incorrectly registers the internal sensor
Flashes: the device has not received the data from the sensor for 10 minutes - the search for new sensor will be started after 2 hours of not receiving data from the sensor

PS: I have the same problem - do not even want to read packets from other sensor WH25 - from the HP1001 - a previously read correctly.   

Regards from Poland
 

[zedrad1]

Thanks for that. I was getting ready to look it up but i had to go to work. I guess I need to restart the observer part. It has been working fine, I wonder why it is being stupid.
 

[btw-nc]

I've moved the sensor even closer to the IP unit to see if that makes a difference. It's now about 20 inches away.

[Rychu]

I've moved the sensor even closer to the IP unit to see if that makes a difference. It's now about 20 inches away.

The minimum distance from the sensor to the base station is 10 feet or 3m - according to the instructions.

Only above this distance should not be interference.

My sensor from the news function at a distance of 50m from the base station and there were no problems. Disturbances began to occur gradually until it stopped just reported to the base station.

===========

Forced to base station merged with another sensor WH25 - from another of my station HP1001. The sensor and the station joined up - but after an hour of actual work connection has been broken.

Conclusion: the sensor is good but the base station is running with errors

[btw-nc]

The sensor I'm having a problem with is the indoor sensor. The manual says to place it between 5 and 20 feet from the IP unit. So I have placed it about 8-10 feet away now.  Not hopeful though.

[sinan0310]

I have the same issue on my ws-1200, I plugged off but nothing else worked. It has started in the weekend.

[btw-nc]

I have just sent all the details to the support people at Ambient Weather, and will report back with their response.  My unit went in service on January 14th, 2017.

[btw-nc]

Well, that didn't take long:

-------------
On March 1, 2017, it appears that Amazon Web Services changed how the ObserverIP opens and closes ports on the server. This causes other tasks to slow down, and manifests itself in the indoor temperature-humidity-barometer to act sporadically. We are working on resolving the issue.

We will release a firmware update to fix it.

The update will be found here:

http://www.ambientweather.com/observerip.html


I realize many of you are very upset, but rest assured, we are working as hard as possible to fix the issue. Your patience is very much appreciated.

Regards,

Ed
----------------------

[btw-nc]

This is the note on the website, which specifically mentions the 1400-IP:

On March 1, 2017, it appears that Amazon Web Services changed how the ObserverIP opens and closes ports on the server. This only occurs on the WS-1400-IP system. This causes other tasks to slow down, and manifests itself in the indoor temperature-humidity-barometer to act sporadically. We are working on resolving the issue. Any updates will be posted on this page.

[greatg]

I have been dealing with this issue for 2 months. With multiple emails back and forth with Ambient Weather. Ed stated that this was a problem on WU side. Good to see they finally admitted that they have an issue!

[btw-nc]

I just updated firmware to 3.1.3   Getting ready to check it out now.

[btw-nc]

Up and running on firmware 3.1.3   Let's see if that's the trick. 

By the way, I had to connect my IP module directly to the router (same as the PC is connected to) and turn off Windows Firewall for the upgrade to complete.

[greatg]

I updated to this new release. But, doesn't appear to have resolved the issue. Pressure data is still sporadic or missing?

[BroPete]

Thank you very much! I've had the same problem for a week or two and noticed a station near mine was having the same trouble.

[btw-nc]

So far, so good with mine. The pressure graph on WU has been solid since I did the update.

[greatg]

Is yours connected directly to your router? I have mine going through a network switch?

[btw-nc]

Mine's plugged into a switch as well. Did you press the reset button after updating?

[greatg]

Yes, Rest button pressed. Several power downs.

[btw-nc]

What is the link to your station on WU?  I want to see if the graph resembled mine.