Difference between revisions of "Edge reasoners"
From AMTech WikiDocs
Line 7: | Line 7: | ||
[[File:erSetObservationFilters.png|850px|thumbnail|center|Select observation type]] | [[File:erSetObservationFilters.png|850px|thumbnail|center|Select observation type]] | ||
[[File:erSetObservationFilters2.png|850px|thumbnail|center|Select observation type]] | [[File:erSetObservationFilters2.png|850px|thumbnail|center|Select observation type]] | ||
− | + | =Add actions= | |
− | + | ===Select the target M2MBridge instance=== | |
− | + | ===Select the target thing instance that will execute the command=== | |
− | + | ===Select the observation type to be sent as a command to selected thing instance=== | |
[[File:erSendCommand.png|850px|thumbnail|center|Select observation type]] | [[File:erSendCommand.png|850px|thumbnail|center|Select observation type]] | ||
− | + | ===Bind values by constants, observation properties or javascript code explained in [[Binding|section]]=== | |
[[File:erBindingActionsProperties.png|850px|thumbnail|center|Select observation type]] | [[File:erBindingActionsProperties.png|850px|thumbnail|center|Select observation type]] |
Revision as of 21:26, 25 January 2017
Allows to configure reasoners to be executed by M2MBrigdes of an M2MBridge Network
Contents
- 1 Select an observation that must
- 1.1 be generated by the bridge that executes the reasoner
- 1.2 configured at the observation production configuration
- 1.3 Set constrains on observation properties if required similar to those on the thing properties explained in section, however some kind of constraints are not allowed (like proximity area based constraint) and a new one isRequired is included to ensure that the observation instance contains a given field.
- 2 Add actions