The Ambient Weather software team has had numerous problems with the ObserverIP. I've been writing software since 1971 and got tired of the ObserverIP locking up and playing dead. I put bridged NICs in my bench Linux box and monitored the IP traffic with Wireshark. Although, the connection to ambientweather.net runs continuously, interactions with wunderground.net are problematic. I sent the Wireshark logs to the Ambient Weather development team and interacted with them trying to fix the issue. There are several sides to this problem. First, the development process doesn't do regression testing on software releases. You can see this because a new release will fix a bug introduced in the previous release which will then make yet another bug for another release. There are way too many releases as they struggle to stabilize the system. Second, the ObserverIP CPU doesn't have the resources to implement a proper TCP/IP stack. This is why simultaneous accesses crash the system. So instead of a proper stack they have a kludged approximation. My ObserverIP is single access only and it is still unstable while the Wireshark logs highlight handshaking failures in the stack. Conceptually, the ObserverIP is a great idea. Functionally, it doesn't work. What is needed is a better CPU running a minimalist Linux. Then it would be open source and creative weather junkies could hack new ideas. The additional cost of a more capable CPU would be trivial.