Chris

Do the script/automation trace to see why.

Check the traceback error in the `home-assistant.log`

Please verify the file is created and not blank.

At a glance it looks fine here's mine: ```yaml homeassistant: customize: !include customize.yaml packages: !include_dir_named packages auth_providers: - type: homeassistant ```

I also have an extensive list of includes and it works fine: ```yaml ## INCLUDES ## light: !include light.yaml media_player: !include media_player.yaml group: !include groups.yaml script: !include_dir_merge_named scripts/ input_select: !include...

Check the actual error message in the `home-assistant.log` file

These are the codes that get translated: https://github.com/FutureTense/keymaster/blob/a35388b0d269ba8f4487247f8d799989c442bcc0/custom_components/keymaster/const.py#L69-L91

In the case that zwavejs is emitting events, those are used, so what you are seeing is coming from zwavejs.

> So the question is why the event 21, which is correctly marked as a Manual Lock action, also referencing a code slot? This is due to the lock reporting...

You have ZwaveJS working?