No Devices Found?
No Devices Detected?
These can be common errors that will let you know when your unit is not connected to the WiFi and/or Cloud.
This is most commonly caused by having a Low WiFi Signal
If signal is OK, please check your WIFI Router equipment and/or firewall devices that might block traffic.
The best way to check this is to navigate to WiFi on your device:
|Wrench > System > WiFi||
Here you can see the Signal Strength expressed in Decibel format. Its best to stay under -60, once you start getting into the -65 and -80's you will experience disconnects and loss of access remotely to your unit.
In the event you are still connected to WiFi but unable to access your unit remotely, you have have to re setup Cloud Access:
Wrench > System > Remote Access
Here you can edit your email and then re send the Confirmation Email.
Once confirmed you you be back in the cloud.
Using WiFi Extenders or Access Points?
Its possible that WiFi Extenders or Access Points are blocking local packets due to how WDS (Wireless Distribution System) works. In this case you would need to disable Local Discovery, and use Cloud Access.
|Device List > Menu
||> Network Settings > Local Discovery|
Still cannot connect?
Make sure to power down not only the RainMachine but your network devices as well such as Routers and Range Extenders and then power them back up and try again.
Its also possible that your router has Mac Filtering setup, preventing you from connecting. More info here.
If you still can't connect to help narrow down the issue, most phones have the ability to setup a hot spot. You can attempt to connect to this hot spot, to help narrow down the issue.
Trouble shooting with Network Tools
Wrench > System > Network Tools
This is a great utility that will help trouble shoot your internet connectivity or a Blinking Wrench.
Using this tool you can tell what level of connection you have.
This tool will query the following:
Gateway Reachable by Ping?
DNS 1 Reachable by Ping?
DNS 2 Reachable by Ping?
DNS Google Reachable by Ping?
DNS can resolve Google
HTTP Call to Google
DNS can resolve NOAA
HTTP Call to NOAA
Here is one common example where Network Tools can help:
Example 1: (Unit is connected to your router, but the router does not have internet access)
DNS/Gateway pings would work since the router still providing DNS resolution and a ping-able IP address. but would fail on HTTP call to Google and NOAA since the unit was not able to access the internet.
Example 2: (Unit is connected to a range extender that has become disconnected from primary network).
DNS resolution would work since the range extender still has routeing tables but ping DNS/Gateway would fail and HTTP call to Google and NOAA since the unit was not able to access the internet.
Getting Disconnect frequently?
Its possible your router is auto channeling and switching WiFi channel every time a channel gets to noisy. This would need to be disabled on your router if determined to be the issue.
DHCP / IP Address Problems
When running into duplicate IP's on your network, you have to be sure you have unique IP for every device.
This problem typically arises when your using static IP address on devices in the same range as DHCP pool.
In this situation you would want to be sure to switch both devices back to automatic DHCP or be sure the to change the IP address's so they are unique.
More info click here.
Not able to connect using Direct Access?
Make sure your ports are forwarded correctly in your router. (Need help Visit portforward.com)
1st Gen Models (HD-12 Sold before July 2015)
Port 443 or 18443
2nd Gen Models
Port 8080 or 18080
Firewall - Generally most firewalls don't block ports internally, but if you get caught in this situation here are some common ports we use internally.
8000 - Remote Access
8997 - Mobile App to send verification emails
9000 - Outbound to discover sprinklers remotly
Please sign in to leave a comment.