Building on the customizability recently added to the Mushroom template card, Mushroom v2.0.0 allows you to create an even distincter Home Assistant Dashboard. Besides the benefits you will experience, this update also includes a major code refactoring, which should make future development easier and thus updates more frequent.
Primary and secondary information options for all Mushroom cards
Until now, only the Mushroom Entity Card was able to display secondary information alongside the primary information. In Mushroom v2.0.0, all cards get this option. Using a dropdown, you can easily select which information you want where. Currently, the following five options are available:
- name
- state
- last-changed
- last-updated
- none
These newly added options mean that the developer could deprecate two previously used options: hide_name and hide_state. Instead of these, you can simply select none from the dropdown. If you were a user of these options, your Dashboard luckily won't break after installing the update. The developer was kind enough to enable backwards compatibility.
What you will see, however, is a warning and no option to use the visual editor whenever you edit a card using the deprecated options. In my case, I was previously using the hide_state option, and by removing that line from the code, I was able to use the visual editor once again.
Add icons or pictures to any entity in Mushroom v2.0.0
Similarly to the primary and secondary information, the way you select icons or pictures has also slightly changed and been unified. You now have the option to select between:
- icon
- entity-picture
- none
In addition to these option, the template card now gives you the opportunity to not only use Material Design Icons (MDI), but also images. Whenever you select an image, be it from the web or one you have uploaded locally, the icon will automatically be disabled.
Less code means faster development
As hinted at in the introduction, this update is much more than what you see on the surface. Due to all cards sharing the appearance configuration, there is less duplicate code to take care of for the developer. What this means for us users is that future updates will have fewer lines of code to check before each update is released.
