#Opensprinkler api for free
#Opensprinkler api update
#Opensprinkler api manual
#Opensprinkler api code
#Opensprinkler api plus

Before the update I was getting the wake-up error too. Hello, ever since the v2.3 update I haven't been able to login to my account attached are the logs. js file, found the section above, and sprinkled my 3 custom sounds alphabetically into the existing group (following existing formatting)Īfter that, a browser refresh was all that was needed.

#Opensprinkler api code

Not sure how the above code will format here, but I searched for 'Pushover' in the. 'climb=Climb (long)', 'persistent=Persistent (long)', 'echo=Pushover Echo (long)', 'updown=Up Down (long)' 'pianobar=Piano Bar', 'siren=Siren', 'spacealarm=Space Alarm', 'tugboat=Tug Boat', 'alien=Alien Alarm (long)', 'gamelan=Gamelan', 'incoming=Incoming', 'intermission=Intermission', 'iPhone_Ding=iPhone Ding (VA)', 'magic=Magic', 'mechanical=Mechanical', 'bike=Bike', 'Bubbles=Bubbles (VA)', 'bugle=Bugle', 'cashregister=Cash Register', 'classical=Classical', 'Cloud=Cloud (VA)', 'cosmic=Cosmic', 'falling=Falling', '=(device default)', 'none=(none/silent)', 'vibrate=(vibrate only)', 'pushover=Pushover',

You may then add these sounds to Patrick's J_ReactorSensor_UI7.js file Now will allow you to upload custom sounds to their internal library. Until recently, Pushover has constrained us by only allowing select notification sounds. First with VeraAlerts on Vera3/UI5, now with Reactor on openLuup/RPi3. In case nobody has written this yet, I've been using Pushover for a while. Guessing this is the most appropriate area in which to post this. I'll leave it posted for a bit in case someone knows WHY it got hosed. Please ignore the entire 'Tip' below, it ended up hosing my Reactor interface and I had to re-install the Reactor 'stable' version to get back up and running. Editing the J_ReactorSensor_UI7.js is not an undertaking for the simple user 😲 UPDATE: With update for 'R4V' below, your new notification sounds will work just by typing your custom soundfile name into the Sound: field of the Notify Action. The service files for both dimmers and blinds have the function:Īnd to call the action in each case, we have say 'dimmingLevel' vs 'blindPosition': Seems redundant or I have misunderstood something? Question: when wouldn't the plugin parent not have the code to control its children? ie OK it makes sense for the parent to have the routines to control the child devices. The plugin should have in the device file D_xyx.xml the tag: So imagine a plugin that controls say ten binary lights, ten dimmers and ten blinds/shutters:

#Opensprinkler api plus

Plus I don't want random new devices scattered all over my installation. Any stuff ups and this can go into a continuous loop. If the appended info changes, a luup.engine restart occurs. I could try out a few test cases but messing around with () is tricky.

Navigate to (replace x.x.x.Not sure why, but after many years, I'm still unsure how plugins with children are meant to be coded, although I've got away with doing a few with no problems!.

Just follow the simple steps below to switch your UI:įirmware 2.1.0 and newer have the following settings by default. The application now offers an injection method which takes over Ray's OpenSprinkler UI. Starting with firmware 2.0.3, an option has been added to change the Javascript URL path for the UI. To contribute to any language please visit our Transifex page.įor current discussion about the project please refer to the forums.įor advanced users, the application supports authentication (HTTP Basic) and SSL for devices behind proxies. Language translation is crowd sourced using Transifex. The application runs completely within the user's browser (or webview) and communicates directly with the OpenSprinkler. The application is written in Javascript and HTML/CSS. Furthermore, Dan Kimberling's OSPi program is also supported. The application has been tested and is compatible with all versions of the Unified firmware for both Arduino and Raspberry Pi. This application interfaces with OpenSprinkler.

#Opensprinkler api for free

This application is available for free from the following app stores:

#Opensprinkler api manual

Designed to allow manual control, program management (view, edit, delete and add), initiation of a run-once program, viewing device status, adjusting rain delay, changing of OpenSprinkler settings and much more. © 2013-2016 Samer Albahra ( mobile interface for the OpenSprinkler irrigation device. OpenSprinkler App Official Site | Support | Changelog