-
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
-
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?
-
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 -
It's worth noting this recent (?) GitHub change:
GitHub - github/renaming: Guidance for changing the default branch name for GitHub repositories GitHub - github/renaming: Guidance for changing the default branch name for GitHub repositoriesGuidance for changing the default branch name for GitHub repositories - GitHub - github/renaming: Guidance for changing the default branch name for GitHub repositories
This will have an impact on the AltAppStore which has previously assumed the default repository name of master. So when specifying releases, you should ensure that any new plugins explicitly reference the main branch if that's the one you're expecting to use.
-
Hello @therealdb with your OpenSprinkler plugin occasionally when I set a zone for an amount of time lets say 10 minutes, something happens and the counter for 10 minutes counts down 5 seconds to 9:55 then it resets back to 10 minutes. This continues to repeat so the zone will stay on for an infinite amount of time. In my experience this usually happens once the plugin has been running for about a day (ie no recent Luup reloads). I grabbed some logs but it doesn't seem to show anything weird happening. This issue does not happen when I set a zone timer through the OpenSprinkler app. Oddly enough when I stop the zone through the OpenSprinkler app when the timer keeps resetting, the same zone gets queued right away. It seems that the plugin is sending the start zone command every 5 ish seconds.
50 06/07/21 19:19:00.469 luup_log:1304: VeraOpenSprinkler[1.50](setVar@135): setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelTarget","9",1310) old value "11" <0x6b8fe520> 06 06/07/21 19:19:00.469 Device_Variable::m_szValue_set device: 1310 service: urn:upnp-org:serviceId:Dimming1 variable: LoadLevelTarget was: 11 now: 9 #hooks: 0 upnp: 0 skip: 0 v:0x16fabd8/NONE duplicate:0 <0x6b8fe520> 50 06/07/21 19:19:00.480 luup_log:1304: VeraOpenSprinkler[1.50](setVar@135): setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelLast","9",1310) old value "11" <0x6b8fe520> 06 06/07/21 19:19:00.481 Device_Variable::m_szValue_set device: 1310 service: urn:upnp-org:serviceId:Dimming1 variable: LoadLevelLast was: 11 now: 9 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x6b8fe520> 50 06/07/21 19:19:00.482 luup_log:1304: VeraOpenSprinkler[1.50](setVar@135): setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelStatus","9",1310) old value "11" <0x6b8fe520> 06 06/07/21 19:19:00.482 Device_Variable::m_szValue_set device: 1310 service: urn:upnp-org:serviceId:Dimming1 variable: LoadLevelStatus was: 11 now: 9 #hooks: 0 upnp: 0 skip: 0 v:0x16fac40/NONE duplicate:0 <0x6b8fe520> 50 06/07/21 19:19:00.494 luup_log:1304: VeraOpenSprinkler[1.50](setVar@135): setVar("urn:upnp-org:serviceId:SwitchPower1","Target","1",1310) old value "1" <0x6b8fe520> 50 06/07/21 19:19:00.495 luup_log:1304: VeraOpenSprinkler[1.50](actionPowerInternal@785): [actionPower] #1310 - 5 <0x6b8fe520> 50 06/07/21 19:19:00.495 luup_log:1304: VeraOpenSprinkler[1.50](sendDeviceCommand@254): sendDeviceCommand("cm",{ 1="en=1", 2="t=540", 3="sid=5", 4="pid=-1", 5="uwt=0" },1304) <0x6b8fe520> 50 06/07/21 19:19:00.496 luup_log:1304: VeraOpenSprinkler[1.50](sendDeviceCommand@276): sendDeviceCommand - url: "http://192.168.8.225:80/cm?en=1&t=540&sid=5&pid=-1&uwt=0&pw=a6d82bced638de3def1e9bbb4983225c" <0x6b8fe520> 50 06/07/21 19:19:00.556 luup_log:1304: VeraOpenSprinkler[1.50](nil@214): [HttpGet] "http://192.168.8.225:80/cm?en=1&t=540&sid=5&pid=-1&uwt=0&pw=a6d82bced638de3def1e9bbb4983225c" - "{\"result\":1}" <0x6b8fe520> 50 06/07/21 19:19:00.557 luup_log:1304: VeraOpenSprinkler[1.50](setVar@135): setVar("urn:upnp-org:serviceId:SwitchPower1","Status","1",1310) old value "1" <0x6b8fe520> 50 06/07/21 19:19:00.557 luup_log:1304: VeraOpenSprinkler[1.50](deviceMessage@244): deviceMessage(1310,"Turning on for 540 seconds",false,15) <0x6b8fe520>``` -
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 -
Hello all, I have a thermostat in a hallway that controls the whole upstairs floor and my room seems to get way warmer than the hallway its located in. I am not able to move the thermostat, neither are there any external temperature probes available that connect directly to the thermostat.
I had an extra Z wave temp sensor lying around so thought I'd place that in my room and use that somehow in place of the internal temp sensor in the hallway.
I can't seem to think of a good way to go about this, my original plan was to use either the AVT plugin or the Virtual Devices plugin but to my knowledge they won't work they way I intend them to. So I resorted to using Reactor, but that may become very tricky since I will need to put in a lot of fail safes to make sure the heating/cooling turns on/off when expected.
Does anyone have any ideas on how to go about this? Every time I come up with a possible solution, I always find a way that it could fail and either not turn the a/c off/on.
-
Hello @mrFarmer , ever since the v2.3 update I haven't been able to login to my account attached are the logs. Before the update I was getting the wake-up error too. I rolled back to V2.2 and the plugin was stuck on "updating car status".
06 05/17/21 10:45:20.102 Device_Variable::m_szValue_set device: 168 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 1 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0x11c7b58/NONE duplicate:0 <0x7708d520> 06 05/17/21 10:45:20.103 Device_Variable::m_szValue_set device: 901 service: urn:rboer-com:serviceId:TeslaCar1 variable: LastLogin was: 1621273198 now: 1621273520 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x73394520> 01 05/17/21 10:45:20.160 luup_log:901: Tesla Car_error: Unable to select vehicle. errorCode : 400, errorMessage : HTTP/1.1 400 BAD REQUEST !! <0x73394520> 01 05/17/21 10:45:25.101 luup_device_message missing args <0x73394520> 01 05/17/21 10:45:25.101 luup_device_message missing args <0x73394520> 01 05/17/21 10:45:25.102 luup_device_message missing args <0x73394520> 06 05/17/21 10:45:25.103 Device_Variable::m_szValue_set device: 901 service: urn:rboer-com:serviceId:TeslaCar1 variable: LastLogin was: 1621273520 now: 1621273525 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x73394520> 01 05/17/21 10:45:25.158 luup_log:901: Tesla Car_error: Unable to select vehicle. errorCode : 400, errorMessage : HTTP/1.1 400 BAD REQUEST !! <0x73394520> 01 05/17/21 10:45:30.102 luup_device_message missing args <0x73394520> 01 05/17/21 10:45:30.103 luup_device_message missing args <0x73394520> 01 05/17/21 10:45:30.103 luup_device_message missing args <0x73394520> 06 05/17/21 10:45:30.104 Device_Variable::m_szValue_set device: 901 service: urn:rboer-com:serviceId:TeslaCar1 variable: LastLogin was: 1621273525 now: 1621273530 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x73394520> 01 05/17/21 10:45:30.165 luup_log:901: Tesla Car_error: Unable to select vehicle. errorCode : 400, errorMessage : HTTP/1.1 400 BAD REQUEST !! <0x73394520> 01 05/17/21 10:45:35.101 luup_device_message missing args <0x73394520> 01 05/17/21 10:45:35.102 luup_device_message missing args <0x73394520> 01 05/17/21 10:45:35.102 luup_device_message missing args <0x73394520> 06 05/17/21 10:45:35.103 Device_Variable::m_szValue_set device: 901 service: urn:rboer-com:serviceId:TeslaCar1 variable: LastLogin was: 1621273530 now: 1621273535 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x73394520> 01 05/17/21 10:45:35.156 luup_log:901: Tesla Car_error: Unable to select vehicle. errorCode : 400, errorMessage : HTTP/1.1 400 BAD REQUEST !! <0x73394520> 04 05/17/21 10:45:37.219 <Job ID="16" Name="pollnode #9 1 cmds" Device="129" Created="2021-05-17 10:45:37" Started="2021-05-17 10:45:37" Completed="2021-05-17 10:45:37" Duration="0.117271000" Runtime="0.116483000" Status="Successful" LastNote="" Node="9" NodeType="ZWaveDimmableLight" NodeDescription="Shed Inside Light"/> <0x7708d520> 02 05/17/21 10:45:37.219 Device_Basic::AddPoll 129 poll list full, deleting old one <0x7708d520> 06 05/17/21 10:45:37.220 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:HaDevice1 variable: PollRatings was: 5.00 now: 5.00 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x7708d520> 06 05/17/21 10:45:37.221 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: LastPollSuccess was: 1621273204 now: 1621273537 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x7708d520> 06 05/17/21 10:45:37.221 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: ConsecutivePollFails was: 0 now: 0 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x7708d520> 01 05/17/21 10:45:40.100 luup_device_message missing args <0x73394520> 01 05/17/21 10:45:40.101 luup_device_message missing args <0x73394520> 01 05/17/21 10:45:40.101 luup_device_message missing args <0x73394520> 06 05/17/21 10:45:40.103 Device_Variable::m_szValue_set device: 901 service: urn:rboer-com:serviceId:TeslaCar1 variable: LastLogin was: 1621273535 now: 1621273540 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x73394520> 01 05/17/21 10:45:40.157 luup_log:901: Tesla Car_error: Unable to select vehicle. errorCode : 400, errorMessage : HTTP/1.1 400 BAD REQUEST !! <0x73394520> 01 05/17/21 10:45:40.157 luup_log:901: Tesla Car_error: Could not login to Tesla API after 5 attempts. <0x73394520> <0x745ef520> 02 05/17/21 10:45:45.701 luvd_get_info mg conn can't read /etc/cmh-ludl//shared.js or /etc/cmh-lu//shared.js from filename /shared.js pPtrFile (null) <0x6ed5f520>``` -
Hey @toggledbits I recently picked up a Rachio controller for a family member and installed the plugin you have created. I have two issues and was wondering if you have any insight:
I have 2 controllers linked to one account and both controllers+zones are showing up, is there anyway to disable 1 controller from showing up? Is the best solution just to hide the extra zones etc?
Since each zone uses a custom device type, you cannot control them in the mobile app at all. Is it possible to change the device type to a dimmer or valve (something like the OpenSprinkler plugin) so that I can use the plugin in the mobile app and other 3rd party apps?
-
Hello @therealdb , I had to rebuild my sprinkler set up and noticed that none of the child devices that the plugin created automatically showed up in the same room as the parent device. The variable ChildrenSameRoom is set to 1 but all my zones are in "No Room". Is there any quick way I can get them all in the same room as the parent device? I have around 18 child devices so manually setting each room will take quite long!
New plug-in: Vera-HABridge to sync HA-Bridge status from Vera to Alexa
-
So, I was bored to see all those "device not responding" banners in the Alexa app and I created a new plug-in:
dbochicchio/Vera-HABridge
Luup plugin to syncronize Vera/openLuup status to HA-Bridge and Alexa. - dbochicchio/Vera-HABridge
This will update your devices' status to HA-Bridge and Alexa will finally reflect the correct status!
Just install, insert the HA-Bridge IP and port and you're done. It will work with lights and scenes (scene just to update the status and remove the "device not responding" banner). Colors are not supported, because
It will work with Vera bridged on openLuup, but HA-Bridge accessing the Vera's device directly (there's a special variable, look at the logs).
Very beta, feedback appreciated as always
I hope they'll add a way to query the status via voice soon
-
Installing this and will be testing. Thanks. Gave me the opportunity to update my habridge as I was running an ancient version.
Funny I lately have been struggling with problem with a real hue2 bridge but not with the habridge.Edit: works awesome!
-
Cool!
C
-
I have a version with colors, but because Christmas I'm still finishing it. I'll publish it next week, with a couple of fixes. It seems to run OK on my system in the latest two weeks.
-
V 0.11 on GitHub https://github.com/dbochicchio/Vera-HABridge/releases/tag/v0.11
What's new:
- support for colors
- bug fixing
- stabilization
