Network errors

[craigmw]

I have just switched over to the new firmware from Dan’s python program and am having some difficulties with network errors.  I have two OSPi’s, on for the front and one for the back yard. The back yard OSPi is running on port 8082 and the front on 8080. I use port forwarding and a dynamic DNS server to access the units from outside my LAN, but I get these errors even if I connect directly to the units on the LAN by typing in their local addresses and port numbers. Both units are accessed by WiFi USB dongles, so I first thought that these connections might be flaky. However, I can use Putty to SSH into both, and the putty connection via WiFi seems to be fine. I had this issue occur while running a “Run Once” program, and it left the valve open. This could be a disaster, so I want to be certain that such Network Errors are not going to lead to such problems.  Any thought about how to fix these issues.

One other thing that might be nice… in Samer’s Android App, I can select between these two OSPi units, but I don’t see a way to do this on the web app. Is this possible, or does this feature not exist for the web app.

 

Thanks…

[craigmw]

I have had to revert both OSPi units to Dan’s interval program because of this network error problem. I’d really like to get the new program working, but not at the expense of having non-functional sprinklers. Dan’s program seems to be working fine on both. Has anyone else run into this issue?

[craigmw]

Incidentally, the instructions given for setting up the new C++ based kernel have an issue. Obviously, it is necessary to inactivate the Dan’s Python kernel to prevent device contention and allow access to port 8080. However, the original instructions for installing the Python interval programming and making it start automatically (http://rayshobby.net/mediawiki/index.php?title=Python_Interval_Program_for_OSPi#Starting_the_program_automatically) use an entry in rc.local. However, the instructions for disabling the Python interval program indicate that the program is auto-started via init.d (using update-rc.d). Running sudo /etc/init.d/ospi stop will give an error (file not found) if one followed the link above for automatically starting the Python interval program (which I did). Instead, it is necessary to remove (or comment out) the lines in /etc/rc.local that start the Python interval program on reboot.

 

Note that even after doing so, I am still getting network errors reported in the web app. I will try with completely fresh installs of Raspbian to see if that might fix this issue, but for now, I’ll need to stick with Dan’s program.

[Author]

Posts