Hi -
I’ve got PLEG working really well on a couple of Vera Lites that I’ve installed but am having crazy problems with one of them. It seems somewhere along the way I created a Condition and Action that is still in the system and won’t go away. It is a Guest Status virtual button that is the Input. The Condition was GuestOn and the action was to change some thermostat settings. I followed previous advice and had PLEG install another instance and then methodically went through the first instance and removed all Actions, Conditions and Inputs. I then uninstalled the first instance of PLEG. The ghost Condition and Action still worked so I’ve tried deleting the entire PLxx app set and it’s still there so clearly it lives on.
Is there anyway to reset this to know that everything is cleared out of Inputs, Triggers and Actions and I’ll just start over with a new PLxx?
Forgot to mention, this is at a remote location so I can’t get to the log files (at least I don’t know how) to see what’s happening real-time.
I might be able to figure out by looking at the state of your Vera.
Do not post the result … Send it to me via email … Also it could have passwords that
you have saved as parameters in to Plugins in Vera. So you may want to obfuscate any passwords in the data.
[hr]
You can get it remotely as follows:
[hr]
http://fwd2.mios.com/VeraUserID/VeraPassword/VeraSerial/data_request?id=user_data2&output_format=json
Where: fwd2 is the server to access your Vera remotely … see below VeraUserID is your user ID on cp.mios.com VeraPassword is the associated password. VeraSerial
You can find your VeraSerial and your fwd? Server from:
I have set an action for On and another one for Off and then edit it. The action tab shows one action per statud but PLTS launches 2 differents actions on the On trigger
I have done a reboot, a browser reload (CTRL+F5 in Firefox) thus still the same issue
In the advanced tab, the action
I have another PLEG with a condition that run in a infinite loop. I have edited the condition with no luck. Deleting the condition did not resolve anything, still an action
I have deleted the PLTS and still the code remain
I found that the trigger (PROGRAMLOGIC_xx) was still in the trigger list
I have disable it (can’t remove it) and then the code stopped to be executed…
I clicked on the On button of the device 194
This device has only one action (in actions tab and in advanced tab)
Actions=
{‘On’:[{‘device’:‘187’,‘service’:‘urn:upnp-org:serviceId:SwitchPower1’,‘action’:‘SetTarget’,‘arguments’:[{‘name’:‘newTargetValue’,‘value’:‘1’}]}],‘Off’:[{‘device’:‘187’,‘service’:‘urn:upnp-org:serviceId:SwitchPower1’,‘action’:‘SetTarget’,‘arguments’:[{‘name’:‘newTargetValue’,‘value’:‘0’}]}]}
But it’s launching 2 jobs (one OFF for device 190 → unwanted, one ON for device 187 → the real one)
I found the ID of the scene used by the PLTS number 92 (before I delete it) in the UserData2 (or in status URL) and used the http://ip_address:3480/data_request?id=scene&action=delete&scene=xx
Folks, Thanks for providing some details … I have found the source of the problems and will have two fixes shortly.
[ul][li]Fix the problem of phantom Actions when a PL plugin is deleted.
When you delete a PL plugin, the LAST defined Actions will be run when ANY of the defined input triggers are fired.
If you had deleted the inputs before deleting the plugin, you would not have seen a problem.[/li]
[li]I will add some startup code that will scan for previously deleted PL plugins and clean up any left over notification scenes.[/li]
[list]
[/list][/ul]
I have another strange statement…
In the PLTS 194, I have a condition called ModeNuit (NightMode) wich prevent the On status to be activate:
(OuverturePorteFenetreSalleAManger OR OuverturePorteFenetreCuisine) AND ModeNuit
->could be translated in (MainDoorOpened OR KitchenDoorOpened) AND NightMode
Actually the Plugin Day or Night is in day mode, so the On action can’t be activated
If I open one of this door, the plugin stay in Off mode, but launches scene 126 which lights up all my devices like if the plugin was in On mode
Have you ever deleted a PL device ? This may be the same phantom action I was describing.
Are you running the Scene as an Action … or does the scene have a trigger on the PL device for the appropriate condition ?
I have already tested the fix … So it will take a day or so to get through the MCV audit.
I’ve deleted a lot of PLxx because last day I had a lot of trouble that made my lights unable to be shutoff
I tought first it was the fibaro module, then I discovered that it was the Vera which aws sending a On command
Then I tought about my conditions which could be false. So I deleted all the conditions. Always the same
So I decided to delete all the PLTS that ware sending On command
With no luck till I discovered the trigger in the list
I’m running the scene as an action
The fisrt PLTS I made were by trigger on condition in a separate scene. these are running well for the moment (I do not touch anything now until the release will be published…)
Advice for those who had the same problem of launching unwanted actions by PLTS
After the upgrade to 4.0, nothing changed…
A little luup reload after, always the same…
A complete reboot of Vera, always the same…
I had to return in the action tab in all “bad” PLTS, make a change (at this stage I had strange behaviors like switching off unwanted lights in an on action), revert to old parameters and save and then Alleluiah !!
For the moment all is good, I’ll continue tomorrow in the morning my tests
Thanks Richard, you’re my hero (and my energy saver because the outside lights no more getting on in day mode)
