- This topic has 41 replies, 22 voices, and was last updated 3 years ago by Anonymous.
November 7, 2016 at 10:11 am #44492
We’ve released OpenSprinkler Unified Firmware 2.1.7. Among the main changes, we’ve added support for push notifications using IFTTT, and the programmed water times now support full precision down to seconds. See the list below for details. Thanks!
- Program water times now support full precision down to seconds, from 0 to 64800 (18 hours). Previous firmware uses a compression method to nonlinearly scale the water time (such that beyond 59 seconds, the water times must be in steps of minutes) — this restriction has now been removed.
- To make space for the increased program data, the maximum number of programs has reduced to 17 for OS 2.3 and all Linux-based OpenSprinkler (e.g. OSPi), and to 8 for OS 2.0, 2.1 and 2.2. If you have a large number of programs, you should take this into consideration when deciding to upgrade the firmware.
- Added push notification support using IFTTT. This allows the controller to send notifications to you through email, text message, or phone app. You can select the set of events to get notified for. At the moment, supported events include: Program Scheduled, Rain Sensor, Flow Sensor Update, Weather Update, Controller Reboot, and Station Run. Please check Firmware 2.1.7 User Manual and our Support Articles for details, particularly how to obtain an IFTTT key and how to create an applet (previously called IFTTT recipe). Thanks to Mike Szelong for proposing this feature.
NOTE: IFTTT support is only available for OS 2.3 and all Linux-based systems. It is NOT available for OS 2.0, 2.1, and 2.2.
- Added an additional type of sensor: Program Switch. This allows the user to connect a switch / button to the sensor port and use it to trigger the first program (Program 1). An LCD icon (P1) will be displayed when this sensor is enabled.
- Added HTTP GET API to start a specific program (see 2.1.7 API document) for details). Previously to use the API to start a program, you would need to call /jp to get the program water times first, then send a run-once program to the controller. Now you can directly use the /mp command to start a program given its index.
- Added support for GPIO station and HTTP station for OS 2.3. Previously this feature has been made available for Linux-based systems (e.g. OSPi). It’s now also supported on OS 2.3. Thanks to Peter Basham for contributing this feature.
A GPIO station can directly toggle a spare GPIO pin. An HTTP station can send a generic HTTP GET request upon opening / closing a station. These are two types of special / virtual stations. The other supported types include RF (radio frequency) station and Remote station. The HTTP station is more general / flexible than a Remote station.
Minor Changes / Bug Fixes:
- Integrated Robert Hillman’s implementation of flow sensor to log flow rate after each station run.
- Added support to use custom DNS IP (available when DHCP is turned off).
- Added new option to enable/disable special station auto-refresh. For example, if you use RF station and do not want the controller to periodically send refresh signals to keep the RF station in sync, you can leave this option disabled.
- The range of station delay time is now -600 to 600 seconds. The range of master-on adjusted time is now 0 to 600 seconds. The range of master-off adjusted time is now -600 to 0 seconds. All of them are in steps of 5 seconds. Previously the master-off adjustment is also allowed to be positive, but because the scheduler currently cannot handle a positive master-off adjustment, we’ve now limited this adjustment to negative (or 0) only.
- Enables LCD backlight to stay on (by setting a non-zero idle brightness).
- Allows weather checking when program is running.
- Made the firmware code compilable with Arduino 1.6.9.
User Manual, and API document for Firmware 2.1.7 are also released and can be found in our Support Articles.
Because firmware update will automatically trigger a factory reset, before updating firmware, please use the app / web UI to export your configurations to a file, so that you can import it after the update.
Upgrade OS 2.0/2.2/2.3 to Firmware 2.1.7:
Please follow the OS Firmware Upgrade Instructions.
Upgrade Linux-based OS to Firmware 2.1.7:
Please follow the OSPi/OSBo Firmware Upgrade Instructions.
Special Notes for OpenSprinkler 2.1
As in the previous firmware, if you own OpenSprinkler 2.1, this firmware can no longer be uploaded through the USB port. Instead, you will need an external programmer (such as USBasp or USBtiny) to directly flash it to the microcontroller. If you are interested in upgrading to the latest hardware version 2.3, we provide discounted price for upgrading. Feel free to contact us about it.
Instructions to upgrade OS 2.1 using an external programmer can be found Upgrading OS 2.1 to Firmware 2.1.6 and Beyond.
November 7, 2016 at 5:01 pm #44505
There seems to be a 1.6.0 Windows 10 phone app update. After the update, the app won’t start. even after a reïnstall.
The app on my Windows 10 computer is working correct.
Update 2.1.7 on RPi installed perfectly. thxNovember 7, 2016 at 5:12 pm #44506
Does the app just quit back to the program menu after selecting it? This issue should be resolved now in my testing. The previous build (1.5.0) first introduced this issue and it appeared to be due to a deprecated MS method.
I will do some testing and see what I can find.
Thank you for the report.November 7, 2016 at 11:52 pm #44512
I updated my system (running on a Pi2B+) and I got no errors during the upgrade.
However now, the web app nor the android app can connect to opensprinkler. When i check the status of the opensprinker service on the pi, it shows all green, no errors.
Any idea’s?November 8, 2016 at 2:11 am #44515
I just created a new topic on the issue with the WindowsPhone App. It still doesn’t seem to work on my side either.
ThanksNovember 9, 2016 at 8:16 am #44553
Just updated my OpenSprinkler DC v2.3 to 2.1.7 without any problem. I still wonder why updating requires usb connection and hope for future update via network. The language strings now look a lot better in German.November 10, 2016 at 4:09 pm #44560
Attempting to update 2.1.6(1) on hardware 2.2
V1.04 installed on windows laptop running Windows 7, and run in administrator, finds device after “Check for new devices”
Pressing Update Firmware greys out that selection but then no place to click “OK” (same results twice)
Thanks for any help
PeteNovember 10, 2016 at 11:45 pm #44563
Excited about the firmware updates. I am hopeful that the shorter flow times will allow Open
Sprinkler to be a part of my Aeroponics project. 5 second flow is typical.
Does anyone know what sensors we can monitor and hopefully log?
I need pH, TDS, Water Temperature and flow. Possibly pressure as well.
I also need to develop code to make changes/adjustments such as open valves, turn on pumps based on readings.November 17, 2016 at 1:06 pm #44616
Since I upgraded to the latest firmware my DC 2.3 model seems to crash once every day or two. I have never had an issue before and now I have to manually turn the unit off and then back on to fix the problem.
Has anyone else experienced this since upgrading?
-nate-November 20, 2016 at 11:20 am #44665
@Peter, we’ve seen a few issues with the updater getting stuck on ‘Checking Connections’ on Windows. Not sure what caused the issue as neither Samer nor I can reproduce the problem. But there is an alternative version of the firmware updater that you can try. First, download the following
1) Unzip the file to a folder, then go to the Windows subfolder, and find the executable.
2) Do NOT click on ‘Download Firmware’ button — because this is an older version, the download link is no longer available. But the firmware files are already embedded the local folders, so there is no need to download. If you accidentally clicked on it, just delete the folder and start over from step 1) again.
3) Click on ‘Detect Hardware’ button. Assuming the driver is installed correctly, it should detect that your OS.
4) Click ‘Upload Selected Firmware’ and wait for it to finish.November 20, 2016 at 11:22 am #44666
@natebarnz: when you say ‘crash’ do you mean the controller becomes unresponsive, or reboots, or something else? If would help if you can export configurations as a file, and submit a support ticket by attaching the configuration file. That way we can import it and see if we can reproduce the issue.November 20, 2016 at 5:51 pm #44690
Ray, Thank you, thank you,
Worked first time with your excellent instructions.
Your level of support is always great.
PeteNovember 21, 2016 at 10:12 am #44704
The system appears to crash. I cannot connect to it with the iphone app, chrome app, or direct ip address. The direct ip address connections loads the black screen and even says loading for a second before going totally black. The API does not respond either. So far the only solution has been to power cycle the unit.
I will submit the support ticket as you said.
-nate-November 24, 2016 at 4:29 am #44733
Hi, Ray, thanks for the update!
Just a reminder to everyone who is updating, the new 2.1.7 firmware requires a SD card in the slot, if not, you will see ERROR CODE 0x2D.
November 27, 2016 at 6:05 am #44759
- This reply was modified 3 years, 8 months ago by thisisit.
just successfully updated my OpenSprinkler Pi to 2.1.7 I’m using a Pi3 and it worked flawless the whole season.
If you only want to update the instructions provided is incomplete:
First step you have to download the update by “git clone https://github.com/OpenSprinkler/OpenSprinklerGen2.git”
And for me the last step was power off then on again.
Now everything works perfect!
Hope this to be useful for others.
Greetings from Austria,
Juergen.December 2, 2016 at 3:20 am #44802
@skyynet, I understand it’s a pain that the OS update process still requires a USB cable. This is because the microcontroller uses a USB-serial bootloader that’s simple, open-source, and has been widely used elsewhere. The bootloader is a piece of code that allows the microcontroller to overwrite its flash memory content (hence update firmware). It sounds simple but it actually is non-trivial to write as it involves low-level assembly code. I’ve looked into Ethernet-based bootloader, which would allow updating through web connection directly without any USB connection, but none is reliable and has been tested over long time. So I do not want to take the risk of deploying it. Hope this makes sense.
One thing I should mention is that with the ESP8266 WiFi chip, a lot of these legacy limitations will be eliminated completely. For example, OpenGarage, which is built around ESP8266, allows over the air (OTA) update, because OTA update is a standard feature in the SDK.December 14, 2016 at 8:35 am #45004
Hi, I would like Upgrade Firmware to 2.1.7…but the page of Instructions for update it’s not reachable.
someone has the instructions for the upgrade?December 18, 2016 at 2:34 am #45022
Nope, the support page for firmware upgrade instructions isn’t working for me either. 🙁December 18, 2016 at 3:52 pm #45026
DittoDecember 19, 2016 at 11:21 am #45034
Apparently they changed the subdomain on freshdesk to openthings. https://openthings.freshdesk.com/support/home
I took me quite a while to somehow come across this. Would be nice if they updated their docs.December 20, 2016 at 1:48 am #45037
Sorry for the confusion the way the name change is handled by Freshdesk is not what we expected.
Sent from my iPhone using TapatalkDecember 20, 2016 at 1:48 am #45038
Sorry for the confusion the way the name change is handled by Freshdesk is not what we expected.
Sent from my iPhone using TapatalkJanuary 26, 2017 at 12:37 pm #45303
Excellent update! The full precision down to seconds is my main reason for upgrading.February 4, 2017 at 12:06 am #45352
I can’t seem to get IFTTT Integrations to send ‘sprinkler’ notifications through IFTTT Maker channel. I’ve tried making this work a couple times since November and it’s just not sending any events to my IFTTT applet. I’ve followed the simple instructions to the T and still nothing. Has anyone else had trouble making this work; it seems that many have gotten it to work. Is there some other parameter that is missing from the firmware instructions?
Please help.February 4, 2017 at 12:27 am #45353
I apologize; seems like I just had to generate a new Maker key. I’m not sure why but the new key is working.
- You must be logged in to reply to this topic.