This interferes with other custom cards

[McGiverGim]

First of all, thanks for your great card.

I don't know if this is expected. I have discovered that this custom card interferes with others.

I detected that the multiple-entity-row card was having a bad behavior. You can get a complete description of the issue and the tests here: benct/lovelace-multiple-entity-row#138

Finally, I discovered that the culprit was lovelace-canary. Removing it the multiple-entity-row card worked again as expected.

I don't know if this is a known limitation of the card or a bug. I used it basically as replacement of stack-in-card but if this is not a bug, I think I will need to return to it or to something similar and I like the simplicity of yours.

[jcwillox]

Thanks, this is actually expected, if two cards are handling the secondary_info option, then Canary will override its expansion. It is impossible to add exclusions for every plugin that handles its own secondary info templating, which is why the disable_canary option exists, see Disabling-Extensions.

I should be able to add an exclusion for multiple-entity-row, for now adding disable_canary: secondary_info to the configs will solve this issue.

[McGiverGim]

Tested disable_canary: secondary_info and it works. I will use it for the moment. But is difficult to know where and when this is affecting.

Thanks for your help!!!