I must be missing something obvious here, but how do you get PLEG to actually save an action. I have 2 simple conditions set up (cHeatOn and cHeatOff). The action for each is to turn a Danfoss TRV to a set value and call for heat to the boiler (Secure 2 way boiler receiver). The boiler controller is essentially a dual relay switch, when I add one of the 2 switches as a device for the an action, I cannot change the state from Off to Heat. When I add the Danfoss living connect I can change the temp target, but the value is never stored.
All in all very frustrating for what should be a simple operation. I have searched and found a link to another post about PLEG not saving state, but this seems to be more fundemental than what is described in this other thread.
Please tell me what I am doing wrong!
Thanks,
Vera Newbie
I did a complete factory reset of the Vera Edge. Reinstalled the apps and started from scratch.
Nothing changed much.
So having given up on the “Control” option in the Actions tab, I am now directly setting the parameters in the “Advanced” tab.
After much trial and error I got a PLEG device to control Virtual Switches, using an Aeon 6 in 1 sensor as an input (temperature only).
I then added the Secure SSR302 “HeatOn” and “Off” commands to the actions to turn the boiler on and off. This didn’t work until I set the conditions to “Repeat”. However, the virtual switches did?
As I have not yet moved into my house, then I simply have 2 light bulbs attached to the SSR302. After adding a Danfoss Living connect TRV (but not doing anything with it yet) the PLEG device stopped working.
– NEWSFLASH –
In the middle of writing this message it has suddenly come to life. Is this some sort of polling delay?
This whole Vera/PLEG experience is not quite what I was expecting. Am I am missing something?
Any answer would be much appreciated.
Thanks.
Here is my device report -
HeatingZone1[5]
2016-04-11 18:07:07.771
Registration
Installed: Mon Apr 11 2016. 90 Day Evaluation Period which allows a total of 4 PLEG and/or PLTS plugins.
Device Properties
Name Device Name Device Variable
pLoungeTemp 6 in 1 Multisensor (temperature) CurrentTemperature
Conditions
Name Repeat Expression
cBoilerOn Yes pLoungeTemp <= 25.0
cBoilerOff Yes pLoungeTemp > 25
Actions
Actions for Condition: cBoilerOff
Device Actions:
Immediate
Device Action Arguments
VirtualSwitch2 SetTarget newTargetValue=1
VirtualSwitch SetTarget newTargetValue=0
ZoneValve1 SetModeTarget NewModeTarget=Off
Actions for Condition: cBoilerOn
Device Actions:
Immediate
Device Action Arguments
VirtualSwitch SetTarget newTargetValue=1
ZoneValve1 SetModeTarget NewModeTarget=HeatOn
VirtualSwitch2 SetTarget newTargetValue=0
Many have tried there own rain dance to get things to work.
The fact is their is still some serious problems in the Vera software that have not been fixed yet.
These are NOT PLEG bugs … But they do limit PLEG’s use. Most folks do not suffer from this problem. Other’s have the same problem with other plugins and even Vera’s components like the Scene Editor.
I have been developing the UI for the Next Gen PLEG. I an tell you there are still some performance problems in the core of the UI7 system.
NOTE: once you get your PLEG configured … The runtime component has been rock solid.
Is there a known good version of UI and App versions that work well together?
So I now have a action that works 10% of the time. If I “Do It Now” then the correct actions are performed.
I think I am missing something on how to get the actions to trigger. If I reboot Vera and the conditions for cBoilerOn are met, then although the Status reports that cBoilerOn is true the actions do not execute. Do I need some additional poll to wakeup the device? I have the repeats set on the conditions, but what is the repeat timescale?
I suspect the 10% is when the temperature on the sensor changes and the whole process is re-evaluated.
Thanks for all the help so far.
If the conditions n is already true the actions will NOT fire unless you have REPEATS set for that condition.
That allows you to run the actions ns again even though the condition is already true.