Closed Apollon77 closed 9 months ago
I'd really appreciate this feature. In my use case it would be valuble for working with homematic methods from within NR, e.g. putParamset
, reportValueUsage
, rssiInfo
etc.
I would also definitely make use of it.
This would allow me to get rid of the Javascript adapter completely.
Like this? FYI @mickym2
You can specify the instance and the command (default is send
if empty). And the payload of the msg object is used as the message for sendTo
. Output is the result of the message callback.
same result as this blockly:
No not only to the pushover adapter - General a Node which you can use to use directly the sendTo functionality to any iobroker adapter like the generic sendTo puzzle piece.
So you can decide which and how many parameters you want to send.
Therefore I didn't understand, why this new puzzle was created:
with the generic, existing piece you could send messages to the mqtt adapter as well.
So within the node the adapter which should be addressed should be selectable, the command should be specified and variable options for parameters as requested by the adapter. Same functionality as the generic SendTo puzzle in blockly.
No not only to the pushover adapter
Of course... I've thought the pushover example is self explanatory
yes and then you need different parameters or objects depending on the receiving adapter.
and then you need different parameters
At the moment msg.payload
is used. The example above is the same as this blockly:
Please draw a mockup what do you expect.
No then its fine - so the payload is then an object with different properties as requested by the adapter!
the payload is then an object with different properties as requested by the adapter
Yes, and the output message object contains the result.
I will add the possibility to set msg.instance
and msg.command
also via the msg object for maximum flexibility.
Great
e.g. for Telegram and other cases where we want request/response like communication and adapter supports it