In the UI, you end up with the raw Java event Object. JavaScript Scripting - Automation | openHAB
This means that the properties are going to more closely map to the Rules DSL Implicit variables. Textual Rules | openHAB
rules/rules.js - openHAB JS is the source code in openhab-js that converts the Java event Object to a JS event Object. This doesn’t get run for UI rules (there’s no way we’ve found yet to intercept the event and replace it like can be done for file based rules). But you can see the code that extracts the data from the Java Object there so you’ll know what to reference in your UI rules..
case 'org.openhab.core.thing.events.ChannelTriggeredEvent':
data.channelUID = event.getChannel().toString();
data.receivedEvent = event.getEvent();
data.eventType = 'triggered';
data.triggerType = 'ChannelEventTrigger';
break;
}
So you can see that the JS event Object’s channelUID comes from event.getChannel().toString() and the actual event comes from event.getEvent(). But you should be able to just use event.channel and event.event. I know for sure event.event works at least.
There is a utility to dump all the members of an Object in openhab-js: utils.dumpObject()