@toggledbits said in "Plugins"/firm-coded rulesets in MSR?:
OK. Let's talk about this for a minute. How do you envision that working? If you are working on an expression for a Rule, how would it establish context? Do you work from inside the rule, and if so, what is needed that is not currently provided? Same for global expressions... how would this operate differently from the global expression editor? Is it really necessary to create a separate facility, or would changes to the current expression editors somehow suffice?
I usually open two windows, and I'm working on a (disabled) test rule where I test things, and then copy it over to the final rule. The problem is that sometimes I don't want to mess existing expressions, or the expressions require values that are not evaluated until I save the rule - and then scrolling up and down. I just want a way to quickly test expressions without messing with existing expressions. Sometimes you're just testing new expressions, sometimes you're trying to tweak things. A debug tool is a better way to test, imho, since I don't need to persist the status.
Curious about this. In the MQTT example, there is a
perform()function that can be used to run an action from an expression, and you can publish anything you want (usingx_mqtt.publish), so I assume you are talking about something else. On HTTP, are you suggesting/imagining a function to perform an HTTP request and return the response as the function value?
The message could be complex, like
text: "ABC",
priority: 1,
silent: true
icon: "icon"
}
and I want to pass parameters instead of trying to compose every time dynamically.
I'd like to invoke a function, instead, and be free to change the format in the future in a single place - or define defaults if necessary. I usually have functions for things like notifications (and I'm using the same payload to decide if I want to deliver it to TVs or PCs as well), TTS (where I pass volume, if it's emergency notification, etc) or to invoke an enpoint to get cams screenshot. Right now I'm still invoking luup endpoints that translate them via UDP/MQTT, but I want to remove this depedency on luup and invoke my own HTTP endpoints - or compose an MQTT message, based on the same placeholder (my system accepts the same message via MQTT or HTTP - for the same action).
So, I just want the ability to define a function like this (pseudo code):
function sendAlert(what, silent, sendToTv, chatid, localEmoji) {
chatid = chatid or chats.group;
silent = silent or false;
sendToTv = sendToTv or false;
publishMqtt("dbdomoticz/cmd/notification",
{
text = what,
emoji = localEmoji,
chatid = chatid,
silent = silent
}
);
if (sendToTv)
sendAlertToLGTV(what);
}
And then have an action in the GUI, where placeholders are the parameters I have in the function.
GitHub - toggledbits/Vera-Decouple: Scripts to decouple Vera Home Automation Controllers from their parent cloud services
Using a Vera Edge as a network-attached zwave device (skipping the vera software)
