January 3, 2019 at 5:35 am #53636
I’ve also been having this problem occasionally (maybe days or weeks apart?) where I discover the controller has dropped off the wifi network. I use OpenHab to drive the watering program, so it’s a big problem if it drops offline when I’m not around to reconnect it for more than a day or two. The display on the unit says it is reconnecting, but it does not do so until I reboot the unit (either by power cycling or holding the B2 button), at which point it reconnects immediately.
The get info page says “Firmware: 2.1.8(1), Hardware version: 3.0 – DC”
For now, I’ve set OpenHab up to warn me more actively if it drops the connection, but there’s something clearly not working in the firmware when it attempts to reconnect to wifi (its attempts – if indeed it is really attempting to reconnect – universally fail, whereas following a reboot it reconnects immediately… this leads me to believe it will not be solved by replacing the hardware).
Is there any way to access the unit at a lower level than the web gui and download a system log?January 10, 2019 at 1:15 pm #53717
Perhaps someone can name a specific router (Brand name and model number) that we can order and try? We have test OS 3 units connected to Netgear and Asus routers and have not have any disconnection issues, so it would be difficult to debug without having a router that it actually has issues with.
Something else that’s worth trying is to see if settings a static IP on OpenSprinkler would help. I suspect not, since I assume the issue is in establishing WiFi connection and not in DHCP. But nonetheless it’s worth a try.
January 11, 2019 at 1:34 am #53738
- This reply was modified 2 months, 1 week ago by Ray.
Mine is an Asus RT-AC88U.
I know it’s splitting hairs, but I don’t think it’s a disconnection issue: I believe it is a *reconnection* issue. That is, connection interruptions can happen for all sorts of reasons – for example, I’ve rebooted my router three times in the past week for other reasons – and in each case the OpenSprinkler has re-established the connection just fine as soon as the router comes back up. However, when the failure arises, the display on the OpenSprinkler shows that it is reconnecting, but it fails to do so until I intervene, no matter how long it is left to attempt reconnection. When the failure occurs, the issue is resolved immediately – and 100% reliably – by rebooting the OpenSprinkler unit. That appears to be the only way to resolve the issue. It would be good if detailed diagnostic logs were kept on the OpenSprinkler itself so that we can see what is going wrong in the OS’s system when it fails, but I am not aware of any logs except those associated with the timing of watering.January 14, 2019 at 12:40 pm #53763
I agree as the unit will not reconnect.
Maybe a auto reboot when the unit fails to connect after a number of tries or a certain amount of time on no WIFI connection.January 14, 2019 at 2:51 pm #53764
That seems like a really good idea, actually – it doesn’t depend on being able to trace why it is currently failing to connect (which sounds, from Ray’s post, like it could otherwise be a roadblock if they can’t reproduce it). I don’t think there’s any need for the time tolerance to be particularly short. For example, it could be a logic like this:
IF no functioning network connection (unable to sync NTP?) for at least 6 hours
AND currently configured for WiFi connection
AND unit uptime > 24 hours
THEN reboot system
That will mean it only tries the reboot as a last resort – not because the router it is connected to is disconnected from the internet for a while – and even then it would only reboot itself once every 24 hours.January 18, 2019 at 9:17 pm #53802
I was having the same issue. The WIFI connection drops from the OS and yet the display states it is connected and has an IP address. I am using a Technicolor MediaAccess TG789vac v2 Router. I am running on 2.1.8 (2) and only received the unit this month (Jan ’19). I may have just found a solution to this issue. I set a static IP address for OS on my router and it connected without a reboot of the OS. Hope this helps.January 19, 2019 at 12:56 am #53804
I think your case may have been a slightly different issue (or at least different to some of these cases, including mine – there could be multiple problems in this thread). In my case, the display on the OpenSprinkler indicates that it is trying to reconnect (as opposed to indicating that it’s connected and has an IP address), but it never successfully reconnects. So the OpenSprinkler unit is picking up that it has lost the connection… but the only way to do anything about it is to reboot the OpenSprinkler unit.
I have already set a fixed IP address for OS on the router, so that has not been a solution for the problem I’m encountering.January 23, 2019 at 6:57 pm #53836
I’m having the same issue as raaahbin. The unit will disconnect from wifi and then becomes stuck displaying a “reconnecting” message, but it never reconnects. After a restart it connects immediately. I have App: 1.8.2, Firmware: 2.1.8(2), Hardware version: 3.0 – AC, connecting to Apple Airport express router. I’m also using a fixed IP address for the unit.
Timing is random, sometimes within 24 hours sometimes 2 weeks apart.
Let me know if there is anything I can test/troubleshoot/log.January 26, 2019 at 9:16 pm #53864
It is probably a problem with renewing the dhcp lease, probably try static IP address. I set my dhcp lease as static on my dhcp server (router).
If I reset my access point I find I have to power cycle usually. My OpenSprinkler is plugged into a smart outlet so I can do it remote.
edit: i’m running on raspberry piJanuary 28, 2019 at 6:28 pm #53881
I already have a static IP address, assigned by my router based on the OpenSprinkler’s MAC address.January 30, 2019 at 7:02 am #53903
I think I have the same issue (I created a new thread then found this one). Sprinkler falls off the network and does not reconnect. I don’t know if it says ‘reconnecting’, next time I will check. The time I did check I was able to see the IP address on the Sprinkler. Where do you see it say reconnecting?
To fix the issue, I don’t reboot the Sprinkler, I disable the re-enable the WIFI on my router (I don’t reboot the router, just turn of the WIFI then back on). It then reliably reconnects .
App: 1.8.2, Firmware: 2.1.8(2), Hardware version: 3.0 DC
I have a second router I will try soon.January 31, 2019 at 10:45 am #53915
i have a windows 10 computer on wifi and it has a problem getting back a network connection after the dhcp lease has expired… this started about about 6-9 months ago. i’m on a r8000 router running as access point and clearOS as my firewall/router. for some reason i think this is something netgear changed in their firmware… are u guys with problems on netgear hardware???January 31, 2019 at 8:03 pm #53917
Asus router here. And in almost every case that sounds genuinely identical to mine (there have been a few others in the thread that sound different – the ones which have the IP address displayed, rather than the “reconnecting” message), it seems we have set it up with fixed IP addresses on the router. The consistent behaviour seems to be that only rebooting the OpenSprinkler unit – not anything else – will resolve the problem in these cases.
It does seem that there are other potential problems with wifi connections to the OpenSprinkler – some of which appear to have been resolved by setting a fixed IP address on the router – but the one a number of us are facing with the unit being stuck on “reconnecting” until rebooted, is a distinct one, and does not appear resolved by the suggestions that have appeared here so far.
On the bright side, my unit seems to have been up for a couple of weeks without the problem occurring… but that’s also the trouble with intermittent faults.February 1, 2019 at 12:02 am #53919
I am using TP-Link newtork hardware. My router sets an IP for my unit with mac address.February 4, 2019 at 9:30 pm #53946
Yes, I may have spoken to soon. Fixing an IP address resolved my connection issue for a few days, now the router looses connection to the OS every couple of days. Rebooting the router or WIFI made no difference, can only reboot the OS to regain connection. As suggested previously by others it would be good if the OS rebooted when signal lost, or alternatively a fix for those of us that are having problems, to have the option in the main system menu to reset the OS on a particular schedule (eg 24, 48, 72 hrs etc) and at a chosen time (say 2am when my system is idle). This should go a long way to working around the connection issue.
You must be logged in to reply to this topic.