OpenSprinkler works great! Thanks!

[brians]

I happen to have an OpenSprinkler I purchased a couple years ago when my EZ-Flora died. So far it has worked fine as standalone but was surprised to see it in the store here!

Since it is winter here up in Canada and cannot actually test it by watering the lawn, I can only test using the web UI response and seems to be working.

Some minor quirks I notice...

If I turn on multiple stations too quickly in a program, instead of the open sprinkler queueing them, it seems to have more than one of the stations enabled on simultaneously - sometimes I have seen a couple, other times I have seen four on at once, which is not possible to do normally and it should normally queue them to run after each prior one is finished. I have worked around this by putting a wait of 5 seconds between each station on command in ISY program.

Other thing is I named one of my stations "Front Lawn/Side Lawn" and ISY does not show this station with  the "/" slash character. I think I have seen this before in other node servers but I would suggest to replace the / with whitespace or some other character depending on what the actual reason is. I fixed by renaming the station in open sprinkler without the / and then I had to remove/add the poly for ISY to see.

The good thing about having ISY integration and programs turning on the stations is I can water in different order now. Opensprinkler programs only water in order of the stations 01-08 and cannot have a program that does stations in order 03,06,01,04 for example. I actually rewired mine so it would water lawn in proper physical order.

Edited March 6, 2022 by brians
add more info

[Javi]

Hi @brians,

Thanks for the feedback!

My main use cases are integration with Flume for broken drip lines which go unnoticed until I see plants in distress and having remote access from ISY Portal and UD Mobile.

This was my first Node Server so I'm sure there will be other issues once the watering season has started.   The multiple statations issue should be reported to OpenSprinkler as that appears to be a firmware issue. I'll try to replicate and report and update the Node Server known issues so users can know they must add a delay in programs. 

[brians]

@JaviOne more thing you could add is a query option from ISY, not a huge deal but I just noticed was not available.

 

 

[Javi]

Thanks @brians. I've added your requests to the the issue tracker.

[brians]

@JaviNot sure when it happened but the Opensprinkler Node server seems broken after some update I did.

I do not check on it all the time because we still have snow, but I just noticed that I get a message to Please set or check open sprinkler password and IP Address. I tried removing/adding the Node server and the fields ipaddress and password do not appear as default. I tried adding via custom parameters and still does not work.

 

[stevehoyt]

to @Javi and any others interested in sprinkler monitoring

 

I am doing the same thing as you javi, only using the rain machine node server and flume.

 In addition to your application, my main reason is to detect broken lines and timely repair them as we are in a drought. 

[Javi]

Thanks @brians. I'll have to take a look next week sometime, I'm still on 3.0.44 as I need a stable version of PG3 for frontend integration into UD Mobile. I'm saving the upgrade tests for last but should be in the next few business days. What PG3 version are you using?      

Hi @stevehoyt, I'm doing the same as you, it was your idea ?  

[brians]

I’m on 3.0.55

 

[Javi]

I think this was just a case of me forgetting to push fixes to production. Please try version 2022.01.24 when available. There currently appears to be an issue when updating the store, so if the Node Server is missing from the store, try again at a later time.  Thanks.

[brians]

@Javi, I deleted and re-installed and is working again.

Just need to get rid of a foot or so of snow on my lawn before fully testing

 

[Javi]

Great!   I've got about a month also. The version pushed last night has been running on 2 ISYs for about two and a half months without issues.  

[sjenkins]

Hey @Javi,

Been working great for me since the start.

I'll show you below an oddity.  Notice my station 8 is outside the OpenSprinkler Stations.

I cannot move it back in ; no way ; no how.  Other than deleting the node server and adding it back which seems more effort than its worth.  My OCD is killing me though.  

This is NOT a problem, just odd.  Please do not waste any of your time on it, just keep it in the back of your head if you notice something which can cause this on one of your edits.

 

[Javi]

9 hours ago, sjenkins said:

Hey @Javi,

Been working great for me since the start.

I'll show you below an oddity.  Notice my station 8 is outside the OpenSprinkler Stations.

I cannot move it back in ; no way ; no how.  Other than deleting the node server and adding it back which seems more effort than its worth.  My OCD is killing me though.  

This is NOT a problem, just odd.  Please do not waste any of your time on it, just keep it in the back of your head if you notice something which can cause this on one of your edits.

 

Very odd indeed.

Can you verify un-grouping all stations from the parent node,  then re-group stations has been tried?

[brians]

@Javi

Seems to be an issue after updates as per this thread... my other node servers are ok.

 

[Javi]

16 hours ago, brians said:

@Javi

Seems to be an issue after updates as per this thread... my other node servers are ok.

 

Thanks, replicated.   Python may not be configured for Tk

[Javi]

Should be fixed in version 2022.07.01

[brians]

21 hours ago, Javi said:

Should be fixed in version 2022.07.01

That version is only in non production store and you have removed from production?

 

[Javi]

2 hours ago, brians said:

That version is only in non production store and you have removed from production?

 

Looking into the issue. 

[Javi]

Should now be active in the production store.