basicUsername: (optional) Only needed when the OpenSprinkler device is behind a basic auth enforcing reverse proxy.

refresh: Number of seconds in between refreshing the Thing state with the API.

port: Port the OpenSprinkler device is listening on.

hostname: Hostname or IP address of the OpenSprinkler HTTP API.

OpenSprinkler devices can be discovered by the binding sending requests to every IP on your network.ĭue to this method used, it is very slow at finding devices and can saturate network bandwidth. Recommend that you first add a single device thing and then if you need the extra controls, add as many of the station things as you wish. OpenSprinkler Device is for device-specific controls that usually apply to multiple stations or main unit sensors, e.g.to turn it on or off, or the time remaining. OpenSprinkler Station is for gaining advanced controls and status information over a single station (zone) of a device, e.g.

OpenSprinkler HTTP Bridge is required to communicate with an OpenSprinkler device through the network and should be added first.Mixing the two concepts can also be done, the choice is yours. You can choose to manually start, stop or delay the stand alone watering programs that are stored and run fully from the OpenSprinkler device.Īlternatively you can setup openHAB rules to control everything in more depth by setting up multiple station things for each watering zone to gain more in depth control.īy using the internal programs and sensors of the OpenSprinkler device, it can remove the complexity of what happens to the watering if openHAB crashes, is rebooted, or drops out of WiFi range in the middle of your watering rules. This binding allows good and flexible control over your OpenSprinkler devices.

Openhab opensprinkler