You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wgplugin_info is a generic name for accessing internal values from Wiregate that are not on the bus.
However, technically it just fetches a json object and there is absolutely no reason why the plugin cannot be used for other data sources.
I.e. (by rewriting the invoked url) I wrote a node-red flow that serves global context data in the expected format for CV.
I would suggest to:
rename wgplugin_info to something more generic, i.e. "external_info" or "json_info" (wgplugin_info could stay a deprecated aliases for some time)
make the URL that CV uses to fetch the data configurable (defaulting to the current value if not configured)
describe the expected format of the calls. i.e.
single "object is fetched from configured URL with "name" as request parameter
expected response is a single json object in the format {"requested_object_name":"value"}
return empty body in case of non-existent object or other errors
The text was updated successfully, but these errors were encountered:
@ctr49 can you be a bit more precise about how this Nore-RED connection does work in this case?
And also give a bit more information for the documentation so that it'll be more easy for others to use?
We are very close to the 0.12 release, so it's a good timeframe to do a widget renaming
wgplugin_info is a generic name for accessing internal values from Wiregate that are not on the bus.
However, technically it just fetches a json object and there is absolutely no reason why the plugin cannot be used for other data sources.
I.e. (by rewriting the invoked url) I wrote a node-red flow that serves global context data in the expected format for CV.
I would suggest to:
The text was updated successfully, but these errors were encountered: