Loading...
This is a generic ember plus module - successful use of this tool requires use and familiary with Ember Plus Viewer or a similar tool to identify the Ember Paths, and types, to be monitored and controlled.
The module only supports connection via TCP.
Some devices support mDNS announcements according to the Ember Plus specification. The module should discover these, otherwise device IP and Port can be manually entered.
If you require matrix control, enter the ember path(s) here.
Defines matrix behaviour.
Paths defined here will be registed with the host on initialisation, they are available as variables and for use in feedbacks.
Central to the concept of ember+ is the address or path of the data element you wish to monitor or change. There are several ways to represent these in the module. Principally as decimals and strings. Regardless of the preferred method, one should be consistent - undesired behaviour can occur if the same path is specified in both methods across different actions and feedbacks.
Paths can always be entered as a decimal address (ie 1.2.3.4). Forward slashes, as used in Ember+ Viewer, will be automatically substituted.
Paths can also be entered as a period seperated string. Such as Path.To.Ember.Node. These text paths can be found in Ember Plus Viewer, however they need to be reformatted to use period seperators rather than forward slashes. Note: ' ' & '#' characters used in ember paths are not supported for use in variables by companion, and will be replaced by '_' in variable ids - the path can still be used in actions and feedbacks however.
Any path field that contains brackets [] will just use the contents enclosed in the brackets as the path, if it is a valid decimal path. Thus you can copy paste any path with text and decimals from Ember Plus Viewer, and keep the text for readability or enter your own description This is a very useful path[1.2.3.4]. Only the path will be used for variable creation. This method cannot be used in config fields.
Except in the module configuration, all of the above can be constructed with variables for both actions and feedbacks when using the Path from String option.
For Set Value Actions one must ensure the correct data type is selected. In particular confusion can occur between Integer and ENUM types.
Ember+ devices may expose executable functions (such as triggering snapshots, firing macros, or executing remote methods).
Function node on the target device. Arguments can be passed comma-separated (e.g. 123, "text", true), line-separated, or as a JSON array (e.g. [123, "text", true]). Dynamic Companion variables are supported.Parameter Compare Number, Parameter Equals String, and Parameter True type coerce all data to the respective data type, thus can be used on any node type. Ie, you can check a boolean node with the Parameter Equals String feedback by setting the Value to true. However, the path dropdown for each feedback is filtered to parameters of the appropriate type(s) for ease of use. Prior to version 2.5 all data was coerced to strings prior to equality tests. The path field for Parameter Compare Number and Parameter Equals String presents a dropdown of registered paths. New paths (including variables) can be entered and if valid will be automatically registered and added to the dropdowns and variable list.
The Action Recorder can record Set Value actions for ember parameters you are currently subscribed to.
Generic
CommunityGeneric
CommunityGeneric
CommunityGeneric
CommunityGeneric
Community