Skip to content

fix(recipes): use valid trigger and action names - #8

Closed
am-official wants to merge 1 commit into
wized2:betafrom
am-official:fix/recipe-enum-names
Closed

am-official wants to merge 1 commit into
wized2:betafrom
am-official:fix/recipe-enum-names

Conversation

@am-official

Copy link
Copy Markdown

Summary

Follow-up to #7. Three recipes used names that don't exist in TriggerType / ActionType, so importing them failed:

  • charging_notify.json: trigger POWER_CONNECTED → CHARGER_CONNECTED
  • night_dnd.json: action SET_RINGER → RINGER_MODE
  • work_wifi_silent.json: action SET_RINGER → RINGER_MODE

Nothing else changes. I checked every file in recipes/ against the enums in Models.kt (trigger, condition, action type and ringer mode), and all 8 now resolve.

Target

  • beta (default)
  • main (stable hotfix only)

Checklist

  • PR targets beta unless hotfix
  • Tests for RuleLogic / pure helpers when applicable (JSON-only change)
  • No INTERNET / trackers added

charging_notify used POWER_CONNECTED and night_dnd / work_wifi_silent used SET_RINGER. Neither exists in TriggerType / ActionType, so importing these recipes failed. They now use CHARGER_CONNECTED and RINGER_MODE.
@wized2 wized2 closed this in 90a2295 Nov 6, 2026
@wized2

wized2 commented Nov 6, 2026

Copy link
Copy Markdown
Owner

Fixed on main in 90a2295: recipes now use RINGER_MODE and CHARGER_CONNECTED (valid enum names). Validated against Models.kt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants