Skip to content

Disabling Extensions

Josh Willox edited this page Jul 6, 2020 · 1 revision

Given the nature of this plugin, there is the potential for it to interfere with other cards or entity rows if they use the same-named options. With this in mind, you can disable Canary's access to a card or row using the disable_canary option.

Note: this is only relevant if you are having compatibility issues, there is no performance improvement. Major compatibility issues, such as with core Lovelace should be reported as an issue.

Extensions are the options that are added to the respective Lovelace elements, a list of these can be seen in the sidebar, e.g. generic-entity-row is a module and secondary_info is an extension.

Example

  • If you wanted some other plugin to manage secondary info you could specifically disable canary on that row.
type: entities
entities:
  - entity: sensor.fuel_price_average
    name: Average
    secondary_info: ""
    # there are three ways to disable canary.

    disable_canary: true  # boolean: disables all extensions.

    disable_canary: secondary_info  # string: disable one extensions.

    disable_canary:  # list: disable multiple extensions.
      - secondary_info
      - hide_warning

Clone this wiki locally