Same version, just new file names. I will still publish interim build via GitHub (if necessary) and then update the Store one. It’s also on AltAppStore, if anyone want to use it.
Always best to use the “store” version, I suppose. It’ll cut down on your labor at some point as well as you won’t have to have two sets of files.
How would you suggest one converts over to the store version? Is there a migration path? Or do we have to start from scratch?
It depends. I’m not encouraging people to use the AppStore, unless they want to auto update the plug-in, but I’m not planning to release a lot of versions, it’s working OK, apart some work to better support scenes.
Anyway, if you want to use the AppStore, just install the plugin. Then go to the old device, and change:
- impl_file to I_VeraOpenSprinkler1.xml
- device_file to D_VeraOpenSprinkler1.xml
- plugin to 9301
And delete the newly created device. Reload luup ending and you’d be good.
Right now it’s not released into the store. You can check it approval progress here:
http://apps.mios.com/plugin.php?id=9301
EDIT: approved and in the AltAppStore as well.
1 Like
i see this is now available in the app store. will installing this cause any issues with the old version? i have one of the og opensprinkler units that i have held off updating for years because it works ok with the old Vera app
nope. they have different file names, so they can co-exist and run side by side.
so will this new plugin work with firmware version 2.1.7 ? As it seems this is the latest firmware my old opensprinkler supports
It should. 2.1.7 has the new endpoints.
i have tried installing this plugin a few times now, it installs ok and i assign all the stations / programs to rooms., but after some time the engine (Lua engine?) goes into a restart loop . I have had to restore from a back up once and remove the plug in once to stop the reload loop
I am sorry to hear that. Can you please share some logs? I want to make sure I can improve it.
hello I installed opensprinkler but it blocks my verasecure I tried this plugin it installs correctly and I assign all the stations / programs to the rooms., but after a certain time, the engine (Lua engine?) enters a restart loop. I had to restore a backup once and remove the plug-in once to stop the reload loop
Do you have the old version still installed?
This is very strange. Unfortunately I can’t help more with no logs provided.
I am having the same issue. What logs are you needing and how do you recommend getting them?
http://YOUR VERA IP/cgi-bin/cmh/log.sh?Device=LuaUPnP
1 Like
Ok - I had to remove the plugin from my prod system, as it was making it unusable. I installed it on my backup to see if I could replicate the issue. It appears to be doing frequent reloads, but not as bad as my prod box. attaching the log from my back up and hopefully it will provide some clues. If not, i can look at reloading it back on my prod box specifically to generate the log.luaupnp log.pdf (2.8 MB)
There’s something going on with child devices. I will take a look. Out of curiosity, do you installed it from the AppStore? Thanks.
EDIT: also, next time, please enable debug mode (there’s a debug variable on the master device), so I get the full logs, and upload in a zip in .txt format, because the PDF looks very weird. Thanks again!
I did install from the app store. It is currently un-installed, but this weekend I will play with it more and see if I can get you more data.
There’s definitely something going on with the AppStore version. I’ll try to test it later today. Unfortunately, my VeraEdge system is a mess, so I’m running this plugin on OpenLuup and I got no problems. I’ll definitely investigate more.
So now that the weather has been quite warm Ive been able to test the plugin more. When you set the switch dimmer level the correct zone gets turned on to the correct time, but the issue is that it keeps resetting to the time set. For example if I set the zone to 21% the zone gets turned on for 21 minutes, but it keeps resetting to 21 mins its never counts down.
Yep, this is by design and should set back to 0 when completed. I could try to make it updated, but it’s only a cosmetic thing. Unfortunately Vera device templates are very limited and my intention was to not create a proprietary one, in order to support the commands in mobile apps.