Scene Control Suite - Scene Activation

[JustinG]

Hi Mark, welcome to the forums.

@mimafamilie

run_controller('{{sceneController}}',{{undoSettings}})

The double brace “{{” is not valid javascript. These are placeholders used by the rule templates, and should have been replaced by your selected values when you created a new instance of this rule template. Are you using the new full release of OH3.2? There was a breaking change in 3.2 that uses a different placeholder syntax than previous versions, so this rule won’t work as a rule template for most of the snapshots or milestones leading up to the full release of 3.2.

Fortunately, the fix is fairly easy for now. You can do the replace manually. {{sceneController}} just needs to be replaced by the name of the item holding your metadata, and {{undoSettings}} can just be replaced by false or removed altogether. So the line would look something like this:

run_controller('SceneMorning',false)

or just

run_controller('SceneMorning')

I do also see a couple other small things in the rule and metadata that may present some difficulties. So, we should try and get those cleared up too.

@mimafamilie

triggers:
  - id: "4"
    configuration:
      itemName: Scene_Control_Suite_Abendstimmung
    type: core.ItemCommandTrigger
conditions:
  - inputs: {}
    id: "3"
    configuration:
      itemName: Scene_Control_Suite_Abendstimmung
      state: ON
      operator: =
    type: core.ItemStateCondition

You have the same item name for the rule trigger and the rule condition. I assume that this item is the one that has the metadata. In that case it is correct to have this item name in the conditions section of the rule. That part is what allows you to disable this scene completely in case there’s some reason you don’t want the scene to even be able to be activated. In the trigger section some separate item or event is expected. This is whatever you are going to do to tell the system you want this particular scene. Maybe that’s a a button push, or toggling a switch on the UI or even just an astro event.

Again, this is very easy to fix at this point since you already have the rule in the UI you can just open up the rule page, push the red button next to the current trigger to delete it and then press the green “Add trigger” button to set up a new sensible trigger.

@mimafamilie

value: ADD
config:
  Baum_Tief_Helligkeit: "26"
  Baum_Tief_Farbtemperatur: "100"
  Baum_Zentrum_Farbtemperatur: "68"

This shouldn’t actually impact the system at all, but the scene system doesn’t use the value of the metadata at all, just the config so having value: ADD isn’t doing anything for the system.