I bought a new Vera3 which automatically updated to UI7. I kinda like it actually; especially the iOS App! However, I’m running into a problem. I decided that one of the first things I wanted to install was PLEG; so I did, and I can’t get it to work. I started out with some pretty advanced logic (I’m a developer, so more advanced = bettter ;D).
It didn’t work. So I removed the app (only via the Web UI though, there are probably some leftovers on the FS?), reinstalled it (both PLEG and PLC), and added a simple “trigger” watching the “night mode”. I called it tNightMode if that matters. It threw me an error: tNightMode: Invalid Value token: TNIGHTMODE. When opening Status it says “Error getting status of tNightMode”. I tried switching between “home” and “night” modes to trigger a mode change event handler if such a thing exists. No dice. Restarted the Vera. No dice. Tried a simple property (defaulted to p1) reading a LoadLevelTarget of a dimmer in case the Mode-triggers was a WIP. Same thing though - “Error getting status of p1”.
I am waiting on an API for House Modes … MCV said they put it on the Schedule for the next 30 days (about 2 weeks ago)
So I expect it at the end of year.
If they hold to the schedule … I should be able to incorporate House Modes into PLEG/PLC and Vera Alerts by mid January.
The actions Editor does not work in Remote Access. The code has been fixed. But because of a bug in the App Store I can’t release it. Into week 2 on that problem.
I actually came here looking for guidance on how to use the My Modes part of the Inputs section in UI7. Does your last post mean that this is just a dummy interface for what you will be able to add in January, or have I misunderstood?
My confusion was due to there being a house mode section under inputs, where you can name each mode for use in conditions, but from what you say, I assume this is therefore non-functional preparation for what will come in Jan (any names entered are invalid variables when editing conditions).
It’s been alive for a while.
PLEG has inputs to trigger when a house mode changes.
It also has an Action (of the PLEG device) to set the house mode to any value you want.
how do I pull the modes into the conditions ?. There is a selection option for every other input apart from modes as far as I can see. I thought a condition would be created using mode the same as any other trigger. do I need to create a property or input that includes the mode to be able to use it in condition ?.
I’m trying to create something simple which has certain switches on if in home mode and off in away mode. therefore I was thinking the condition would be very simple and just include “home” so if its true the switches are on, if false the switches are off. Its getting the mode included in the condition that I can’t seem to fathom.
how do I pull the modes into the conditions ?. There is a selection option for every other input apart from modes as far as I can see.
On PLEG’s Inputs tab, you should find a sub-tab called My Modes. This allows you to define your own names for each of the UI7 House Modes. These can then be used in Conditions.
Hi Rex, I had set up the names on the tab, its pulling those names into conditions that I’m struggling with. Whatever I try it shows up as invalid.
If I’ve understood correctly setting up a simple condition using home / away should be as follows :
input - I’ve set up home to be mhome and away to be maway.
Condition - If I want a switch to be on whilst mhome is true my condition would simply be mhome
Its getting the modes into the condition that I’m struggling with, whatever I try it shows as unknown variable. This seems so straight forward that I must be missing something stupid but can’t work it out. I’ve read the getting started doc.
It works if you enter the Condition expression manually. There does seem to be a problem with the Condition editor not recognizing the mode names. I’m sure RTS will sort that out.
