Hey I’m trying tu use the exec in a rule to execute a jq command. I’m using 1.14 of the exec binding. Running this command in a terminal will return the label of a TV channel. sudo -u openhab /usr/bin/curl -s http://209.0.0.0:8080/rest/items/LG_TV0_Channel | /usr/bin/jq '.stateDescription.options[…

It worked! Thanks Scott! I changed the rule like this: rule "Test DSL rule" when Item LG_TV0_Channel changed then logWarn("Rules", "Test: Start") logWarn("Rules", "LG_TV0_Channel changed: {}", LG_TV0_Channel.state) var current_label val state_description_options = LG_TV0_Chann…

I see. I guess the binding populates that with “discovered” data from TV. Yup, those Item options are not directly accessible from DSL rules. You could re-jig your idea to use HTTP Action to grab the target Items JSON, then use a JSONPATH transform to recover the text you want, all in a DSL rule. …

Using Jython, you can use something like this… from core.log import logging, LOG_PREFIX#, log_traceback LOG = logging.getLogger("{}.TEST_3".format(LOG_PREFIX)) # get a list of all state description options for an Item LOG.warn("stateDescription.options: '{}'".format(itemRegistry.getItem("Lock_Entr…

[image] rossko57: I presume you are using the pipe | to pass the output to something else (jq?). That was the problem. After some googleing I found that passing pipe to exec is not working so I made a script: #!/bin/bash curl -s ‘ http://209.0.0.0:8080/rest/items/LG_TV0_Channel ’ | jq ‘.state…

Thank you Scott, but I have no ideea on how to implement this :roll_eyes:

jq is notorious for problem with quote and parsing from one liners like this without a full shell. jq solves this by allowing you to define your arguments and variables before wrapping them in your query. some examples here [lisi4ok] passing arguments to jq filter jso…

[image] LaurentiuB: I have no ideea on how to implement this You could set up Jython and the helper libraries manually… Helper Libraries for openHAB Scripted Automation — openHAB Helper Libraries ... … or copy an add-on to your $OPENHAB_HOME/addons/ dir…

I begin to wonder if you can get hold of this info directly in DSL. I don’t have a suitable Item to try it out on, with real stateDescription options … but try this and see what you get var sd = LG_TV0_Channel.getStateDescription logInfo("test", "object {}", sd) logInfo("test", "options list {}"…

I thought you were asking for an NGRE example :slightly_smiling_face:. Here is how you could get an option using the rules DSL… rule "Test DSL rule" when System started then logWarn("Rules", "Test: Start") var current_label val state_description_options = Lock_EntranceFront.stateDe…

[image] LaurentiuB: That was the problem. After some googleing I found that passing pipe to exec is not working so I made a script: It’s also possible to run it in a shell if you pass the command to a shell. For example: val myText = "bash -c 'sudo -u openhab /usr/bin/curl... | /usr/bin/…

I don’t know how to use your example. I tried rule "Test DSL rule" when System started then logWarn("Rules", "Test: Start") var current_label val state_description_options = WebOS.stateDescription.options state_description_options.forEach[option| if (option.value == W…

Concatenate inside exec command

Add-ons Bindings

5iver (Scott Rushworth) October 4, 2020, 9:52pm 18

You could set up Jython and the helper libraries manually…

… or copy an add-on to your $OPENHAB_HOME/addons/ directory…

If you have any questions, just ask!