Currently, intermediary action are not handled by the unit action scheduling and therefore some of the base units can not be allocated even when they offer operation services.
e.g a scenes activation state can not be scheduled, because the activation state handling is bypassing the action scheduling. This is caused by the fact that an action of activating a scene needs to provide all impacted units after the action was applied, but the action ids of the affected units are only available when the action are applied to the impacted units. In case the scene activation would take place at a later stage, the impact action ids would not be available at the time when building the action description. Therefore, a preregistration seems to be required to guarantee to full action chain while enabling intermediary action to be scheduled as well.
Task:
Introduce "REGISTERED" ActionState.
Reimplement action scheduling to support the registered state.
Use this pre action registration for all intermediary unit controller
Problem Case
Currently, intermediary action are not handled by the unit action scheduling and therefore some of the base units can not be allocated even when they offer operation services. e.g a scenes activation state can not be scheduled, because the activation state handling is bypassing the action scheduling. This is caused by the fact that an action of activating a scene needs to provide all impacted units after the action was applied, but the action ids of the affected units are only available when the action are applied to the impacted units. In case the scene activation would take place at a later stage, the impact action ids would not be available at the time when building the action description. Therefore, a preregistration seems to be required to guarantee to full action chain while enabling intermediary action to be scheduled as well.
Task: