Skip to content

Skip sending actions to OpenHAB if they do not cause a state change #80

@pLeminoq

Description

@pLeminoq

Examples

  • If a light is off because the terminating action is executing and then an agent puts on another off action, this action causes an action to be send to OpenHAB.
  • Turning the root location off will likely trigger many commands to OpenHAB for devices that are already off.

Advantages

  • By Skipping to send such an action to OpenHAB, we should generally be more efficient.
  • We could avoid issues with mapping feedback from OpenHAB to our actions

Possible Disadvantages

  • There could be problems if we are out of sync with OpenHAB. E.g. a lamp is on for real, but our representation is that it is still off. As a consequence we would not send an off command.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions