Organizing/ structuring rule sets and rules

[Pabla]

Been trying to call the service automation:trigger to trigger an automation on my HA. Below is the screenshot of the reaction but every time I hit the play button to test it nothing happens. I called the service locally on HA and it worked fine. MSR latest-22203-d7cd6357 and HA 2022.8.3. No errors in HASS logs or Reactor logs.

Edit: Higher quality screenshot

[Pabla]

Figured out the correct way, instead of using x_hass_systemcall_service you'd instead find the entity of the automation you'd like to trigger and set the action to x_hass_automation.trigger

[toggledbits]

OK. I would have liked to see logs posted for this, because the logs should have both the payload sent to Hass, and the full response from Hass. If you get a chance to try it the other way, please post those logs. But as you see, there is often more than one way to do things, and if what you're doing works, good on you for putting it together.

[Pabla]

@toggledbits went ahead and got the logs for the initial way only this time I didn't include data in the string.

[latest-22203]2022-08-15T00:35:05.068Z <HassController:null> HassController#hass: sending payload for x_hass_system.call_service on System#hass>system action: [Object]{ "type": "call_service", "service_data": { "data": {  }, "target": { "entity_id": "automation.bar_alarm_is_not_on_actionable_notifications" } }, "domain": "automation", "service": "trigger" }

[latest-22203]2022-08-15T00:35:05.075Z <HassController:ERR> HassController#hass request 1660523705069<2022-08-14, 5:35:05 p.m.> (call_service) failed: [Object]{ "id": 1660523705069, "type": "result", "success": false, "error": { "code": "invalid_format", "message": "extra keys not allowed @ data['data']" } }

[latest-22203]2022-08-15T00:35:05.081Z <Engine:INFO> Resuming reaction Bar Alarm Not On<SET> (rule-grpo90sc5u:S) from step 1

[latest-22203]2022-08-15T00:35:05.081Z <Engine:INFO> Bar Alarm Not On<SET> all actions completed.```

[toggledbits]

OK. So you can see the error being reported in the second line. Your payload, reported in first line, still sends data, which is apparently not expected by Hass. Figuring out the right form of payload to send is the key here.

[Pabla]

So the issue was using data and target all that was needed was the automation's entity ID. Should look something like this now:

{
    "entity_id": [
        "automation.bar_alarm_is_not_on_actionable_notifications"
    ]
}