[Ray]

Are you talking about to individual zones or two sets of zones? If it’s two individual zones, then I think swapping wires would be the easiest. If this is referring to two sets of zones, could you provide more specifics, like how many zones are there in each set? It’s possible to edit the configuration file and re-import that to the controller.

[Ray]

I see, I agree that being able to change the program from N-day to 1-day when editing is indeed a convenience needed in your case. I will update the firmware to accept 1 day interval. Yes, this is just one line of change in the firmware and in the UI.

[Ray]

OpenSprinkler 3.0 has current sensing; OpenSprinkler Pi does not. The current sensing circuit itself does not prevent damage due to shorting because the sensing resistor can be burned if there is a solenoid shorting. So having a fuse on board (which OSPi has) is a better option for short protection.

[Ray]

I would not recommend this, because a sensor with 7V operating voltage means its output is also usually at that voltage level, which is above the controller’s operating voltage. If you have to use this sensor, I suggest that you either use a resistor voltage divider, or a resistor plus a zener diode to reduce the output voltage down to 5V, which is safe for the controller’s sensor pin.

[Ray]

I have a pixel 3a with Android 11 and the app works just fine. We unfortunately don’t have an Android 10 device to test with. Is it possible for you to update to Android 11? If not, you can for now use the mobile web browser instead of the app.

[Ray]

The original fuse is rated 2A. Pretty much any fuse you can find that can fit there is ok, doesn’t have to be the same size. If you can’t find a fuse, you can temporarily use a wire to short it across the fuse to get the controller to power up again.

[Ray]

There is an implementation of this feature in a development branch of the firmware currently:
https://github.com/OpenSprinkler/OpenSprinkler-Firmware/tree/scheduler-feature
it hasn’t been merged into the master branch yet but we are working on it.

[Ray]

Can you post a picture of the fuse? These parts are generally available on Amazon or eBay.

[Ray]

@SpikeyGG: I am actually considering adding a feature to the firmware, that makes use of a program, to reboot the controller at some designate times. Basically the idea is that if the program name starts with :> then what follows it is expected to be a command (e.g. reboot etc.). This way it can make use of the existing program scheduling structure to execute, say, a reboot command. The advantage is that this requires no UI changes (thus avoiding the annoying iOS app store approval process); the downside is that it does waste one program.

[Ray]

There is an implementation of this feature in a development branch of the firmware currently:
https://github.com/OpenSprinkler/OpenSprinkler-Firmware/tree/scheduler-feature
it hasn’t been merged into the master branch yet but we are working on it.

[Ray]

Please either update your firmware to the latest 2.1.9(7), or change NTP to a valid NTP server. Only firmware 2.1.9(7) supports default NTP server when NTP IP is set to 0.0.0.0 — earlier firmwares do NOT support the default NTP server.

[Ray]

One thing to keep in mind: the switch, as in a sensor, should be connected between SN1 (or SN2) and GND, not VIN, or COM. This is explained in the OSPi user manual.
https://openthings.freshdesk.com/support/solutions/articles/5000631606-user-manual-opensprinkler-pi-ospi-
If the switch is connected incorrectly, it could be triggering the program to run unexpected.

[Ray]

Please submit a support ticket at:
support.opensprinkler.com
we will need to know basic information such as the order number and may possibly ask you to attach a copy of your configurations to help diagnose the issue.

[Ray]

Soil sensors that output digital signals are already supported and the statuses are pushed to MQTT in firmware 2.1.9(7). If you are referring to analog soil sensor — the firmware does NOT support analog sensor because the GPIO pins used to read sensor status is not an analog pin. You would need to use either an i2c type of soil sensor, or have an i2c type of analog to digital converter in order to interface it with opensprinkler.

[Ray]

We are aware of the discontinuation of darksky at the end of this year and are looking at alternative weather data sources. OpenWeatherMap, which we had used before switching to darksky is still available and we can easily switch to it by changing a configuration flag. The weather code is written in a very modular way so it’s fairly easy to integrate a new weather data source.

[Ray]

Is it possible that the zone you are testing is not associated to activate the master zone you are testing? I just checked
demo.opensprinkler.com
I turned on a zone that’s associated with master 1, and both zones are instantly green. So I am not sure if I can reproduce what you reported.

[Ray]

While this can be done, it requires you to modify the firmware — reading temperature + humidity sensor needs to be implemented; and how exactly that affects the water adjustment also needs to be implemented.

[Ray]

The activation of the master zone is implemented at a very low level which is below the MQTT notification, that’s why it doesn’t send out a notification for the master zone. On the main screen, though, it should show as green because the status of the master zone does change correctly according to its status. Did you set a master on or off delay? The on/off delay will modify the exact moment the master zone fires.

[Ray]

Yes the cable can be reversed. Either way, just make sure the bump on the connector matches the opening on the receptacle at both ends — on the main controller this should be obvious; on the Ethernet module, the printed enclosure has an opening that matches the bump on the connector.

[Ray]

Please refer to this thread of posts:
https://opensprinkler.com/forums/topic/feature-request-prevent-oled-burn-in/

[Ray]

No, you do not need expander unless if you need those zones physically. OpenSprinkler allows you to set more zones than there are physically, because a zone can be a ‘virtual zone’, such as you can set it up as HTTP zone, remote zone, RF zone etc. In your case, the dummy zone is just used to activate the master zone. If you do not want to see those unused zones on the screen, you can disable them — click the ‘gears’ icon next to a zone name, and click ‘disabled’, that way it will be hidden from the UI.

[Ray]

You can do so by using a spare zone (you don’t need zone expander, you can simply enable more zones in Edit Options -> Station Handling, OpenSprinkler allows you to set more logical zones than the number of physical zones you may have). The spare zone can serve as a ‘dummy’ zone to activate master.

[Ray]

All versions of OSPi can use the current firmware, there is no separate firmware for earlier versions vs. later versions. Perhaps you can try to upgrade your Raspbian to the current version and also your firmware to the current version too (2.1.9(7) whereas you reported 2.1.9(4) is what you have).

[Ray]

The log event is only written to flash when the rain sensor is deactivated. This is because it needs to record the duration of this event and it only knows the duration when the event is over.

[Ray]

The call only incurs cost if you have selected an adjustment method that is not Manual. If you chose ‘manual’ then the weather script only returns things like time zone, sunset/sunrise time, and does not trigger a weather query. So no worries.

[Author]

Posts