Forum Replies Created
-
Posts
-
bkastel, not sure if this helps you, but your problem description actually matches an issue I had when first installing my OSPi. I believe the symptoms would probably apply to a lot of internal vs. external network issues.
If I’m inside my WAN, I access my OSPi via the internal IP (192.168…) given by the router’s DHCP (static routes, BTW). Outside my WAN, say, on cellular or whatever else, I use the port forwarding IP. The port-forwarded IP does not work on my home WiFi, nor does the internal work from outside (duh). My solution so far has been to create two controller instances in the mobile app–one for @Home, and the other for remote, both using the respective IP addresses that work in each case.
Again, not sure if this helps, but I posted just in case it might.
+1. Ray, take my money, now! I just installed OSPi this past week–very easy install, no hitches–and was thinking about how thermostats use 24VAC for switching, just like a lot of sprinkler systems do (mine included). Of course, sprinklers use solenoids, and HVAC switching is for the control side of a relay, but both are just driving coils in the final analysis.
A system that didn’t need a Pi, like the ESP8266 you mentioned, would be even better cost-wise, as long as it could provide similar functionality. I know that the Pi is a bit of overkill for OpenSprinkler, but it’s at such a good price point that the overkill doesn’t mean overpriced.
Can’t wait to see this come to fruition!! Loving my OSPi so far!!
