buttons dissapered after latest HA update 2022.3 #139

bucky2076 · 2022-03-03T09:57:22Z

I have a page with banner cards. The text caption shows, the icon shows, but all buttons are invisible.

RamiRihawi · 2022-03-03T10:12:47Z

I have the same issue, this part is not working anymore!

        map_state:
          'on':
            icon: mdi:toggle-switch
          'off':
            icon: mdi:toggle-switch-off-outline

bucky2076 · 2022-03-03T10:28:44Z

seems to me to be an artefact of the upgrade to material.

bucky2076 · 2022-03-03T10:30:40Z

entity: switch.mini_me
name: mini-me

not working either.

ajghor · 2022-03-03T11:18:53Z

not working for me neither...
Tried installing 1.0.0-beta.3, doesn't work either

psleutel · 2022-03-03T11:23:09Z

Same issue here

swampylee · 2022-03-03T13:26:57Z

Exactly the same issue here.

swampylee · 2022-03-03T18:59:22Z

This is not an ideal solution and hopefully @nervetattoo takes pity on us and fixes this but for now I added this to each switch entity in a card so I can at least see if something is on or off. When you click the switch it opens the standard entity card and then you can turn the entity on or off so an extra few mouse clicks but at least you can see the status of switches.

  - entity: switch.thing
    name: Thing
    domain: sensor
    map_state:
      'on':
        color: green
        value: mdi:toggle-switch-outline
      'off':
        color: white
        value: mdi:toggle-switch-off-outline

matteocorti · 2022-03-03T19:38:55Z

Same here.

l4r53n · 2022-03-03T22:24:09Z

