- This topic has 1 reply, 2 voices, and was last updated 6 years, 2 months ago by
.
-
Posts
-
When the OSPi and OpenSprinkler 3.0 say they have “built in Wifi” does that mean they simply can connect to a wifi network due to having a built in ESP chip or does it mean they can act as they own wifi hotspot for me to connect to with the mobile app/web interface and make settings changes. Can I do both? The reason I ask is that I need to deploy them to locations where there is no existing wifi router so if I have to rely on an existing ifrastructure, it won’t work for me.
I responded to this question in your support ticket. So I am copy pasting my response here:
You are correct that technically both of them can be set in AP mode, so that a phone or computer can connect to them without a router. For RPi, this depends on how you set up the RPi linux system — you can set it in AP mode, but since that’s irrelevant to the firmware it’s just a matter of figuring out the correct commands to set the system in AP mode.
For OpenSprinkler 3.0, currently it only allows accessing firmware features when it’s in Client mode. The AP mode is merely used to configure the WiFi settings so it can log on to your router. There is no technical barrier to make it work in AP mode as well — it’s just that some of the firmware features, like obtaining weather data, perform NTP time sync, will not be available in AP mode, for the obvious reason that in AP mode it doesn’t have Internet connection. Other than that, it can fully function in AP mode.
That said, a WiFi router these days is very cheap, you can get a WiFi router for something like 10 bucks, then you can have your OpenSprinkler 3.0 and phone/computer connect to the router and communicate through the router. The router is not a modem, so does not need Internet connection. I suspect this is also more efficient for ESP8266 because in Client mode it doesn’t have to manage DHCP and other AP-related tasks.
- You must be logged in to reply to this topic.