Expansion Board Not Adding

I installed OpenSprinkler + an expansion board today. The system is working except for the expansion board. I go to add it (click the bell with the message indicator where it says “Unused Expanders Detected”) and it takes me Station Handling. I add 16 stations (I have 14) and click submit and it seems to recognize that I have 16 stations. I went to test the sprinkler system and it only ran the 8 stations that are wired to the original OpenSprinkler controller. It did not run stations 9 to 14. The message indicator also keeps popping up with the ‘Unused Expanders Detected”. What do I need to do to add the expansion board? What am I missing?

OpenSprinkler 3.3 enclosure

Hi,

I started building the latest OS (3.3) from github (https://github.com/OpenSprinkler/OpenSprinkler-Hardware), but I couldn’t find any enclosure 3D models there. I found a link in one of the other posts (https://opensprinkler.com/forums/topic/instructions-for-testing-os-3-2-with-w5500-ethernet-module/), but it doesn’t seem to exist anymore. The only model I found was on thingiverse, but it’s for version 3.2.

https://www.thingiverse.com/thing:4639621

Could the official 3D models be uploaded to github, please? Or is that model on thingiverse the official one? I printed it, and it looks like the 3.3 boards fit. Perhaps there is no need for a specific enclosure for 3.3?

Thanks,
Miki.

Can I get the latest firmware on older ospi v1.4 board with RPI 1?

I have a ospi board v1.4 circa 2012 that’s running fine. BUT The firmware is so old at this point that the latest version of the android app does not work with it.

Is it possible to update to lateest firmware onto this super old 32 bit rpi?

If need be I can start from scratch with a suitable older rpi os. It currently has raspbian jessie on it.

AFAIK there is not upgrade path. I need a new install. Not an issue to redo the configuration

currently:
App Version: 2.4.1
firmware 2.1.8

If the old RPI is not up to it. I have an rpi 3. I suppose with a cable I could still use the old ospi1.4 board.

Black Screen @ connect – IOS or browser remote/local

ISSUE RESOLVED

I own two version 3 systems (3.2AC) Firmware 2.1.9(9) and have been very pleased since purchase. I was pleased with an older version as well so I bought two more of the later models.

Time to blow out the systems here in New York and I had not logged in to either recently. I first noticed black screen with the IOS App login. I then attempted login (which appears successful) with a browser, but likewise a black screen at either location.

Working locally at one location using local IP address and browser, same thing: black screen. At the display of the device itself all looks normal: gateway OK; local and outside IP addresses OK; time sync OK; weather update OK. Device can be pinged locally,but there is no doubt that login is successful. Upon reaching either device a login screen appears and upon connection, screen is black. Rebooted the one local device several times in order to record model/software and MAC info. Rebooting made no difference.

Something obviously happened not stimulated by a local human being!

Connection Error

I’m not able to connect to my open sprinkler off sigh via ui.opensprinler.com. I was able to connect for a short period of time. I remade my OCT token, and I checked the IP address and the port #. Everything checks out. I can connect from the app, but when I try to login from the UI, it says unable to connect. Any suggestions on what else to try?

Future of the .io domain??

Hi All!

The British government announced on October 3 that it is releasing sovereignty of its territory in the Indian Ocean and turning it over to the island country of Mauritius. Once the treaty is signed, the British Indian Ocean Territory will formally cease to exist and the International Standard for Organization (ISO) is supposed to remove country code “IO” from its specification. This in turn should trigger the Internet Assigned Numbers Authority (IANA) to deprecate the “.io” domain, refuse new registrations with a “.io” domain, and begin the process of retiring existing ones.

…Like for example “OpenThings.io” which is pretty important!

Now, it is possible that “.io” is popular enough that the IANA may make it a non-country Top Level Domain (TLD) like “.edu” and nothing will change.

I’m just raising awareness and starting the conversation for contingency planning.

I love OpenSprinkler (and OpenGarage) so much; I don’t want to lose any functionality!

vscode run on Raspberry pi 4 configuration for editing, compiling and debugging

vscode can be run directly on a raspberry pi 4 for editing, compiling and debugging the latestest 2.2.1 opensprinkler code.

The C++ extensions must be added to vscode and the attached task.json and launch.json configurations files are needed as well. The “.txt” must be removed from the file names. Also the “path” parameters must be changed to match your own opensprinkler folder location.

The compile time is a bit slow but acceptable. The break point debugging capabilities are excellent.
Since I can’t attach the task.json file here are the contents:

{
“version”: “2.0.0”,
“tasks”: [
{
“label”: “build OpenSprinkler”,
“type”: “cppbuild”,
“command”: “/usr/bin/g++”,
“args”: [
“-std=c++14”,
“-o”,
“OpenSprinkler”,
“-DOSPI”,
“-DLIBGPIOD”,
“-DSMTP_OPENSSL”,
“-g”,
“-include”,
“string.h”,
“main.cpp”,
“OpenSprinkler.cpp”,
“program.cpp”,
“opensprinkler_server.cpp”,
“utils.cpp”,
“weather.cpp”,
“gpio.cpp”,
“mqtt.cpp”,
“external/TinyWebsockets/tiny_websockets_lib/src/*.cpp”,
“external/OpenThings-Framework-Firmware-Library/*.cpp”,
“smtp.c”,
“-Iexternal/TinyWebsockets/tiny_websockets_lib/include”,
“-Iexternal/OpenThings-Framework-Firmware-Library/”,
“-lpthread”,
“-lmosquitto”,
“-lssl”,
“-lcrypto”,
“-lgpiod”
],
“group”: {
“kind”: “build”,
“isDefault”: true
},
“problemMatcher”: [“$gcc”],
“detail”: “Build the OpenSprinkler executable.”
}
]
}

Modding OpenSprinkler DC Version for Latching Valves?

Hello everyone,

I recently purchased the OpenSprinkler DC version but realized after the fact that my irrigation system uses latching valves. Unfortunately, returning or refunding the unit is not practical for me due to international shipping and customs (I’m in Europe, and the product is from the US).

I was wondering if anyone here knows of a way to modify the DC version to work with latching valves? Perhaps there’s a hardware mod or some workaround?

Additionally, is it possible to connect an extension board designed for latching valves to the DC version of OpenSprinkler? Could I use the extension board to control my latching valves even if the main controller isn’t the “DC Latch” model?

Thanks in advance for any advice or guidance!

Best regards,

Flo