You can define a global variable at the bottom of the edit page if you start it with a @.
For a local var you can use tick the box somewhere up top that shows variable, complex and extended statements etc.
That will give you a new area at the top to define local vars and assign them to a device, static, etc.
@Keo if I am following your question correctly the app actually supports it under additional actions in your search trigger. It can parse fields within the Google items, like calendar events, and turn switches on/off based on text within the item. So webcore wouldn’t be needed.
Your description of the calendar event could be turn on kitchen, turn off dining room and it will math that against switches you define within the search trigger.
I agree. If you are just turning a variable on/off, then webcore would not be needed. I have several things that happen with specific Google calendar events, so I use webcore to make those things happen.
@keo Would the ability to map GCal event attributes to Hub Variables be useful?
This would be added to the Additional Actions section of the GCal Search Triggers but idea is at the start of the event, the variables chosen would be updated with the value from the Google Item (calendar event in your case) and then at the scheduled end it will blank out the variable value. Above screenshot is just a quick example of what things could look like.
