Recent Posts

Pages: [1] 2 3 ... 10

Please check your inbox as we have created a support ticket in order to help you out.

Thank you. :)

Thanks, although I don't see a support ticket in either my messages on here or email? Not sure if it got lost or something?
Program Logic Plugins / Re: Looping random events
« Last post by akbooer on Today at 01:59:27 pm »
Try this plugin

Deus ex Machina II
Program Logic Plugins / Looping random events
« Last post by johnes on Today at 01:48:59 pm »
I have a series of lights I'd like to turn on / off at random intervals.

Let's say :
 - LightA on for 5-7 minutes every 2-3 hours.
 - LightB on for 2-3 minutes every 1-2 hours.

Is something like this possible using PLEG or would I need to find a different way to script it out?  I'm not looking for someone to write it for me... just want to know which path to head down.
openLuup / Re: openLuup: Asynchronous I/O
« Last post by rafale77 on Today at 01:33:19 pm »
Completely agree. I was thinking more of the vera UI7 rather than openLuup here... I have yet to get openLuup to crash due to cpu useage.
Do not use "Sleep". And in the above code, call_delay is used incorrectly. The correct code might be (I haven't tested it):

Code: [Select]
function XXXUniqueName(stuff)
  luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "0"}, <D>)

local status = luup.variable_get("urn:upnp-org:serviceId:SwitchPower1", "Status", <D>)
if (status == "0") then
  luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "1"}, <D>)
  luup.call_delay("XXXUniqueName", 10, "")
  luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "1"}, <B1>)
  luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "1"}, <B2>)
  luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "1"}, <C>)
Plugins & Plugin Development / Re: PLUGIN: Virtual Sensor
« Last post by Rompabear on Today at 10:34:57 am »
Hi RigPapa,

While searching for an answer to my problem, I came across your thread and plug-in :)
I wish I had found you earlier as I have been looking for the functionality of a Virtual Switch but with an extra Arm/Disarm toggle for ages.

I thought that I had found my ideal answer when I came across this thread;-,86502.0.html

I have made several Virtual Motion Sensors by uploading a new I_MotionSensor1.xml  to my VERA and following their instructions to create the devices manually.
Everything works very well, with one exception.
For a few of the devices, I want to only trigger them and cannot easily send an untrigger.
I would like some of them to revert to untriggered by themselves - after a set period (30 seconds)

I have tried to install a new service using the instructions in this thread;-,102089.0.html
but the variable AutoUntrip is not created.

I don't want to hijack your thread as I've not installed your plug-in (it seems a bit overkill for my needs) but you seem to be very knowledgeable about variables and possibly know what I should do?

About negative numbers. I will try to push an update today

@tomtcom can you make graphs which not working public and give me a link to your dashboard? Also, by any chance do you have 2 or more same feeds used in different graphs?
We talked about spaces in between the key name as that is single quote. How about a variable that has a space in it's name where it is double quotes? I get 0 for value.

{ key='HeatSetpoint', deviceId=116, serviceId="urn:upnp-org:serviceId:TemperatureSetpoint1_Heat", serviceVar="CurrentSetpoint Heat"},
{ key='CoolSetpoint', deviceId=116, serviceId="urn:upnp-org:serviceId:TemperatureSetpoint1_Cool", serviceVar="CurrentSetpoint Cool"}

Spaces are not valid characters in a variable name... The current setpoint variables for all three (general, heat and cool) are all "CurrentSetpoint"... They are differentiated by the service ID, either "urn:upnp-org:serviceId:TemperatureSetpoint1", "urn:upnp-org:serviceId:TemperatureSetpoint1_Heat" or "urn:upnp-org:serviceId:TemperatureSetpoint1_Cool"... The variable names displayed in the device settings uses the space delimited name because the vera code cheats when generating the html for the thermostat devices.

Code: [Select]
{ key='HeatSetpoint', deviceId=116, serviceId="urn:upnp-org:serviceId:TemperatureSetpoint1_Heat", serviceVar="CurrentSetpoint"},
{ key='CoolSetpoint', deviceId=116, serviceId="urn:upnp-org:serviceId:TemperatureSetpoint1_Cool", serviceVar="CurrentSetpoint"}
Thank you for that. I wouldn't have know. I'll update it.

Sent from my VS995 using Tapatalk

General / Re: Leviton Dimmer/Switch OTA Firmware Updates
« Last post by shapshere on Today at 08:24:07 am »
There should be no need for an alternative. This is from the z-wave alliance.

For consumers, homeowners, integrators, and service providers, these enhancements offer tremendous benefits in terms of shorter and easier installations, richer device profiles, improved self-healing and longer battery life. With the new Z-Wave Plus certification program, the Z-Wave Alliance is introducing a series of packaging logos that will be located on every Z-Wave Plus? certified product, informing the consumer this product incorporates the enhanced capabilities of the Next Gen, Z-Wave 500 series.

50% improvement in battery life
67% improvement in range
250% more bandwidth
Three RF channels for improved noise immunity and higher bandwidth
New Plug-n-Play Network-wide Inclusion feature
Improved self-healing and fault tolerance with Explorer Frame feature
Standardized method for Over the Air firmware updates (OTA)
Improved product information capture for product certification database

There are a number of alternate solutions to vera for OTA upgrades. Since the upgrades require to reset/remove the device from the network, upgrade it and then include it back into the network, we probably don't want the vera to do it and like Homeseer does it, to use another zwave radio, create its own network and do the upgrade. I am personally using an aeotec z-stick on the side to do it.

luup.sleep is the call I think TechPigeon was thinking of here (call_delay won't work as shown), but it's a bit dicey and most seasoned Vera users avoid it (you can cause deadlocks and reloads if your delay is too long).

Why not try Reactor? It's got a built-in feature for stuff like this. I use the "repeats N times with X seconds" option to make certain switches do extra jobs, for example: if we cycle the first switch nearest the bottom of the basement stairs (which operates a light there normally) off twice within 15 seconds, all the lights go out in every part of the basement. You could easily reverse this process as well, and have an on cycle turn on all the lights. Built-in functionality. Done and run.
Pages: [1] 2 3 ... 10