Forum Replies Created
-
AuthorPosts
-
TimParticipantWe are already running firmware 2.18(4), App Version 2.0.2
TimParticipantThanks Ray, No didn’t buy via the German distributor, purchased directly from your website.
Typically we would use DHCP, however in this instance we are unable too (All of our other 10+ OpenSpinklers are DHCP assigned). There isn’t a IP conflict so that isn’t causing the issue, it just seems to be hit and miss between which adapter it selects on startup (Wifi or ethernet). Given you have a Static IP as an option, I thought the problem should be something that you would want to be aware of. Unless there is a fault with our unit, it should be fairly easy to replicate.On a side note, I don’t believe there is an option to specify a Subnet Mask when assigning a static IP address, seems an odd thing to not be able to specify.
TimParticipantAny chance this could be looked at? Its sort of a big problem for us. From my testing this only seems to be a problem when setting a static IP. If I change back to DHCP the ethernet adapter stays connected all the time. Switching to a static address and about 1 in 3 reboots the wifi will take precedent and I get no connectivity via the ethernet.
Thanks
TimParticipantHi all, I’m not sure the IPv6 is the solution, when checking the TCP listening ports, I only have port 80 and 22 open after doing an update. Before the upgrade (Version 2.1.4) ports, 80, 22 and 8080 are listening.
TimParticipantThanks Kimbhoot, I have another 6 units running 2.1.7, installed about 12 months ago. All working fine on IPv4.
If in fact its IPv6 only, this will cause a huge amount of problems for our external access.Ray/Anyone, can this be confirmed 100%? Is there a way to access the old software?
September 18, 2017 at 7:16 pm in reply to: Tutorial: Install OpenSprinkler (unified) on a fresh Raspbian image for a Pi 2+ #47789
TimParticipantHi Ray, I’m just running up new OSPi (This is the 7th one I’ve done) but I’m having some issues. After deploying the “OSPi SD Card Image 2” I was able to access OpenSprinkler via port 8080. Version 2.1.4 I believe. I then followed the upgrade instruction (https://openthings.freshdesk.com/support/solutions/articles/5000631599-installing-and-updating-the-unified-firmware#install) to download the latest version, ran the build and restart the OSPi, but now I’m unable to access the web interface on 8080.
I’ve checked on the Pi and its not listening on Port 8080, only 80 and 22 after the upgrade process.. The OpenSprinkler service is running.
I’ve done this twice from scratch, thinking I stuffed up part of the process, but for the life of me, cant work it out..
Any help would be much appreciated.
TimParticipantThanks Ray. The flow sensor requires 5V. I run an OpenSprinkle Pi, so just wired this to the 5V output on the board. I’ll get the wiring colours soon and post up some more details.
I found the setting the “Flow Pulse Rate” to 0.09 is very close to be 100% accurate.
TimParticipantThanks Ray, fair point about the multiple stations, but like you said, I don’t think this is used all that often.
I miss typed IE above, was supposed to be I.E (Example). I do however agree with the Internet Explorer statement, we find chrome works 100% with open sprinkler, Internet Explorer is a bit hit and miss, well more miss.
Maybe if multiple station (Non Sequential) run maybe it could just display the total, but if all stations are Sequential it could then have a 4th column with water used per zone?
Cheers
TimDecember 4, 2016 at 9:44 pm in reply to: Remote Stations not working after Unified Firmware 2.1.7 Update #44819
TimParticipantThanks Ray, only one small problem with the button option. I’m using OSPi-AC hardware and don’t have any.
Cheers
November 21, 2016 at 6:04 pm in reply to: Remote Stations not working after Unified Firmware 2.1.7 Update #44708
TimParticipantThanks Ray, turning on “Special-Station Auto Refresh” option fixed the problem.
On a side note, “System 2” which was configured as “An Extender” before the upgrade. After the upgrade and resorting the config, the System wasn’t automatically re-enabled as an “Extender”. I also couldn’t find the option to turn this back on.??
The only way I managed to setup “System 2” as an extender again, was to change the Remote station settings configure on “System 1” which then prompted to change “System 2” to an “Extended”Cheers
TimParticipantQuite right you are.. I do feel like an idiot..
Thanks.
TimParticipantHi Ray, thank you for the very detailed response..
It was an interesting Video to watch..With your Sequential Group concept, Could I effetely put Stations 1 & 2 in a group (Group A) to run in parallel, then Stations 3,4 and 5 in a group (Group B) also to run parallel. Then schedule Group A to run for 20 minutes, and Group B to run for 30 minutes. Would the outcome then be, that station 1 and 2 run for 20 minutes together, then at the end of the 20 minutes stations 3,4 and 5 run for their 30 minutes all together?
If so, this would be perfect….Where do I find the current value in the UI? This alone would be very helpful. Maybe also if the average current draw is listed in the Logs, similar to the flow rate. This could give a bit of history to look back over to check when a problem occurred even.
I’m running the following versions.App Version: 1.4.9
Firmware: 2.1.6
Hardware Version: OSPi-ACOne again, thank you for the replay. Much appreciated.
-
AuthorPosts