Forum Replies Created
-
AuthorPosts
-
May 28, 2017 at 5:16 pm in reply to: Moving home and (probably) leaving my OpenSprinkerPi behind #46452
StephenParticipantSamer,
The benefit to me of assigning a static IP address on the device is that, in theory, I always know what to type into Terminal when I am upgrading its firmware & software, and I don’t therefore need to do a network LAN scan!I already have another device (a NAS) in my router that has a static IP, but, if I understand you correctly, you are suggesting I use the mac address of the device and reserve a range of IP addresses via DHCP for that mac address – right?
May 27, 2017 at 5:38 pm in reply to: Moving home and (probably) leaving my OpenSprinkerPi behind #46442
StephenParticipantSamer,
Thanks for the quick reply!
Just so I’m sure. it boots into AP Mode so it can be found by typing in 192.168.4.1 and then, once connected to my WiFi network, it reboots into Client Mode I can change the IP range to something different to match my router?
In my setup, my router’s IP range is 10.0.xx.xxx so I can set the OpenSprinkler 3 to that IP range and with a static IP of say 10.0.0.111?
If this is the case, this new hardware looks ideal for me to leave behind when we sell our home, as the new owner would only have to find the “3” by using the same range of IP on their router – 10.0.xx.xxx or, if different, reset the “3” to factory and then typing 192.168.4.1, find it there, then change the IP address to whatever they desire.
Only issue could be that my modified configuration settings for the names of the zones and the watering times would be reset, but, I guess I could give them a copy of the config file and they might be able to upload it once they have reset the “3” to their desired range.
Does that all make sense?
May 26, 2017 at 7:18 pm in reply to: Moving home and (probably) leaving my OpenSprinkerPi behind #46432
StephenParticipant*Updating this thread*
Since starting this thread, I note that there is anew product that might really suit me the OpenSprinkler 3.
It has a tiny OLED screen where you can see the IP address of the device, and this might make it simpler to manage for the new owner of our home when we sell it!
It’s WiFi only I think, but as there is no ethernet cable running to the existing Pi, and I connect using Wii anyway, this won’t be a problem.However, setup might be tricky. I’ve read the OpenSprinkler v3.0 Getting Started Guide and it looks like it boots into 192.168.4.1 whereas my current router setup is 10.0.0.xxx.
Could I still set up this new OpenSprinkler 3 if I set my laptop to this new range – 192.168.xx.xx and, once set up, change the device’s IP address from 192.168.xx.xx to 10.0.0.xx?
I think this might work, but would appreciate feedback.
December 14, 2016 at 8:00 pm in reply to: Moving home and (probably) leaving my OpenSprinkerPi behind #45005
StephenParticipantRay,
After some thought, I have decided to try a EoP setup because there is no easy way to run etherent cable into the back garden. If the two poerpoints are on the same circuit (I have two) than this setup might be more stable than my current wifi setup, and it that’s the case, may switch to an OpenSprinkler so any new home owner does not have the added (and fun) challenge of the Raspberry Pi setup.I’ll try to keep updating this thread with my progress so others can see how I go !
November 23, 2016 at 7:29 am in reply to: Moving home and (probably) leaving my OpenSprinkerPi behind #44724
StephenParticipantVendril,
Nice idea if their router has an IP range of 10.0.0x to 10.0.0.xxx – the same range as my current system.
I switched from a Billion router with a range of 192.168.1.xxx to another router with a range of 10.0.0.xxx so had to recreate some static IPs on various devices.
Oh for a world with simple IP ranges!
November 21, 2016 at 7:47 am in reply to: Export/Import Configuration – can we add date of "Export" to "backup.json"? #44701
StephenParticipantSamer,
Thanks for this – can’t wait to see it roll out!
StephenParticipantSamer,
Yes I picked up on the “OpenThings” but was alluding to the open “world” that you are creating – my post was a bit obscure – sorry!
Looking forward to you and Ray “opening” my world!
November 20, 2016 at 6:11 pm in reply to: Moving home and (probably) leaving my OpenSprinkerPi behind #44692
StephenParticipantRay,
The OpenSprinkler (and OpenGarage) project has taken home automations to another level – but also that is available to those of use who are happy to tinker a bit.
It’s looking like the TP-Link and OpenSprinkler is the way to go. During reset, am I to understand that its default setting are on a label, and then pressing “reset”, those settings are to be used to access it, and from there, I could change the IP Address, subnet mask, SSID and password to match settings of a new home nework?
ps: I could not find the device in your store – is it this one? TP-Link TL-WR802N
StephenParticipantSamer,
I’m loving the “OpenWorld” but admit that I was getting a little confused with the heirarchy of websites and forums.
I guess you will be using “OpenWorld.io” as a portal for all the other projects so you can either find “all things open” at this site and then get re-directed, or just go direct – right?
Thrilled the databases will be shared – thereby, presumably, if I wish to log into one or other of the sites, I can use the same User details – right?
November 20, 2016 at 3:29 am in reply to: Moving home and (probably) leaving my OpenSprinkerPi behind #44661
StephenParticipantKSprinkler75,
I qiute agree that many people won’t have a clue how a sprinkler system works, has never changed their own car oil, calls the repair person when something breaks and never touched a lawn mower.
Our home only runs a small 7 zone system with 8 valves, but I have put a lot of time into it to get the watering set up well for each garden bed, and the garden is an asset to the home. I would not want it to “die of thirst” because a new owner can’t access the OpenSprinkerPi or an OpenSprinkler, and, where I live, don’t reckon there’d be too many OpenSprinkler experts on call.
Any new owner would probably just go to the local hardware store and buy an 8-zone device that they or someone else can set up, but I was thinking of advertising the house with a “mobile-phone-ready” sprinklers system.
Unless the “OpenSprinkler + TP Link wireless bridge” is easy to set up, and I swap over to this setup, perhaps I just won’t mention the sprinklers!
November 20, 2016 at 3:21 am in reply to: Moving home and (probably) leaving my OpenSprinkerPi behind #44660
StephenParticipantSamer,
I’m leaning towrds an OpenSrinkler with TP Link wireless bridge for ease of setup for a new owner. Before we sell our home, I may switch from an OpenSprinkerPi to an OpenSprinkler with TP Link wireless bridge, but, truly, how easy would it be for someone to inherit my OpenSprinkler system and change to their network details.
Is the TP Link Wireless bridge easy to re-configure with new modem/router SSIDs and passphrases?
November 18, 2016 at 6:37 pm in reply to: Moving home and (probably) leaving my OpenSprinkerPi behind #44621
StephenParticipantRottenMutt,
Thanks for your reply. I just can’t imagine someone buying my house with its automated sprinkler sytsem and then telling them they need to unhook it all from the wall, bring it inside, hook it up to a keyboard and monitor and then run the wifi setup as you kindly suggested.This is no slight on your comment, but only on the “process” of introducing someone to the Raspberry Pi/OSPI world. It would almost be easier to just buy an off-the-shelf, unless I created a “paint-by-numbers” instruction sheet for all this!
As you suggested, wouldn’t it be great if there was a button on the OSPI or Pi to press that then pinged all readable WiFi networks and from there, you could add in your SSID passwords!
I guess you’d still need to bring the device indoors to access a keyboard and screen, but it would make the setup/handover so much easier!
ps: Followup – would an “OpenSprinkler” be easier to set up for a “noob”, because it has an inbuilt LCD?
StephenParticipantThis works for me here in Australia …
country=AU
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1network={
ssid=”YourNetworkSSID”
psk=”YourVerySecretPassword”
}
StephenParticipantLoads of little issues, but nearly resolved …
I forgot to mention that I am using Raspian “Jessie” but following the oh-so-clear instructions here (updated 8th February 2016) , I found my problems and fixed them…
Samer, I remote-desktopped into my Pi and it could not see the internet through the inbuilt browser, so your post got me started. Next I had to work out what to do, and apparently, networking changed in Raspian “Jessie”. I had to check/update three files:
/etc/network/interfaces
/etc/wpa_supplicant/wpa_supplicant.conf
/etc/dhcpcd.confAt home, my router has two WiFi networks – a “normal” one and a “5G” one so in the “wpa_supplicant.conf” file, I added their network details – SSID & Network keys.
In the “dhcpcd.conf” file, I created two new entries – a static IP address for the “eth0” and another for the “wlan0” interfaces.
After a “sudo reboot” I remote desktopped again and the Pi browser could see the ‘net so I felt I was getting closer.
Now the “git clone …” command worked, but I still had to remember to change into the new directory with “cd OpensprinklerGen2″ before the “./build.sh ospi” command would work.
So many little things!
The build was successful – now I am running:
App Version: 1.4.10
Firmware: 2.1.6(2)
Hardware Version: OSPi-ACps: I am happy to post the settings here if anyone else would like to see what I did
StephenParticipantDuring its setup, I have it hard-wired to a WiFI extender and have installed XRDP so can see the Pi’s screen using Remote Desktop on a mac.
Thinking about what you said, I launched the browser on the Pi, and got an error resolving “www.google’com” so you might be right!
Do I correct this error inside the Pi, or inside my router?
StephenParticipantI was thinking exactly the same thing a few days ago because we had torrential rain and the power point blew.
Luckily, I could eventually wifi myself back into the OSPI but I was wondering the same thing, given my enclosure setup!
StephenParticipantWow, that was quick!
Yes, it has been fixed in version 2.2.30 that I just updated using the “System Update” plugin! Thank you, everyone!
Attachments:
StephenParticipantFor the “email_adj” plugin, would it be possible to add a field in the setup window called “Send Test Email” or something like that? That way, we could test our settings and make adjustments, rather than having to wait until the OSPi started its next cycle.
I have set it up with my email settings but as it is pouring with rain here in Brisbane, I had turned the whole sytem OFF through the GUI (not at the wall). In order to check my settings, I did a “run-once” but did not receive an email, so I suspect my email settings might be incorrect.
The plugin asks for “GMail username” – did this mean only email addresses like this work – “[email protected]” – or will email address hosted through Google APPS also work, so an email address like this – “[email protected]” – would work?
StephenParticipantDan,
I have just updated my OSPi using the “old-fashioned” git pull, and I am pleased that you have changed how the plugins work.
Ever keen to see new things you guys are creating, I browsed to the plugins page, and note there is a small typographical error – you have “BROWS MORE PLUGINS” – it should read “BROWSE MORE PLUGINS”.
Keep up the great work!
Attachments:
StephenParticipantHa – and I thought that my setup was tricky!
Let’s forget this idea/suggestion for now. I did not consider so many variables before asking the question! I’ll just concentrate on adding a few more valves to my existing sprinkler pipes.
StephenParticipantIngo,
Thanks for your reply. Perhaps then to cover more users, the GUI could show a permanent optiion for:
wlan0:
eth0:in the interface, the OSPi could show both IP addresses if detected? In my case then, it would show:
wlan0: 192.168.1.100
eth0:and in your case, for example (using whatever your IPs are…)
wlan0: 192.168.1.100
eth0: 192.168.1.64That’s not perfect, but would cover most users using 1 or 2 interfaces into the Raspberry Pi.
-
AuthorPosts