No sorry my explanation is weird. What I mean is that when I set the dimmer to 21 it keeps resetting the open sprinkler to 21 mins and never lets the count down go down.
Are you saying that it keeps setting it to 21 minutes and it runs indefinitely? Thanks.
Yes! Exactly what I mean
not good. I will try it again later today, I got a perfect replica of opensprinklers APIs to test it without messing with water ![]()
Hey! Ever get a chance to test the plugin? No rush just was wondering ![]()
Nope. I’ve been busy lately and been fighting with the stability of my Vera. I hope to find some time next week.
All good, stay safe!
hey @Pabla I looked at the code and I can’t repro. My Vera right now is a mess, so I can’t test it except on openluup.
I need to think more about this codce in the coming days, since it’s holiday here in Italy and we’re stuck at home until monday. I’ll keep you posted.
Let me know If I can help you with anything, enjoy the holidays ![]()
Naa, the repro steps are clear. I just need to find time to focus, since it seems very subtle.
I will probably also fix the reboot-loop mentioned by some, so I will discover zones/programs only on first installation and on demand. I will definitely release a new version in a week or less.
I just finished installing and testing my OSPi. It is running AppVersion 2.1.10, Firmware 2.1.9(3) Could someone post a simple set of steps to install the current Vera OpenSprinkler plugin? Or should I wait on this as it appears there’s a few issues that are being worked on?
Hello All -
This new plugin has been working well for me, thank you.
I’m dealing with support on a reload/reboot issue (sometimes several per hour). They are having problems figuring out why but did mention that there’s a lot of polling activity from this plugin.
While I doubt this is the cause, I have noted a lot of logging traffic for OS in the past. Is there anything I can do for this? I did note that the “debug” variable is set to 0.
I checked the logs of your controller, I found that during a time period of 1 hour there was no reloads, however, I could see that one device is particularly sending information constantly to the controller and perhaps flooding it is the Sprinkler Controller and its child devices, this could be causing the system to be saturated, you can try to change the polling settings on those devices and that might improve the situation.
Polling can be adjusted with “Refresh” variable. Default is 15, but you set it to whatever you want. I
I doubt this will cause stability issue, only more HTTP traffic.
EDIT: while they investigate why (I know: poor Zwave implementation on their part…) set refresh to a very hight value (as 1200, 20 minutes) and see if things are better.
I agree this is likely ZWave-driven and has nothing to do with OS. However, I appreciate your feedback. This will be helpful as we dig in.
So, version 1.3 is ready on GitHub. I’ve rewritten the update mechamism from scratch, so it’s now doing just one HTTP call, instead of 4. This should do less HTTP traffic on your network.
What’s new
- discovery is now done on first run only. If you want to run a configuration, you have to set Configured variable to 0 and do a luup reload. In a future version I’ll offer a Configure method.
- zone status is now in sync with the device. @Pabla, this should fix the bug you reported.
I’ve not tested it on a Vera, but on openluup only, but this should work nonetheless, since I only changed the update code.
Great update! I’ve uploaded the latest to my VeraSecure and it seems to be working great so far!
That’s great to hear @tbully! I’ll update the AppStore version in the coming days, if all reports seems to qualify this as a good release.
Obviously when the plugin is updated, it’s supposed to pour rain for the next week
gotta love living in a temperate rainforest!
well, you could test the rain delay feature, after all ![]()
I have an opensprinkler Rasbperry pi. I uploaded this from github to LUUP but when I setup a sprinker I just get the error “Unable to send command to the controller” This is just static IP on the Pi and I have no trouble accessing OSPi with a web browser