Same issue here :-(

mbergdal · 2022-03-04T00:18:21Z

This is probably due to the update from Paper to Material Web Components that has been done in 2022.3 version. The problem seems to be related to the use of the in this code. (Ref: https://www.home-assistant.io/blog/2022/03/02/release-20223/#ui-upgrades)

My solution for now was to edit the /config/www/community/banner-card/banner-card.js and replace all instances of mwc-switch with ha-switch. (I also commented out the CSS-part related to ) Then save the file. (I did all this in the VSCode add-on)

To make the modified file to be served to Lovelace, you then will have to delete the .gz-file in the same folder (as it is served first if it is present). Then clear the browser cache (not only Ctrl+F5), but clear cached files. (Ref: https://hacs.xyz/docs/categories/plugins#special-notes-about-downloaded-lovelace-plugins)

Then refresh the Lovelace frontend and your switches should be present again.

Spookster · 2022-03-04T01:51:50Z

"replace all instances of with . "?
Maybe the formatting from your message is missing, but what are you replacing what with what?

mbergdal · 2022-03-04T09:59:05Z

Sorry, didn't catch that my html-tag was removed. Thanks for pointing that out :) Updated my previous post.

swampylee · 2022-03-04T10:27:27Z

Sorry, didn't catch that my html-tag was removed. Thanks for pointing that out :) Updated my previous post.

Thanks very much, this is a much better solution than mine and works great.

ajghor · 2022-03-04T11:18:27Z

@swampylee Many Thanks!
It is alive!

l4r53n · 2022-03-04T12:39:59Z

Working great, thanks!

bcmitri · 2022-03-04T12:50:00Z

That seemed to do the trick. Now, does anyone have a similar fix for #133 (Covers no longer shows after HA update)?

swampylee · 2022-03-04T12:54:12Z

That seemed to do the trick. Now, does anyone have a similar fix for #133 (Covers no longer shows after HA update)?

I don't have that issue as I don't use Covers but why not try the fix listed in that thread which is to use a custom repository from here: https://github.com/rosskyl/banner-card/releases/tag/0.13.0 and then manually make the modifications above?

swampylee · 2022-03-04T12:55:20Z

@swampylee Many Thanks! It is alive!

All thanks should go to @mbergdal

bcmitri · 2022-03-04T12:59:19Z

That seemed to do the trick. Now, does anyone have a similar fix for #133 (Covers no longer shows after HA update)?

I don't have that issue as I don't use Covers but why not try the fix listed in that thread which is to use a custom repository from here: https://github.com/rosskyl/banner-card/releases/tag/0.13.0 and then manually make the modifications above?

I can try again, but I seem to recall that was just an earlier fork of the code which is either missing other fixes, including mapping attributes.

ahbrims · 2022-03-04T15:17:13Z

I installed HA version 2022.3 yesterday and got the same problem, but today have installed again and now it works ok chrome on my Mac without @[mbergdal] changes. It still is not working in the HA app. I do note that the ha version is 2022.3.1 today, unsure if this is a change from yesterday? Anyway, the issue seems to have gone away?

nogueirasa · 2022-03-04T22:57:17Z

Same here.

Back to version 2022.2

tchellomello · 2022-03-05T05:29:23Z

Same here but with the comment from @mbergdal (#139 (comment)) worked like a charm. Thank you!!!

Soyde · 2022-03-05T09:14:09Z

Could you help me?
I'm trying to apply solution from @mbergdal (#139 (comment)), I replaced 3 coincidences at /config/www/community/banner-card/banner-card.js.
Also deleted gz file, cleared browser cache (indeed I also installed another plugin via HACS in order to do a forced clear cache when it is requested after installing other plugin) and also restarted Homeassistant but my buttons are still missing.

Maybe I'm missing this part, but I don’t know what to do "I also commented out the CSS-part related to"

Maybe someone can pass me the whole edited js file?

Please, help!
Thanks

swampylee · 2022-03-05T10:43:13Z

Could you help me? I'm trying to apply solution from @mbergdal (#139 (comment)), I replaced 3 coincidences at /config/www/community/banner-card/banner-card.js. Also deleted gz file, cleared browser cache (indeed I also installed another plugin via HACS in order to do a forced clear cache when it is requested after installing other plugin) and also restarted Homeassistant but my buttons are still missing.

Maybe I'm missing this part, but I don’t know what to do "I also commented out the CSS-part related to"

Maybe someone can pass me the whole edited js file?

Please, help! Thanks

All I can suggest is that you go into Chrome settings and clear cache there, close browser and try again. If that doesn't work then you can try removing the CSS part you refer to which I think is this line highlighted with style.... below.

`    `}renderCustomElement(t,e,i=""){if(customElements.get(t))return this._renderCustomElement(t,e,i);console.error(t+" doesn't exist")}renderAsToggle({onClick:t,size:e,name:i,state:s,domain:n,entity:r,color:o}){return o=o||"var(--switch-checked-color)",j`
      <div class="entity-state" style="${this.grid(e)}">
        ${ot(i,t)}
        <span class="entity-value">
          <ha-switch
            **style="--mdc-theme-secondary: ${o};"**
            ?checked=${"on"===s}
            @click=${this._service(n,"toggle",r)}
          >
          </ha-switch>
        </span>
      </div>`

matteocorti · 2022-03-05T12:54:58Z

This is probably due to the update from Paper to Material Web Components that has been done in 2022.3 version. The problem seems to be related to the use of the in this code. (Ref: https://www.home-assistant.io/blog/2022/03/02/release-20223/#ui-upgrades)

My solution for now was to edit the /config/www/community/banner-card/banner-card.js and replace all instances of mwc-switch with ha-switch. (I also commented out the CSS-part related to ) Then save the file. (I did all this in the VSCode add-on)

To make the modified file to be served to Lovelace, you then will have to delete the .gz-file in the same folder (as it is served first if it is present). Then clear the browser cache (not only Ctrl+F5), but clear cached files. (Ref: https://hacs.xyz/docs/categories/plugins#special-notes-about-downloaded-lovelace-plugins)

Then refresh the Lovelace frontend and your switches should be present again.

It works like a charm. No need to comment out the CSS part.

Neu-Bob · 2022-03-05T13:30:36Z

https://hacs.xyz/docs/categories/plugins#special-notes-about-downloaded-lovelace-plugins

I'm having issues clearing the cache... any tips for that?

l4r53n · 2022-03-05T15:11:36Z

If you are using chrome: Shift + CTRL + DEL

moelloman · 2022-03-05T18:41:01Z

Hi, the workaround from @mbergdal in comment #139 works on the computer but not on the mobile phone. I use iOS Safari and the light switches are not shown. Any idea how to fix? Will be available an update of the frontend soon?

mbergdal · 2022-03-05T18:50:00Z

Hi, the workaround from @mbergdal in comment #139 works on the computer but not on the mobile phone. I use iOS Safari and the light switches are not shown. Any idea how to fix? Will be available an update of the frontend soon?

Works on my phone iPhone and iPad. Could this be a caching problem? Not sure how to force a cache update in iOS...

matteocorti · 2022-03-05T19:01:04Z

Hi, the workaround from @mbergdal in comment #139 works on the computer but not on the mobile phone. I use iOS Safari and the light switches are not shown. Any idea how to fix? Will be available an update of the frontend soon?

Works on my phone iPhone and iPad. Could this be a caching problem? Not sure how to force a cache update in iOS...

Device Settings (I don't have the English version) and then debug. You should have an option to clear the caches.

moelloman · 2022-03-06T10:16:04Z

Thanks @mbergdal and @matteocorti .
It works in the browser but what I ment originally (sorry for my missleading post) is the mobile App. Any proposal to fix it there?

matteocorti · 2022-03-06T10:17:19Z

Thanks @mbergdal and @matteocorti .

It works in the browser but what I ment originally (sorry for my missleading post) is the mobile App. Any proposal to fix it there?

Device Settings (I don't have the English version) and then debug. You should have an option to clear the caches.

moelloman · 2022-03-06T11:03:36Z

Thanks @mbergdal and @matteocorti .
It works in the browser but what I ment originally (sorry for my missleading post) is the mobile App. Any proposal to fix it there?

Device Settings (I don't have the English version) and then debug. You should have an option to clear the caches.

Found it, It's in App Settings- Debug - Clear local app cache. Thanks 👍

crempp · 2022-03-06T19:47:30Z

It appears upkeep on this plugin has slowed down or stopped. I use this card very extensively in my setup so it's important for me to keep it working. For that reason I have forked the repo and I have been merging in PRs submitted to @nervetattoo to fix many of the issues encountered over the past few months. I don't intend to take over development of this card but I realized that many issues are quickly fixed with PRs submitted only to sit unmerged. I figured it would be easy to just fork and pull the PRs over and publish releases.

If you would like to use my fork please feel free but keep in mind I don't guarantee anything. I will probably fix any catastrophic errors I will merge in bug fix PRs from the parent repo. I really hope @nervetattoo has time to get back to this because I love this card.

Remove the old Banner Card from HACS
Go to HACS, select "Frontend" and then click the three dots in the upper right and select "Custom Repositories"
Enter Repository: https://github.com/crempp/banner-card and Category: Lovelace
Click add

After the custom repository is added you'll see a new card available on the HACS Frontend page. Click "Download". You'll have to reload the frontend but you shouldn't have to change any usages of the card. It should just work.

I hope this helps.

bcmitri · 2022-03-06T20:21:14Z

It appears upkeep on this plugin has slowed down or stopped. I use this card very extensively in my setup so it's important for me to keep it working. For that reason I have forked the repo and I have been merging in PRs submitted to @nervetattoo to fix many of the issues encountered over the past few months. I don't intend to take over development of this card but I realized that many issues are quickly fixed with PRs submitted only to sit unmerged. I figured it would be easy to just fork and pull the PRs over and publish releases.

If you would like to use my fork please feel free but keep in mind I don't guarantee anything. I will probably fix any catastrophic errors I will merge in bug fix PRs from the parent repo. I really hope @nervetattoo has time to get back to this because I love this card.

Remove the old Banner Card from HACS

Go to HACS, select "Frontend" and then click the three dots in the upper right and select "Custom Repositories"

Enter Repository: https://github.com/crempp/banner-card and Category: Lovelace

Click add

After the custom repository is added you'll see a new card available on the HACS Frontend page. Click "Download". You'll have to reload the frontend but you shouldn't have to change any usages of the card. It should just work.

I hope this helps.

Doing the Lord's work. Unfortunately, you seem to be missing some fixes that were added in the following releases:

Any chances of getting those pulled in?

crempp · 2022-03-06T20:50:09Z

@bcmitri Thanks!

I didn't look at changes in the beta branch because I was uncertain how much had changed and what level of effort would be required to merge them in. I took a quick look and it doesn't look too crazy. I'll try it out later when I get some time.

crempp · 2022-03-06T22:38:35Z

@bcmitri, I cherry picked the three major fixes from those beta releases. Most of the changes in beta are for Github automations, switching the test runner and looks like an attempt to move to typescript. I'm not going to mess with that.

I didn't merge in anything from beta.1 since the only meaningful fix was Support row_size: auto which was already included in the master branch. I merged in the fixes in beta.2 and beta.3 for

Exclamation mark icon over images, fixes Exclamation mark over pictures since 0.117.x #95
map_attributes, fixes Map attributes #113

There's a new release (0.13.3) you should be able to update to in HACS. I tested that the card still functions but I don't use those features so I didn't test the features themselves.

Enjoy!

bcmitri · 2022-03-06T22:50:19Z

@crempp Those were the ones! And, at a glance, it seems like everything is working properly. Thanks so much!

bucky2076 · 2022-03-07T05:46:50Z

working now for me too... can't thank you enough....

psleutel · 2022-03-07T07:51:42Z

@bcmitri Thanks so much!

Works as designed again

swampylee · 2022-03-07T08:50:12Z

@crempp Thanks very much - all working great!

maiconguelere · 2022-03-07T19:17:19Z

I have another workaround
I just added "domain: sensor", an icon and an action to every "toggle" that dissapeared

It was like this:

  - entity: switch.light_1
    name: Light 1
    color: black
    map_state:
      'on':
        color: yellow

And now it is like this

  - entity: switch.light_1
    name: Light 1
    domain: sensor
    action:
      service: switch.toggle
    value: mdi:lightbulb
    color: black
    map_state:
      'on':
        color: yellow

wehrstedt · 2022-03-07T21:58:32Z

That seemed to do the trick. Now, does anyone have a similar fix for #133 (Covers no longer shows after HA update)?

wehrstedt@f4e634e

crempp · 2022-03-08T05:38:49Z

@wehrstedt I included your fix (thank you for that) in my forked release so you or others can point HACS at the forked repo.

wehrstedt · 2022-03-08T17:12:09Z

@wehrstedt I included your fix (thank you for that) in my forked release so you or others can point HACS at the forked repo.

Thanks, but im currently maintain my own fork (once it stops working due to HA updates) because I'm still waiting that #114 will be merged someday ... Are you actively maintain your fork?

clwolf75 · 2022-03-08T21:46:39Z

Now I'm confused at which fork to get! lol. But this worked great. And I prefer the icons versus the toggles.

I have another workaround I just added "domain: sensor", an icon and an action to every "toggle" that dissapeared

It was like this:
  - entity: switch.light_1
    name: Light 1
    color: black
    map_state:
      'on':
        color: yellow
And now it is like this
  - entity: switch.light_1
    name: Light 1
    domain: sensor
    action:
      service: switch.toggle
    value: mdi:lightbulb
    color: black
    map_state:
      'on':
        color: yellow

wehrstedt · 2022-03-08T21:59:21Z

I do not recommend to use mine. I only update my fork if something does not work in my setup. But it is also not useful to maintain different forks. Thats why i asked. I dont think that this project will be maintained anymore.

clwolf75 · 2022-03-08T22:01:50Z

That's unfortunate. I just created my dashboard about a week ago. I was going to use area cards, but they are very limited, so I found this card.

nogueirasa · 2022-03-08T22:03:36Z

It appears upkeep on this plugin has slowed down or stopped. I use this card very extensively in my setup so it's important for me to keep it working. For that reason I have forked the repo and I have been merging in PRs submitted to @nervetattoo to fix many of the issues encountered over the past few months. I don't intend to take over development of this card but I realized that many issues are quickly fixed with PRs submitted only to sit unmerged. I figured it would be easy to just fork and pull the PRs over and publish releases.

If you would like to use my fork please feel free but keep in mind I don't guarantee anything. I will probably fix any catastrophic errors I will merge in bug fix PRs from the parent repo. I really hope @nervetattoo has time to get back to this because I love this card.

Remove the old Banner Card from HACS

Go to HACS, select "Frontend" and then click the three dots in the upper right and select "Custom Repositories"

Enter Repository: https://github.com/crempp/banner-card and Category: Lovelace

Click add

After the custom repository is added you'll see a new card available on the HACS Frontend page. Click "Download". You'll have to reload the frontend but you shouldn't have to change any usages of the card. It should just work.

I hope this helps.

Thanks @crempp , back to home assistant updated

crempp · 2022-03-10T22:51:16Z

@wehrstedt I included your fix (thank you for that) in my forked release so you or others can point HACS at the forked repo.

Thanks, but im currently maintain my own fork (once it stops working due to HA updates) because I'm still waiting that #114 will be merged someday ... Are you actively maintain your fork?

@wehrstedt let's say I'm actively pulling in fixes submitted to this repo and other forks and I'm preparing releases in a way that HA can accept. As issues arise I'm watching this repo and other forks and I just pull the PRs into mine and create a release. At least that's my plan. If you have more fixes in the future please tag me and I'll pull them into my fork. So, in summary, I'm going to try to keep up but I really don't want to take over development of this project.

tomod3606 · 2022-03-12T10:29:11Z

This is probably due to the update from Paper to Material Web Components that has been done in 2022.3 version. The problem seems to be related to the use of the in this code. (Ref: https://www.home-assistant.io/blog/2022/03/02/release-20223/#ui-upgrades)

My solution for now was to edit the /config/www/community/banner-card/banner-card.js and replace all instances of mwc-switch with ha-switch. (I also commented out the CSS-part related to ) Then save the file. (I did all this in the VSCode add-on)

To make the modified file to be served to Lovelace, you then will have to delete the .gz-file in the same folder (as it is served first if it is present). Then clear the browser cache (not only Ctrl+F5), but clear cached files. (Ref: https://hacs.xyz/docs/categories/plugins#special-notes-about-downloaded-lovelace-plugins)

Then refresh the Lovelace frontend and your switches should be present again.

I've followed this and it worked well for all the switches, however the media player controls still don't show up. Is there a fix for this section anywhere?

jak119 · 2022-04-16T02:40:31Z

I didn't like the idea of manually editing the .js file so while #140 is pending acceptance I went ahead and created a fork which integrated those changes. If you wish you can add the repo as a manual repo, uninstall "Lovelace banner card" and install "Lovelace banner card fork"

lovedreamland · 2022-05-01T18:13:38Z

I didn't like the idea of manually editing the .js file so while #140 is pending acceptance I went ahead and created a fork which integrated those changes. If you wish you can add the repo as a manual repo, uninstall "Lovelace banner card" and install "Lovelace banner card fork"

Hello, this version I use the switch is normal, but the curtain still cannot be displayed

smacks0048 · 2024-01-06T21:36:34Z

That seemed to do the trick. Now, does anyone have a similar fix for #133 (Covers no longer shows after HA update)?

I don't have that issue as I don't use Covers but why not try the fix listed in that thread which is to use a custom repository from here: https://github.com/rosskyl/banner-card/releases/tag/0.13.0 and then manually make the modifications above?

I can try again, but I seem to recall that was just an earlier fork of the code which is either missing other fixes, including mapping attributes.

Hi all, I managed do fix the issue with the switches - thank you for the hints.

Did anyone fix the issue with the covers? I am still struggling with that one.

matteocorti added a commit to matteocorti/banner-card that referenced this issue Mar 5, 2022

Fixes nervetattoo#139

e62a4f2

richardsim7 mentioned this issue Mar 8, 2022

switch entities no longer default to toggle switches home-assistant/core#67620

Closed

nervetattoo closed this as completed in 554c77c Jun 1, 2022

bigramonk mentioned this issue Feb 10, 2023

Switch doesnt show up? #155

Open

buttons dissapered after latest HA update 2022.3 #139

buttons dissapered after latest HA update 2022.3 #139

Comments

bucky2076 commented Mar 3, 2022

RamiRihawi commented Mar 3, 2022 • edited Loading

bucky2076 commented Mar 3, 2022

bucky2076 commented Mar 3, 2022

ajghor commented Mar 3, 2022

psleutel commented Mar 3, 2022

swampylee commented Mar 3, 2022

swampylee commented Mar 3, 2022 • edited Loading

matteocorti commented Mar 3, 2022

l4r53n commented Mar 3, 2022

mbergdal commented Mar 4, 2022 • edited Loading

Spookster commented Mar 4, 2022

mbergdal commented Mar 4, 2022

swampylee commented Mar 4, 2022

ajghor commented Mar 4, 2022

l4r53n commented Mar 4, 2022

bcmitri commented Mar 4, 2022

swampylee commented Mar 4, 2022

swampylee commented Mar 4, 2022

bcmitri commented Mar 4, 2022 • edited Loading

ahbrims commented Mar 4, 2022 • edited Loading

nogueirasa commented Mar 4, 2022

tchellomello commented Mar 5, 2022 • edited Loading

Soyde commented Mar 5, 2022 • edited Loading

swampylee commented Mar 5, 2022

matteocorti commented Mar 5, 2022

Neu-Bob commented Mar 5, 2022

l4r53n commented Mar 5, 2022

moelloman commented Mar 5, 2022 • edited Loading

mbergdal commented Mar 5, 2022

matteocorti commented Mar 5, 2022

moelloman commented Mar 6, 2022

matteocorti commented Mar 6, 2022

moelloman commented Mar 6, 2022

crempp commented Mar 6, 2022

bcmitri commented Mar 6, 2022

crempp commented Mar 6, 2022

crempp commented Mar 6, 2022

bcmitri commented Mar 6, 2022

bucky2076 commented Mar 7, 2022

psleutel commented Mar 7, 2022

swampylee commented Mar 7, 2022

maiconguelere commented Mar 7, 2022

wehrstedt commented Mar 7, 2022

crempp commented Mar 8, 2022

wehrstedt commented Mar 8, 2022 • edited Loading

clwolf75 commented Mar 8, 2022

wehrstedt commented Mar 8, 2022

clwolf75 commented Mar 8, 2022

nogueirasa commented Mar 8, 2022

crempp commented Mar 10, 2022

tomod3606 commented Mar 12, 2022

jak119 commented Apr 16, 2022

lovedreamland commented May 1, 2022

smacks0048 commented Jan 6, 2024

RamiRihawi commented Mar 3, 2022 •

edited

Loading

swampylee commented Mar 3, 2022 •

edited

Loading

mbergdal commented Mar 4, 2022 •

edited

Loading

bcmitri commented Mar 4, 2022 •

edited

Loading

ahbrims commented Mar 4, 2022 •

edited

Loading

tchellomello commented Mar 5, 2022 •

edited

Loading

Soyde commented Mar 5, 2022 •

edited

Loading

moelloman commented Mar 5, 2022 •

edited

Loading

wehrstedt commented Mar 8, 2022 •

edited

Loading