- This topic is empty.
May 4, 2014 at 12:49 pm #22873
I have a pre-release version 2.0 (came in the clear box) and it had worked flawlessly for months. After updating to firmware 2.0.4 it now randomly locks up and remains that way until it is power cycled. When it “freezes” none of the buttons work, it is unreachable via network, and the LCD screen is frozen on (presumably) the time it all went bad (most recently last night at 2:30am). Worst of all, nothing gets watered! Wondering if i should just downgrade back to the older firmware that worked… Also, possibly unrelated, the clock seems to be running fast and I’m pretty sure it is NOT able to sync via NTP. (It has frozen with NTP on and off so I don’t think that is causing my problems). Not sure if it matters but it is connected via ethernet to an apple airport extreme…
EricMay 4, 2014 at 10:38 pm #26705
I am really sorry to hear that. Right now I can’t think of any obvious reason why the firmware upgrade would cause it to freeze. The fact that it freezes probably indicates that it’s having trouble connecting to the network (and thus spending most of the time establishing connections instead of responding). So my first question is: is it able to get a valid IP address? and can you see from the LCD screen (the little WiFI-style icon) whether it’s connected or disconnected? One difference in firmware 2.0.4 is that the software-defined Mac address has changed. I am wondering if this may have caused some trouble.
I also suggest trying to turn the ‘Auto Reconnect’ option to No — if the controller doesn’t freeze any more, then the problem is due to issues connecting to the router; if the controller still freezes, the the problem is somewhere else.
A support email has been sent to you. Please see the instructions therein. Thanks.May 5, 2014 at 4:46 am #26706
This part got me thinking:
One difference in firmware 2.0.4 is that the software-defined Mac address has changed. I am wondering if this may have caused some trouble.
I have given it a static IP which was reserved in my router via the OLD mac address. I have a feeling that might be what caused it to get stuck trying to reconnect… I updated my airport to the NEW mac address; hopefully that fixes things…June 3, 2014 at 5:43 am #26707
I seem to be experiencing a similar problem:
mine hung a couple of times with the same symptoms: no network, unresponsive to button press, display on.
The second time it could have coincided with my ethernet switch loosing power for an hour or so.
I also have “auto reconnect” enabled.
If the problem is some kind of tight loop, is it possible to workaround it with a watchdog?
– OpenSprinkler v2.1u
– firmware 2.0.4June 4, 2014 at 3:43 pm #26708
One more data point to add to my case: I tried with the “reconnect” option off and it still freezes.
It seems to hang after a few hours it restart it.June 5, 2014 at 4:37 am #26709
The freezing problem is usually because the controller cannot ping the server or is having trouble performing NTP sync. So here are my suggestions:
go to options, and turn NTP sync off, Auto reconnect off, also set DHCP off, instead, use a static ip (make sure the ip is compatible with your network, and make sure you set the correct gateway ip as well, i.e. your router’s ip).
See if these help eliminate the freezing problem.June 9, 2014 at 2:26 pm #26710
I am also experiencing this issue. Brand new hardware (assembled), firmware 2.0.4. The unit will, at apparently random intervals – usually less than 12 hours, sometimes less than an hour – freeze. The only sign of life is the orange LED on the ethernet port, which is flickering. The green LED on the ethernet port is on solidly. The display is frozen at the last time prior to the freeze. The unit is utterly unresponsive otherwise. I will try the suggestions above and report.
[EDIT] DHCP has always been static, but NTP has been on, and Auto Reconnect has been on. Also – the unit is connected via ethernet to a DSL router/modem. The internet connection is dodgy at best – and slow.June 10, 2014 at 4:43 am #26711
@HFTobeason : can you turn off NTP sync and Auto Reconnect and try again?
For users who encountered freezing issues: try to turn NTP sync off and Auto Reconnect off as suggested above, and see if this solves the problem. It’s important to find out what’s causing the freezing, as this is not something we have been able to reproduce on our side. Being a small, open-source team, we don’t have the resources to do comprehensive testing, so we have to rely on users to do various experiments to find out the cause of the issue. If the NTP sync or Auto Reconnect turns out to be the culprit, the implementation can definitely be improved. Thanks!June 10, 2014 at 12:57 pm #26712
I turned off NTP and Auto Reconnect yesterday afternoon, and have NOT had a freeze since then. However, at the same time, I also deleted ALL schedules. I am adding schedules back now.June 13, 2014 at 12:05 am #26713
OK, that’s for the update. Good to know that turning off NTP and auto connect helped.June 13, 2014 at 1:06 pm #26715
As of this morning, the unit has been running schedules without a hiccup ever since I disabled NTP and Auto Reconnect. When I get back to the house, I will try re-enabling one option at a time to see which is causing the problem.June 16, 2014 at 1:27 pm #26716
I have this same problem. I’m using the latest firmware 2.06 in hopes that it would help. It did not, system freezes solid. This all seems to have happened after I went from 2.0 to 2.01. 2.0 was rock solid and never had issues. Although could be coincidence. Perhaps the hardware is failing for me?
I did notice in the new 2.06 that when its frozen a new little arrow shows on the screen in place of the network bars. Buttons are non-responsive. All I can do is reboot.
I have the newer Gen 1, 2.0 unit with the clear cover. Just before the white one.June 17, 2014 at 1:02 pm #26717
Woke up this morning to the device frozen solid and my sprinklers stuck on this time. That was with NTP shut off so that wasnt it. You guys here still experiencing problems?June 17, 2014 at 2:32 pm #26718
I turned NTP on this morning at 8:30AM. It is now 10:30AM, and the unit is still okay. Note that I have Auto Reconnect OFF.June 17, 2014 at 2:44 pm #26719
Auto Connect Off, roger that. I will test that next. Thank you for the reply.June 17, 2014 at 3:15 pm #26720
Most likely it’s the Auto Connect that’s causing the trouble. It basically tries to ping the router and see if it’s still connected. This feature is implemented in the first place because in case there is a power break, and the controller is powered on before the router is, it should be able to re-establish IP from the router.
A quick work-around is to set a static ip on the controller (note, this only works if you set a static ip on the controller, not by using IP reservation on the router), you can turn off auto-connect, and since the ip is fixed, it doesn’t need to be re-established. This is probably the best option if you are still seeing freezing problem.June 17, 2014 at 3:50 pm #26721
Thank you for the reply. The unit has been on Static IP since I took it out of the box and set it up last year. So no DHCP here.
Things were awesome until I went from 2.0 to 2.1 (over the Winter) and 2.6 (recently). I did not notice anything until I actually started the system back up in Spring.
Ray, I worry about the auto connect feature. I disabled that last weekend and the device actually came back several hours later with a new address in the 192.168.1.X range. Almost like it reset itself or like reconnect “off” means give up and reset the IP stack. Mind you, the device is configured for static IP and my network is not even on that subnet. It’s on 192.168.5.X.
Food for thought. Not sure if it’s relevant or not but I figured it may help us all troubleshoot the issue.
EricJune 17, 2014 at 3:54 pm #26722
If you’ve recently upgraded the firmware, keep in mind that each firmware upgrade will trigger a system reset and all settings are reversed to factory default. So if you’ve set static IP before, make sure you set it again after firmware upgrade.June 22, 2014 at 3:32 pm #26723
I have confirmed that with a Static IP address assigned and Auto Reconnect turned OFF, the device appears to be more stable. NTP sync does not appear to be part of the issue.June 25, 2014 at 8:08 am #26724
I too have not had a lockup since turning Auto Re-connect off (I was already using a Static IP) I continue to use NTP sync.
I spoke too soon, it just locked up.June 25, 2014 at 11:38 am #26725
Auto Reconnect OFF, NTP sync ON, using static IP, 4 programs in use, firmware 2.0.4 — running without problems for 8 days now.June 25, 2014 at 9:23 pm #26726
@jgrylls: which firmware version are you using? I am curious if anyone is using firmware 2.0.6 and still seeing the lockup issue? If so, my assumption about the lockup may be wrong and I have to think about other causes.June 25, 2014 at 9:35 pm #26727
Ray – I’d be happy to load up 2.0.6 and test it, but I couldn’t figure out how…June 25, 2014 at 9:37 pm #26728June 25, 2014 at 9:49 pm #26729
I looked at that post when you issued 2.0.6, but this line stumped me: “Instead, use the firmware updater program from the Github repository (https://github.com/rayshobby/opensprinkler).” When I clicked that link to get to Github, I assume I then need to drill down through OpenSprinkler Controller -> software -> osFirmwareUpdater -> application.macosx -> osFirmwareUpdater.app… But now I’m lost. I must assume that, somewhere in that chain, I’m supposed to be able to download the updater program. I’m just too stupid to figure it out…
- You must be logged in to reply to this topic.