June 30, 2019 at 9:14 pm #61456
Hi, I have a OS3.0 with the LAN adapter, but have found that on a reboot the OS will sometimes ignore the LAN adapter and wait for a WiFi Connection. If I power cycle the OS3.0 it will usually return back to using the LAN adapter, but sometimes I need to restart it multiple times.
Is there someway for to permanently disable the WiFi side? Or force the ethernet adapter to be the primary connection method? Also I’m running a static IP, and there doesn’t seem to be an option to enter in a Subnet Mask? am I’m missing something with the setup?
Thank you.July 8, 2019 at 7:24 pm #61548
Any chance this could be looked at? Its sort of a big problem for us. From my testing this only seems to be a problem when setting a static IP. If I change back to DHCP the ethernet adapter stays connected all the time. Switching to a static address and about 1 in 3 reboots the wifi will take precedent and I get no connectivity via the ethernet.
ThanksJuly 9, 2019 at 8:37 am #61556
I haven’t had this problem with the OS3.0 + LAN adapter, but I assign the OpenSprinler’s IP address within my router config based on the MAC address of the OpenSprinkler. The OpenSprinkler continues to use DHCP, but it will always be assigned the correct IP address even after a full factory reset of the OpenSprinkler.July 9, 2019 at 5:02 pm #61592
On OS 3.2, the Ethernet adapter works as follows: if it detects the adapter, and it can successfully obtain an IP address with the adapter, it starts in Ethernet mode; otherwise it boots into WiFi mode.
To find out why it doesn’t go into Ethernet mode, first check if (upon power on) does it show a ‘Start wired link’ message? If so, that means it has detected the Ethernet adapter, and if consequently it quits Ethernet and boots into WiFi, then it must be because it can’t obtain an IP address. I don’t know the specific reason, but it could be because there is something wrong with the static IP settings (for example, IP conflict, incorrect gateway IP setting etc). Generally I recommend users to stay away from setting static IP, and instead use their router’s DHCP reservation to reserve a fixed IP. This way, the controller still gets a fixed IP but everything is managed through DHCP.
Finally, if you purchased the controller from our German distributor, they had a first batch of OS 3.2 with a slightly outdated firmware, which may have affected static IP. The most recent firmware is 2.1.8(4) (i.e. minor revision 4), and is available here:
you can perform a OTA update (note that OTA update only works in WiFi mode, either AP or station mode is fine) to update your firmware to the latest. But I would say first try to set the controller back to DHCP, and use your router’s DHCP reservation to bind a fixed IP to the controller’s MAC address. If that resolves your issue, there is no need to update firmware.
You must be logged in to reply to this topic.