-
I still use Vera controllers in combination with ReactorSensors. I have several Reactor sensors in use to retrieve weather data from Wunderground (i have a personal weather station), my smartmeter etc.
Recently I installed solar panels with a SolarEdge inverter. SolarEdge has an API to retrieve my power production data from their cloud.
Output is in json.So I created a new Reactor Sensor. Connection is working (query okay).
But I encounter problems at the Value Expressions. Either I get ""query okay" but no data or I get "query okay but 1 expressions failed"This is the json output
{"overview":{"lastUpdateTime":"2023-05-12 10:45:57","lifeTimeData":{"energy":476310.0,"revenue":216.577},"lastYearData":{"energy":433001.0},"lastMonthData":{"energy":433001.0},"lastDayData":{"energy":8262.0},"currentPower":{"power":5647.0},"measuredBy":"INVERTER"}}So it has different layers/levels.
I tried to put in the Value Expressions field several combinations to get the energy data of today (8262.0), like:
response.lastDayData.energy
response.overview.lastDayData.energy
response.overview.lastUpdateTime.lastDayData.energyall fail...
Who can help me with this ?
-
Home Automation means you have to have a way of describing the logical steps you want your home to implement automatically.
Whilst I've always been a fan of the Lua language, as used in Vera (and openLuup) for scenes and plugins, it's perhaps not ideal. For this reason, there has been a long development history of plugins with their own "language" to help define the automation logic: PLEG (for those with a long memory), AltUI workflows, Rules Engine, Reactor, MSR, ...
It's always seemed to me that the 'best' way of describing logic would be a language designed for that purpose – a "logic programming language". Perhaps one of the most famous, and venerable, is Prolog, which had its fiftieth birthday last year in 2022.
Thanks to some relatively recent research A Hitchhiker’s Guide to Reinventing a Prolog Machine, Paul Tarau (2017) it's become possible to implement a very efficient Prolog engine in a reasonably concise way. So, just for fun, I'm developing a CGI plugin for describing openLuup actions in Prolog.
I have an early prototype running (written in Lua, of course). It presents a web page which looks like a fairly typical Interactive Development Environment (IDE) and contains some primitives which allow basic access to the Luup engine.
Screenshot 2023-03-10 at 18.27.33.png
In a subsequent post, I'll give a glimpse of its capabilities...
-
I have the following issue: In my Vera, I have created a dimmer using the Switchboard plugin. I want this light always turn on at 100% brightness when turn the light on. By default, the dimmer remembers its last used setting. I have created the following scene: when the light is turned off, the LoadLevelLast should be 100.
9937e326-2453-43bd-bd32-917803b38e90-image.png
Manually, this works through the test Luup code (Lua), but not through the scene's action by execute the following Luup code.
I also tried in MSR, but no result
Does anyone know the solution to this?
-
Just seen notification to Netatmo developers that the current password-based login is being disabled as from October.
Oath2 is now a requirement for apps needing access to Netatmo. This will require some changes to my venerable plug-in. I’m not sure how easy this will be with the current libraries in use.
Does anyone out there use the Netatmo plug-in?
Does anyone have any advice on using Oath2?
-
Hardly a big deal, and likely user error. Bare metal install on Debian Bullseye
Observed behaviour:
TTS announcements are made with the correct volume. So a message to group 'Everywhere' with Volume 40 is announced. Asking an individual echo device to state its volume after the announcement gets the response 'This device is at volume 4'
So far so good.Using the:
x_vera_svc_bochicchio_com_VeraAlexa1.SetVolumeIn an MSR reaction appears to have no impact when either applied to the group 'Everywhere' or a specific device.
So executing this reaction:
Screenshot 2023-01-31 at 09.17.40.pngIs acknowledged by the device (with a 'beep') and shows the Lua Log below:
2023-01-31 09:21:45.778 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x5572399831f8 2023-01-31 09:21:45.779 openLuup.server:: GET /data_request?GroupZones=Office&DesiredVolume=10&DeviceNum=22&id=action&serviceId=urn%3Abochicchio-com%3AserviceId%3AVeraAlexa1&action=SetVolume&output_format=json&_r=1675156905777 HTTP/1.1 tcp{client}: 0x5572399831f8 2023-01-31 09:21:45.780 luup.call_action:: 22.urn:bochicchio-com:serviceId:VeraAlexa1.SetVolume 2023-01-31 09:21:51.670 luup.variable_set:: 22.urn:bochicchio-com:serviceId:VeraAlexa1.LatestResponse was: sending cmd:speak:<s>Volume Set</s><break time="0s" /> to dev:Office type:A32DOYMUN6DTXA serial:G090U50991550NLS cu... now: sending cmd:vol:10 to dev:Office type:A32DOYMUN6DTXA serial:G090U50991550NLS customerid:A1CVTZEBJIUFJI #hooks:0 2023-01-31 09:21:51.671 openLuup.server:: request completed (35 bytes, 1 chunks, 5891 ms) tcp{client}: 0x5572399831f8 2023-01-31 09:21:51.683 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5572399831f8 2023-01-31 09:21:51.685 openLuup.server:: request completed (930 bytes, 1 chunks, 42818 ms) tcp{client}: 0x557239726708 2023-01-31 09:21:51.687 openLuup.server:: request completed (930 bytes, 1 chunks, 42548 ms) tcp{client}: 0x5572392c0fd8 2023-01-31 09:21:51.688 openLuup.server:: request completed (930 bytes, 1 chunks, 12501 ms) tcp{client}: 0x5572392c7f88 2023-01-31 09:21:51.692 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x5572392c7f88 2023-01-31 09:21:51.704 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x557239be10b8 2023-01-31 09:21:51.704 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=66666322&MinimumDelay=50&output_format=json&_r=1675156911703 HTTP/1.1 tcp{client}: 0x557239be10b8 2023-01-31 09:21:51.905 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=66666322&Timeout=60&MinimumDelay=1500&_=1675022474387 HTTP/1.1 tcp{client}: 0x5572392c0fd8 2023-01-31 09:21:53.042 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=66666322&Timeout=60&MinimumDelay=1500&_=1675079237873 HTTP/1.1 tcp{client}: 0x557239726708However direct interrogation of the device reveals the volume has not changed.
I assume I'm doing something wrong or not understanding how this is meant to work?
One other observation is that messages announce to the 'Everywhere' group appear to make the volume 'stick' where as messages to an individual device appear to revert to the previous volume setting.
My expectation would be analagous to a radio i.e. the volume stays as it was last set, but happy to be corrected.TIA!
C
-
Anyone else seeing issues with Vera TTS? All was working fine. I assumed the cookie had expired, but even having replaced it, and seeing that the .alexa.login file is aging (as I'd expect) No speech.
I seem to be getting an odd timeout but no idea from where.
Debian Bullseye, bare metalGood call from this morning:
2023-01-18 08:22:51.657 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x563e8a2345e8 2023-01-18 08:22:51.667 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x563e89df13d8 2023-01-18 08:22:51.668 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=31085221&MinimumDelay=50&output_format=json&_r=1674030171666 HTTP/1.1 tcp{client}: 0x563e89df13d8 2023-01-18 08:22:58.223 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x563e8a4ab388 2023-01-18 08:22:58.223 openLuup.server:: GET /data_request?Text=Rachel%20has%20arrived%20at%20Washtec&Language=en-GB&GroupZones=Everywhere&Volume=50&DeviceNum=22&id=action&serviceId=urn%3Abochicchio-com%3AserviceId%3AVeraAlexa1&action= Say&output_format=json&_r=1674030178221 HTTP/1.1 tcp{client}: 0x563e8a4ab388 2023-01-18 08:22:58.224 luup.call_action:: 22.urn:bochicchio-com:serviceId:VeraAlexa1.Say 2023-01-18 08:22:58.224 luup_log:22: VeraAlexa: addToQueue: added to queue for 22 2023-01-18 08:23:09.379 luup.variable_set:: 22.urn:bochicchio-com:serviceId:VeraAlexa1.LatestResponse was: sending cmd:speak:<s><lang xml:lang="en-UK"><amazon:domain name="conversational">The temperature outside is -3 degr... now: sendi ng cmd:speak:<s>Rachel has arrived at Washtec</s><break time="0s" /> to dev:Everywhere type:A3C9PE6TNYLTCH ser... #hooks:0 2023-01-18 08:23:09.381 openLuup.server:: request completed (29 bytes, 1 chunks, 11156 ms) tcp{client}: 0x563e8a4ab388 2023-01-18 08:23:09.391 luup.variable_set:: 25001.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 0 now: 1 #hooks:0 2023-01-18 08:23:09.391 luup.variable_set:: 25001.urn:micasaverde-com:serviceId:SecuritySensor1.LastTrip was: 1674030032 now: 1674030189 #hooks:0 2023-01-18 08:23:09.394 openLuup.server:: request completed (1389 bytes, 1 chunks, 31782 ms) tcp{client}: 0x563e897eefd8 2023-01-18 08:23:09.395 openLuup.server:: request completed (1389 bytes, 1 chunks, 31662 ms) tcp{client}: 0x563e8a7c5248 2023-01-18 08:23:09.396 openLuup.server:: request completed (1389 bytes, 1 chunks, 17728 ms) tcp{client}: 0x563e89df13d8 2023-01-18 08:23:09.396 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x563e8a4ab388 2023-01-18 08:23:09.411 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x563e8a13f3c8 2023-01-18 08:23:09.412 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x563e8a79f3c8 2023-01-18 08:23:09.412 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x563e89df13d8 2023-01-18 08:23:09.413 openLuup.server:: GET /data_request?newTargetValue=1&DeviceNum=20330&id=action&serviceId=urn%3Aupnp-org%3AserviceId%3ASwitchPower1&action=SetTarget&output_format=json&_r=1674030189410 HTTP/1.1 tcp{client}: 0x563e 8a13f3c8 2023-01-18 08:23:09.413 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=31085224&MinimumDelay=50&output_format=json&_r=1674030189411 HTTP/1.1 tcp{client}: 0x563e8a79f3c8 2023-01-18 08:23:09.413 luup.call_action:: 20330.urn:upnp-org:serviceId:SwitchPower1.SetTarget 2023-01-18 08:23:09.413 luup.call_action:: action will be handled by parent: 37 2023-01-18 08:23:09.413 luup.variable_set:: 20330.urn:upnp-org:serviceId:SwitchPower1.Target was: 1 now: 1 #hooks:0 2023-01-18 08:23:09.449 openLuup.server:: request completed (35 bytes, 1 chunks, 36 ms) tcp{client}: 0x563e8a13f3c8 2023-01-18 08:23:09.461 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x563e8a13f3c8 2023-01-18 08:23:09.564 openLuup.server:: request completed (819 bytes, 1 chunks, 151 ms) tcp{client}: 0x563e8a79f3c8 2023-01-18 08:23:09.569 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x563e8a79f3c8 2023-01-18 08:23:09.581 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x563e8a32bf28Bad request from just now:
2023-01-18 18:29:26.695 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x557239889e58 2023-01-18 18:29:26.696 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=66503545&MinimumDelay=50&output_format=json&_r=1674066566691 HTTP/1.1 tcp{client}: 0x557239889e58 2023-01-18 18:29:26.799 openLuup.server:: request completed (833 bytes, 1 chunks, 2249 ms) tcp{client}: 0x557239a62f78 2023-01-18 18:29:26.911 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=66503545&Timeout=60&MinimumDelay=1500&_=1674030721531 HTTP/1.1 tcp{client}: 0x5572385f78d8 2023-01-18 18:29:27.028 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x557238b98c58 2023-01-18 18:29:27.029 openLuup.server:: GET /data_request?Text=Testing...1...2...3&Language=en-GB&GroupZones=Everywhere&Volume=50&DeviceNum=22&id=action&serviceId=urn%3Abochicchio-com%3AserviceId%3AVeraAlexa1&action=Say&output_format=json&_r=1674066567027 HTTP/1.1 tcp{client}: 0x557238b98c58 2023-01-18 18:29:27.029 luup.call_action:: 22.urn:bochicchio-com:serviceId:VeraAlexa1.Say 2023-01-18 18:29:27.029 luup_log:22: VeraAlexa: addToQueue: added to queue for 22 2023-01-18 18:29:43.149 openLuup.server:: error 'closed' sending 4 bytes to tcp{client}: 0x557238b98c58 2023-01-18 18:29:43.150 openLuup.server:: ...only 0 bytes sent 2023-01-18 18:29:43.150 openLuup.server:: error 'closed' sending 29 bytes to tcp{client}: 0x557238b98c58 2023-01-18 18:29:43.150 openLuup.server:: ...only 0 bytes sent 2023-01-18 18:29:43.150 openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0x557238b98c58 2023-01-18 18:29:43.150 openLuup.server:: ...only 0 bytes sent 2023-01-18 18:29:43.150 openLuup.server:: error 'closed' sending 5 bytes to tcp{client}: 0x557238b98c58 2023-01-18 18:29:43.150 openLuup.server:: ...only 0 bytes sent 2023-01-18 18:29:43.150 openLuup.server:: request completed (29 bytes, 1 chunks, 16121 ms) tcp{client}: 0x557238b98c58 2023-01-18 18:29:43.153 luup_log:63: BroadLink_Mk2 debug: RM3 Mini - IR 1: device is not a sensor or if a sensor; is not coded for 2023-01-18 18:29:43.153 luup_log:63: BroadLink_Mk2 debug: RM3 Mini - IR 1: veraId: 64, blId: a0:43:b0:8b:e0:e5, altId: a0:43:b0:8b:e0:e5_ir 2023-01-18 18:29:43.153 luup_log:63: BroadLink_Mk2 debug: RM3 Mini - IR 1: urn:schemas-micasaverde-com:device:IrTransmitter:1 2023-01-18 18:29:43.154 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=66503545&Timeout=60&MinimumDelay=1500&_=1674066518681 HTTP/1.1 tcp{client}: 0x557239a62f78 2023-01-18 18:29:43.155 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557238b98c58 2023-01-18 18:29:43.157 openLuup.server:: request completed (591 bytes, 1 chunks, 16460 ms) tcp{client}: 0x557239889e58 2023-01-18 18:29:43.161 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557239889e58 2023-01-18 18:29:43.175 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x5572399f30e8 2023-01-18 18:29:43.176 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=66503545&MinimumDelay=50&output_format=json&_r=1674066583172 HTTP/1.1 tcp{client}: 0x5572399f30e8 2023-01-18 18:29:57.979 luup.variable_set:: 20380.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: 22 now: 21 #hooks:0Any thoughts?
Cheers
C
-
Hello, I'm looking for a way to create a script/executable file I can launch from my Loupedeck controller that will trigger outlets on a Zwave power strip. Can anyone point me to some info on how to do this?
I'm using a VeraPlus controller
Thanks
-
I use the excellent SiteSensor plugin of @toggledbits for some years to get the data from my PWS on Wunderground.
This has worked flawlessly but recently it suddenly stopped working.
I see this in my Vera:6899a8b1-ad67-430a-9dc8-f1da42b04b62-image.png
When I copy/paste the URL code to be queried in my browser this still works.
This is the URL:
https://api.weather.com/v2/pws/observations/current?stationId=ILIMBURG130&format=json&units=m&numericPrecision=decimal&apiKey=xxxxxxxxxxxxxxxxxxxxxxxxxPatrick (or someone else on this forum) can you help me solve this ?
Many thanks in advance! -
Virtual HTTP Devices plug-in:
I wanted to try this out. Installed the plugin and created one device, which came up as a light bulb. So far so good. In AltUI I clicked on the On/Off slider on the page. The log shows that the Target is set to one. Likewise for the Variable list in AltUI. However the Status never gets set to one and the light bulb icon doesn't go yellow.
In some plugins you set the Target and then the plugin checks the physical device actually went on by checking an actual status report from the device, which can be used to set the variable Status.
In other cases a plugin will send a message to the physical device but that device will have no status feedback mechanism available. So the Status variable has to be set locally when the Target is set and everybody hopes the physical device all worked.
Not to sure what Virtual HTTP Devices plug-in does in this regard? Does the above go in anyway to explaining what I'm seeing? Is the plugin looking for status feedback?
-
I have a couple of issue with Openluup ATM. I'm going to work through them in the order that they appeared if that's OK 🙂
OpenLuup on bare metal (Debian Bullseye) running Z-way server and Z-wave.me
Issue:
Error displaying device 0-20510 - urn:schemas-upnp-org:device:BinaryLight:1 nil is not defined
I deleted a (I think) virtual switch in OpenLuup
Now when I call up all devices I have this in a 'tile'And below (in room 101)
ReferenceError: nil is not defined at eval (eval at evaluateConditions (http://192.168.70.249:3480/J_ALTUI_verabox.js:960:18), :1:1) at Object.evaluateConditions (J_ALTUI_verabox.js:960:18) at Object._evaluateConditions [as evaluateConditions] (J_ALTUI_verabox.js:1642:37) at Object._evaluateConditions [as evaluateConditions] (J_ALTUI_multibox.js:629:89) at Object. (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2572:23) at Function.each (https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js:2:2976) at _getDeviceIconPath (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2569:10) at _deviceIconHtml (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2739:18) at _internalDeviceDraw (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2765:19) at _deviceDraw (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2840:4)Any ideas from anyone?
Full reboot has been done....
Cheers
C
-
I've been trying to figure out Reactor but I'm not very good at programming.
I have two scenes in VERA.
One scene should only run during the DAY and then stop running.
One scene should only run during the NIGHT and then stop running.My scenes start off at the right times, but they do not turn off. I created a Sunrise/Sunset Reactor trigger and added it as a condition to each of my scenes.
However, the Reactor trigger when tripping or untripping does not prevent my Vera scenes from running. It will start them correctly the first day, but after that, both scene stay running and fight with each other. What am I doing wrong?
Thanks for any help!
If you are interested, here are the actions I wish to perform with each scene.
FARM STAND - DAY (runs at Sunrise)
Turn ON a device called LETTUCE LAMP
2a) Every 60 min, turn ON a device called LETTUCE PUMP
2b) Wait 15 min then turn OFF a device called LETTUCE PUMPFARM STAND - NIGHT (runs at Sunset)
Turn OFF a device called LETTUCE LAMP
2a) Every 135 min, turn ON a device called LETTUCE PUMP
2b) Wait 15 min then turn OFF a device called LETTUCE PUMPThis sounds simple, but I cannot figure out how to disable these scenes when the theyre not supposed to run.
-
I am no longer using any VERA scenes. I am only using a REACTOR trigger and activities.
Will my activities do what I need them to do? See below:
Here's what I am trying to accomplish:
AT SUNRISE
Turn ON a light called LETTUCE LAMP and keep it ON.
2a) Turn on a device called LETTUCE PUMP for 15 min each hour.
2b) Repeat the pump cycle all day long.AT SUNSET
Turn OFF a light called LETTUCE LAMP and keep it OFF.
2a) Turn on a device called LETTUCE PUMP for 15 min then wait 2 hours..
2b) Repeat the pump cycle all night long. -
Hey @toggledbits updated to Reactor 3.9develop-21009.1600 on my VP running 7.32 and I keep getting this pop up and can't change anything in my reactor sensors because of it. I am running Alt UI 2.52 and there are no updates for it. Screen Shot 2021-03-31 at 8.33.47 PM.png
-
FYI.
Recently a new ALTUI version got pushed out, release 2553. After the update Reactor is no longer showing any of the Control panels in a sensor. looking at the ALTUI changes they seem minimal so in J_ReactorSensor_UI7.js I upped the _MAX_ALTUI_VERSION to 2553 and all seems to be working again.
-
Good evening, all.
Is there a simple readme to set up and use a Broadlink device with OpenLuup?
The readme on github points to a thread on the old forum, and thence to a rabbit hole.Is it just a case of adding IP address of the device? Or does it need the MAC?
Then how do I fire commands? It looks like I need to find the codes and send via Lua?
TIA
C
-
Hi Patrick,
A quick question about your virtual sensor plugin. I saw that the child sensors rely on polling for sensor data updates. Was there a reason not to use a watch on the underlying (source) state variable as opposed to polling. I'm asking in the sense that I need a fairly rapid response to a rise in humidity, but am unsure how to set sensor polling without adding additional io drag to openLuup.
I currently use the state humidity variable directly in a reactor sensor (the data is captured via a bluetooth device with multiple humidity variables), however, these state humidity variables have a generated name making it difficult to determine what is what in group of approximately 10 state humidity variables. So a virtual sensor solves the naming problem, while creating some trigger delay due to polling.
Thx
-
@toggledbits
I have Reactor running under openLuup (which is running inside vwout's Docker container).
On the activities tab, it tells me I should update to a newer version of the device information database. When I go to the Tools tab, for a fraction of a second I can see the green "Update Device Info" button along with the Troubleshooting & Support and Device Spy sections. But after that fraction of a second, they disappear and I only see the Test Tools and Update Device Information Database sections, to just above where the Green button used to be.I've tried this on both Edge and Firefox with the same behavior (with extensions both on and off).
Any suggestions?
-
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!
I could try out a few test cases but messing around with luup.chdev.append() is tricky. If the appended info changes, a luup.engine restart occurs. Any stuff ups and this can go into a continuous loop. Plus I don't want random new devices scattered all over my installation.
So imagine a plugin that controls say ten binary lights, ten dimmers and ten blinds/shutters:
the plugin should have in the device file D_xyx.xml the tag:<handleChildren>1</handleChildren>
OK it makes sense for the parent to have the routines to control the child devices.
Question: when wouldn't the plugin parent not have the code to control its children? ie
<handleChildren>0</handleChildren>
Seems redundant or I have misunderstood something?
The service files for both dimmers and blinds have the function: <action> <name>SetLoadLevelTarget</name> <argumentList> <argument> <name>newLoadlevelTarget</name> <direction>in</direction> <relatedStateVariable>LoadLevelTarget</relatedStateVariable> </argument> </argumentList> </action>And to call the action in each case, we have say 'dimmingLevel' vs 'blindPosition':
luup.call_action('urn:upnp-org:serviceId:Dimming1', "SetLoadLevelTarget", {newLoadlevelTarget = dimmingLevel}, deviceId) luup.call_action('urn:upnp-org:serviceId:Dimming1', "SetLoadLevelTarget", {newLoadlevelTarget = blindPosition}, deviceId)Question: how do you direct the same calls to different functions in the plugin - one to dim the light and the other to postion the blind? It would seem that you would have to look at the target child device and see what type it is, then act accordingly? An example would be good!
In this plugin, devices can come and go - not often - but still needs to be attended to in the code. So the luup.chdev.append() call is executed at every start up. Each child has a descriptive name. When the child is first created this name can be set up by the software to say "Light 1" to "light 10". The user can then subsequently change this descriptive name.Question: How do I know that this descriptive name has been changed by the user and needs to be preserved and how do I check what this descriptive name is ready for when the luup.chdev.append() call is executed? As the function needs this descriptive name.
And I wonder how openluup (without looking at the code) emulates the C blob:
local childDevices = luup.chdev.start(THIS_LUL_DEVICE)
-
All,
Due to changes in the push notification system by Apple, the plugin to send push notifications to HomeWave will have to be updated. Please use the link below. This plugin works on both Vera and OpenLuup platforms.
Push messages will continue to work with the old and the new plugin. Once the server and the HomeWave app are updated, the old plugin will stop working
http://www.intvelt.com/files/HomeWavePush.zip
(Tip) Pushover and Original Reactor using openLuup / ALTUI
-
UPDATE: With @toggledbits 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. Editing the J_ReactorSensor_UI7.js is not an undertaking for the simple user
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. I'll leave it posted for a bit in case someone knows WHY it got hosed.
Sorry,
ChrisGuessing this is the most appropriate area in which to post this . . .
In case nobody has written this yet, I've been using Pushover for a while. First with VeraAlerts on Vera3/UI5, now with Reactor on openLuup/RPi3.
Until recently, Pushover has constrained us by only allowing select notification sounds. Now pushover.net will allow you to upload custom sounds to their internal library.
You may then add these sounds to Patrick's J_ReactorSensor_UI7.js file
values: [ "=(device default)", "none=(none/silent)", "vibrate=(vibrate only)", "pushover=Pushover", "bike=Bike", "Bubbles=Bubbles (VA)", "bugle=Bugle", "cashregister=Cash Register", "classical=Classical", "Cloud=Cloud (VA)", "cosmic=Cosmic", "falling=Falling", "gamelan=Gamelan", "incoming=Incoming", "intermission=Intermission", "iPhone_Ding=iPhone Ding (VA)", "magic=Magic", "mechanical=Mechanical", "pianobar=Piano Bar", "siren=Siren", "spacealarm=Space Alarm", "tugboat=Tug Boat", "alien=Alien Alarm (long)", "climb=Climb (long)", "persistent=Persistent (long)", "echo=Pushover Echo (long)", "updown=Up Down (long)"Not sure how the above code will format here, but I searched for "Pushover" in the .js file, found the section above, and sprinkled my 3 custom sounds alphabetically into the existing group (following existing formatting)
After that, a browser refresh was all that was needed.
That's All Folks,
Don't Call Me Chrissy -
This post is deleted! -
I've updated the stable branch version of R4V (Reactor for Vera aka the Reactor Vera Plugin) so that the sound field in Pushover configuration is now a datalist, which lets you pick from the list of predefined sounds, or enter any other value you like. On Github, available now.
-
@toggledbits
Thanks!
Testing and manual typing of the custom sound names works great!
Chris
