There is a way to use global variables. Jython 2.7.0 definitely works with global variables. In finding a fix for Jython 2.7.1, I learned more about scriptExtensions, which can be used by any language and can be used for global variables. They basically put objects into a shared context accessible by all script engines (all scripts have their own).
As I’ve mentioned elsewhere, I also have Jython and Groovy working for scripted Actions. I will submit a PR once ESH is remigrated, and workup an example for using scriptExtensions.
Metadata is the next best thing! For example, I have metadata in most of my light Items with values for a lux level and brightness setting for each Mode (what I use for TimeOfDay, since I have Party, Vacation, etc.). When the outside lux changes, I have a rule that adjusts the lights according to the metadata for each Item in an active area of the house. I have another rule to detect activity in an area, which turns on/off the lights to values based on the metadata. Previously, this data needed to be stored in Items or in some other object in a rule script. I could add listener’s too, to watch for changes in metadata, but haven’t had the need.
For UI layout, it would be a tree for each Item, with Keys at the root, and branches of name value pairs. The data should be editable, but not sure the best way to design the UI for it.
Morning
|_ Low_Lux_Trigger: 5
|_ Level: 100
Day
|_ Low_Lux_Trigger: 90
|_ Level: 50
Evening
|_ Low_Lux_Trigger: 30
|_ Level: 50
Night
|_ Low_Lux_Trigger: 30
|_ Level: 10
Late
|_ Low_Lux_Trigger: 30
|_ Level: 1
Party
|_ Low_Lux_Trigger: 5
|_ Level: 100
Metadata essentially provides additional data points, beyond e.g. an Item’s state. Here is a writeup that I did…
Eventually, I will get a post about how to setup Area Triggers and Actions, and the rules I use. Once I get the PR out, I’ll distribute them as rule templates! Although, I have DSL versions too.
Semantic tagging uses tags, and also uses metadata for synonyms.