OpenSprinkler Forums OpenSprinkler Unified Firmware My Open Sprinkler has been having trouble connecting lately

This topic contains 40 replies, has 19 voices, and was last updated by  robi 3 months, 1 week ago.

Viewing 16 posts - 26 through 41 (of 41 total)
  • Author
    Posts
  • #53903

    trillian
    Participant

    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.

    #53915

    RottenMutt
    Participant

    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???

    #53917

    raaahbin
    Participant

    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.

    #53919

    jmillerah
    Blocked

    I am using TP-Link newtork hardware. My router sets an IP for my unit with mac address.

    #53946

    Willow
    Participant

    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.
    Thoughts?

    #54085

    mattat01
    Participant

    Hi,

    Has there been any progress on this issue recently? Since upgrading to 2.1.8 I’ve been having these drop-outs too. I’m on 2.1.8(2) OSPi with a static IP set up on my TP Link AC1900 router. When my OS drops out the programs stop running too (I’d hoped that it would just continue irrigating in isolation, but my plants started dying). I have it linked to my Home Assistant but it is just reading information over the API, but I’ve set up an alert to tell me it if drops off the internet (nmap can no longer detect the static IP).

    Interestingly, usually it drops off and does not reconnect. Today it did eventually reconnect after a few hours, but I could only access it via my browser (the app still couldn’t find it), although the router claimed that it is a connected device. After another few hours the app managed to connect too. Maybe this app thing is a red herring, but the dropping off the network is real, and really frustrating when my garden dies as a result. Can’t OSPi continue operating without the network connection, whilst it tries to reconnect?

    Cheers,
    Matthew

    #54143

    Ray
    Keymaster

    @mattat01: you are talking about OSPi, which is different from what other users are talking about (OS 3.0). For OSPi, the issue is not related to our hardware, it would be your RPi, or in case you use a WiFi dongle, the issue with the WiFi dongle. Only OS 3.0 has built-in WiFi.

    #54268

    mattat01
    Participant

    Ok, thanks. I’ll look into that, it is just that I never noticed it dropping out before I upgraded to 2.1.8. Still, you may be right so I’ll look into the hardware connection.

    Thanks,
    Matthew

    #59783

    Mikepuglisi
    Participant

    My opensprinkler also disconnects and fails to reconnect. It only occurred when connecting to a wifi extender (NETGEAR WiFi Range Extender AC750). When I reconfigured the opensprinkler to connect to my main wifi, I haven’t had a problem. Worth noting that my main wifi is actually a weaker signal to the shed, but open sprinkler seems to be more stable with it.

    #60375

    jmillerah
    Blocked

    This just happened again to me. Usually stable OS will disconnect from WIFI and stop doing everything! Including watering my lawn! I have to go under the house and do a power cycle to get it to connect again. This has to be fixed or I will ask for a refund on my OS unit as it is useless as it does not do what it says it will do.
    Running hardware 3, 2.17 firmware with a TP-Link WAP.

    #60395

    protofALk
    Participant

    I am seeing this issue now too – was working fine for a year or so. Didn´t change the setup. I am on a Vodaphone EasyBox 804 and opensprinkler 3.0 DC with Firmware 2.1.8 (1)

    #60454

    Hamboo
    Participant

    Same issue here on 2.1.8, is this being addressed by some oneone?

    #60455

    Hamboo
    Participant

    I opened a ticket on github… hopefully someone is picking this up
    GITHUB

    #61072

    mars
    Participant

    Same issue here on FW2.1.8, HW 3.0 – sporadic reconnect failure each couple of days.
    Connected to AVM Fritz!Box 7590 via FRITZ!Repeater 1750E.
    DHCP enabled (Although Router configured to always assign same address)

    Tried FW upgrade to 2.1.8(4) today, after reading this thread I will also try static address setting.
    Last resort would be daily powercycle via manual timer on wall outlet, which I want to avoid, because it would need to withstand the current draw of my pump and switches.

    • This reply was modified 3 months, 1 week ago by  mars.
    • This reply was modified 3 months, 1 week ago by  mars.
    #61076

    franzstein
    Participant

    I have an OpenSprinkler DC 3.0, Firmware 2.1.8 in an AVM Fritz!Box 3590 Mesh configuration running. The OpenSprinkler is installed in the Garage and most of the time connected to the WiFI AP FRITZ!Powerline 1240E installed nearby. It is running for months now without any issues. Please be aware that older Fritz!Repeater, like the FRITZ!WLAN Repeater 300 may be part of your problem.

    #61093

    robi
    Participant

    These “repeaters” and “range extenders” are very often real truble causers.

    Avoid using them.

    If you have to, don’t mix manufacturer brands. Also don’t mix new and old WiFi devices (like using an older wifi router and a newer repeater or viceversa) as they may implement standards differently, causing malfunctions.

    If there’s no other way to avoid this, use different SSIDs for the main and for the “repeated” signal, so that clients like OS don’t get confused.

    But better, try using quality AccessPoints, like Ubiquiti UniFi.

    • This reply was modified 3 months, 1 week ago by  robi.
Viewing 16 posts - 26 through 41 (of 41 total)

You must be logged in to reply to this topic.

OpenSprinkler Forums OpenSprinkler Unified Firmware My Open Sprinkler has been having trouble connecting lately