- This topic has 4 replies, 2 voices, and was last updated 9 months ago by
.
-
Posts
-
I have a 3.3 AC unit with wired ethernet. After several weeks of uptime, maybe longer, it “permanently” switches to a 169.254 link local IP address until I reboot it. Rebooting it through the buttons on front is sufficient; I do not need to power cycle the hardware.
Nothing else on my LAN falls off the network and there are no power/service interruptions coinciding with this failure.
FW: 2.2.1 (2)
Attachments:
The picture doesn’t show if a wired Ethernet cable is plugged into the module or not. The IP address 169.254.x.x can be due to a number of reasons: the DHCP server didn’t respond; the Ethernet cable isn’t plugged in; VLAN configuration issues if using VLAN.
The IP address 169.254.x.x can be due to a number of reasons: the DHCP server didn’t respond; the Ethernet cable isn’t plugged in; VLAN configuration issues if using VLAN.
None of these apply here. At the time of failure: the cable was plugged in for weeks and has not been touched, nothing on the LAN changed, no other clients were affected.
This isn’t reproducible on demand, but it does recur every few weeks.
And, without touching anything else (including the ethernet cable), resetting the OpenSprinkler unit through the buttons in front causes it to magically start working again.
If this doesn’t happen too often and if rebooting makes it connect again, you can use this work-around: set up a program to reboot the controller automatically every day, or at any interval of your choice. You can check the OpenSprinkler user manual, search ‘special program name’ to find out the instructions.
- You must be logged in to reply to this topic.