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 😲
OPENSPRINKLER WATER LEVEL UPDATE
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: 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. 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!
0 kommentar(er)
