Pop-Up no longer works with Home Assistant 2024.7.x

[KyleStilkey]

My Home Assistant version: 2024.7.1

Seems like with this new release Browser Mod's Pop-Up no longer works. It will show a pop-up once then it will no longer work and display the default more info.

• X Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).

• X Have made sure I am using the latest version of the plugin.

• X Have followed the troubleshooting steps of the "Common Problems" section of https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins.

• X Understand that leaving one or more boxes unticked or failure to follow the template above may increase the time required to handle my bug-report, or cause it to be closed without further action.

[MasterDevwi]

I'm hitting this too. Clicking on an entity linked to a pop-up card no longer shows the pop-up card and instead takes me directly to the entity's more-info page. Initially it was broken on iOS but working on my desktop browser, but after restarting HA I can't get it to work anywhere.

Also, as of 2024.6 the dashboard also doesn't show a preview of the card anymore unless I click Edit to open the pop-up card configuration UI.

[mallewski]

Thanks for all your work and this gorgeous feature to HA. I'm loving IT. Unfortunately same issue here.

Core 2024.7.0 Supervisor 2024.06.2 Operating System 12.4 Frontend 20240703.0

[igiannakas]

Same here unfortunately :( Pop up doesnt work and the entities are shown as the screenshot above with the latest HA version.

[benjycov]

+1 for this.

[fspaggia]

Same behaviour for me. Stopped working after i reloaded cache (new frontend available).

[djjoereece94]

Same here :(

[benjycov]

So it looks like the browser_mod.popup method is still working, just the more-info approach is broken?

[Flintr]

+1

[benjycov]

For anyone else in the same situation, I've just knuckled down and redone all of mine using:

tap_action:
  action: call-service
  service: browser_mod.popup
  service_data: 
    title: Media
    content:
       type:..

and:

  tap_action:
    action: fire-dom-event
    browser_mod:
      service: browser_mod.popup
      data:
        title: {{ room_name(room, country) }}
        content:
           type:...

I've been meaning to do this for ages, and it does seem a better way and more importantly it still works!

[Tobi-Wheeler]

Me Too!

[KJThaDon]

For anyone else in the same situation, I've just knuckled down and redone all of mine using:

tap_action:
  action: call-service
  service: browser_mod.popup
  service_data: 
    title: Media
    content:
       type:..

and:

  tap_action:
    action: fire-dom-event
    browser_mod:
      service: browser_mod.popup
      data:
        title: {{ room_name(room, country) }}
        content:
           type:...

I've been meaning to do this for ages, and it does seem a better way and more importantly it still works!

Can you show an example of how you're integrating it this way please?

I'm trying to switch it to a card like this for example

        tap_action:
          action: call-service
          service: browser_mod.popup
          service_data: 
            title: Media
            content:
                type: custom:popup-card
                dismissable: true
                card:
                  type: custom:teamtracker-card
                  entity: sensor.wolverines_tracker
                  show_timeouts: true
                  show_rank: true
                entity: calendar.michigan_wolverines

[benjycov]

You are nearly there, you can remove:

   type: custom:popup-card
            dismissable: true
            card:

So with the content start immediately with:

type: custom:teamtracker-card

I hope that helps.

On Fri, 5 Jul 2024 at 07:25, KJThaDon @.***> wrote:

For anyone else in the same situation, I've just knuckled down and redone all of mine using:

tap_action: action: call-service service: browser_mod.popup service_data: title: Media content: type:..

and:

tap_action: action: fire-dom-event browser_mod: service: browser_mod.popup data: title: {{ room_name(room, country) }} content: type:...

I've been meaning to do this for ages, and it does seem a better way and more importantly it still works!

Can you show an example of how you're integrating it this way please?

I'm trying to switch it to a card like this for example

    tap_action:
      action: call-service
      service: browser_mod.popup
      service_data:
        title: Media
        content:
            type: custom:popup-card
            dismissable: true
            card:
              type: custom:teamtracker-card
              entity: sensor.wolverines_tracker
              show_timeouts: true
              show_rank: true
            entity: calendar.michigan_wolverines

— Reply to this email directly, view it on GitHub https://github.com/thomasloven/hass-browser_mod/issues/715#issuecomment-2210259145, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZVQ2F2DLDIBMG5KUIQTEDZKY34PAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGI2TSMJUGU . You are receiving this because you commented.Message ID: @.***>

[KJThaDon]

You are nearly there, you can remove: type: custom:popup-card dismissable: true card: So with the content start immediately with: type: custom:teamtracker-card I hope that helps. … On Fri, 5 Jul 2024 at 07:25, KJThaDon @.> wrote: For anyone else in the same situation, I've just knuckled down and redone all of mine using: tap_action: action: call-service service: browser_mod.popup service_data: title: Media content: type:.. and: tap_action: action: fire-dom-event browser_mod: service: browser_mod.popup data: title: {{ room_name(room, country) }} content: type:... I've been meaning to do this for ages, and it does seem a better way and more importantly it still works! Can you show an example of how you're integrating it this way please? I'm trying to switch it to a card like this for example tap_action: action: call-service service: browser_mod.popup service_data: title: Media content: type: custom:popup-card dismissable: true card: type: custom:teamtracker-card entity: sensor.wolverines_tracker show_timeouts: true show_rank: true entity: calendar.michigan_wolverines — Reply to this email directly, view it on GitHub <#715 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZVQ2F2DLDIBMG5KUIQTEDZKY34PAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGI2TSMJUGU . You are receiving this because you commented.Message ID: @.>

Thank you! I got it to work again for that card.

How could this work with pop up cards that are hidden and pop up using the more-info dialog?

[benjycov]

Ah you mean replacing normal more-info when you just look at the entity directly?

I don’t think you can work around that :(

I have to say though sometimes I found that annoying with the more-info approach, go to look at the entity and get my custom popup!

On Fri, 5 Jul 2024 at 09:02, KJThaDon @.***> wrote:

You are nearly there, you can remove: type: custom:popup-card dismissable: true card: So with the content start immediately with: type: custom:teamtracker-card I hope that helps. … <#m_8095103277203468504_> On Fri, 5 Jul 2024 at 07:25, KJThaDon @.> wrote: For anyone else in the same situation, I've just knuckled down and redone all of mine using: tap_action: action: call-service service: browser_mod.popup service_data: title: Media content: type:.. and: tap_action: action: fire-dom-event browser_mod: service: browser_mod.popup data: title: {{ room_name(room, country) }} content: type:... I've been meaning to do this for ages, and it does seem a better way and more importantly it still works! Can you show an example of how you're integrating it this way please? I'm trying to switch it to a card like this for example tap_action: action: call-service service: browser_mod.popup service_data: title: Media content: type: custom:popup-card dismissable: true card: type: custom:teamtracker-card entity: sensor.wolverines_tracker show_timeouts: true show_rank: true entity: calendar.michigan_wolverines — Reply to this email directly, view it on GitHub <#715 (comment) https://github.com/thomasloven/hass-browser_mod/issues/715#issuecomment-2210259145>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZVQ2F2DLDIBMG5KUIQTEDZKY34PAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGI2TSMJUGU https://github.com/notifications/unsubscribe-auth/AQZVQ2F2DLDIBMG5KUIQTEDZKY34PAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGI2TSMJUGU . You are receiving this because you commented.Message ID: @.>

Thank you! I got it to work again for that card.

How could this work with pop up cards that are hidden and pop up using the more-info dialog?

— Reply to this email directly, view it on GitHub https://github.com/thomasloven/hass-browser_mod/issues/715#issuecomment-2210394234, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZVQ2ERIPNDCWBI4VGUBCLZKZHJXAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGM4TIMRTGQ . You are receiving this because you commented.Message ID: @.***>

[Soukyuu]

Well, for me that doesn't work for whatever reason. I tried it in dev tools/call service and the call executes correctly, but no popup is shown. Same for the actual widget. The service also seems to have a problem with mushroom's custom template card, specifically with the entity: your.entity_here part. It complains that entity is unknown.

[KJThaDon]

Ah you mean replacing normal more-info when you just look at the entity directly? I don’t think you can work around that :( I have to say though sometimes I found that annoying with the more-info approach, go to look at the entity and get my custom popup! … On Fri, 5 Jul 2024 at 09:02, KJThaDon @.> wrote: You are nearly there, you can remove: type: custom:popup-card dismissable: true card: So with the content start immediately with: type: custom:teamtracker-card I hope that helps. … <#m_8095103277203468504_> On Fri, 5 Jul 2024 at 07:25, KJThaDon @.> wrote: For anyone else in the same situation, I've just knuckled down and redone all of mine using: tap_action: action: call-service service: browser_mod.popup service_data: title: Media content: type:.. and: tap_action: action: fire-dom-event browser_mod: service: browser_mod.popup data: title: {{ room_name(room, country) }} content: type:... I've been meaning to do this for ages, and it does seem a better way and more importantly it still works! Can you show an example of how you're integrating it this way please? I'm trying to switch it to a card like this for example tap_action: action: call-service service: browser_mod.popup service_data: title: Media content: type: custom:popup-card dismissable: true card: type: custom:teamtracker-card entity: sensor.wolverines_tracker show_timeouts: true show_rank: true entity: calendar.michigan_wolverines — Reply to this email directly, view it on GitHub <#715 (comment) <#715 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZVQ2F2DLDIBMG5KUIQTEDZKY34PAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGI2TSMJUGU https://github.com/notifications/unsubscribe-auth/AQZVQ2F2DLDIBMG5KUIQTEDZKY34PAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGI2TSMJUGU . You are receiving this because you commented.Message ID: @.> Thank you! I got it to work again for that card. How could this work with pop up cards that are hidden and pop up using the more-info dialog? — Reply to this email directly, view it on GitHub <#715 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZVQ2ERIPNDCWBI4VGUBCLZKZHJXAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGM4TIMRTGQ . You are receiving this because you commented.Message ID: @.**>

yes, replacing the pop up of more info. It was working fine forever until now. I have custom cards I made for my TV remotes, and you would click on the entity icon using the more info action and it would open up my custom popup-cards. Not sure what broke with it recently, but I had nearly 10 cards just showing like this, when they used to work.

I did manage to copy the

[Soukyuu]

@KJThaDon: You could try replacing the more_info with the service call, I think that's what @benjycov did. But it does not work for me.

[KJThaDon]

Well, for me that doesn't work for whatever reason. I tried it in dev tools/call service and the call executes correctly, but no popup is shown. Same for the actual widget. The service also seems to have a problem with mushroom's custom template card, specifically with the entity: your.entity_here part. It complains that entity is unknown.

This is how I ended getting one of mine to work with @benjycov help.

        tap_action:
          action: call-service
          service: browser_mod.popup
          service_data:
            content:
              type: custom:teamtracker-card
              entity: sensor.wolverines_tracker

This works fine if you are trying to get a popup of a custom card other than popup-card it seems...

[benjycov]

What browser are you using? I found Ooera to be completely non helpful, couldn’t make them work at all.

Chrome is fine and IOS safari/HA app.

On Fri, 5 Jul 2024 at 09:19, Ivan Pilipenko @.***> wrote:

Well, for me that doesn't work for whatever reason. I tried it in dev tools/call service and the call executes correctly, but no popup is shown. Same for the actual widget. The service also seems to have a problem with mushroom's custom template card, specifically with the entity: your.entity_here part. It complains that entity is unknown.

— Reply to this email directly, view it on GitHub https://github.com/thomasloven/hass-browser_mod/issues/715#issuecomment-2210420916, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZVQ2AYCZXXLYU2IRTJAGTZKZJKRAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGQZDAOJRGY . You are receiving this because you commented.Message ID: @.***>

[benjycov]

Also which method are you using - call-service or fire-dom?

I find call-service is more reliable, but has the downside of opening popups on all browsers.

On Fri, 5 Jul 2024 at 09:25, Ben King @.***> wrote:

What browser are you using? I found Ooera to be completely non helpful, couldn’t make them work at all.

Chrome is fine and IOS safari/HA app.

On Fri, 5 Jul 2024 at 09:19, Ivan Pilipenko @.***> wrote:

Well, for me that doesn't work for whatever reason. I tried it in dev tools/call service and the call executes correctly, but no popup is shown. Same for the actual widget. The service also seems to have a problem with mushroom's custom template card, specifically with the entity: your.entity_here part. It complains that entity is unknown.

— Reply to this email directly, view it on GitHub https://github.com/thomasloven/hass-browser_mod/issues/715#issuecomment-2210420916, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZVQ2AYCZXXLYU2IRTJAGTZKZJKRAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGQZDAOJRGY . You are receiving this because you commented.Message ID: @.***>

[Soukyuu]

This is what I have and it's not working - no popup.

tap_action:
  action: call-service
  service: browser_mod.popup
  data:
    content:
      type: custom:mushroom-template-card
      primary: >-
        UV Index {% if(is_state('sensor.current_uv_index', 'unavailable')) %}
        N/A {% else %} {{ states('sensor.current_uv_index') | round(1) ~' / ' ~
        states('sensor.max_uv_index') | round(1)}} {% endif %} 
      secondary: >-
        {% if is_state('sensor.current_uv_index', 'unavailable') or
        states('sensor.current_uv_index') | float() < 3.5 %}

        Kein Sonnenschutz erforderlich

        {% else %}

        {{ 'Kind darf ohne Schutz für ' ~
        states('sensor.skin_type_1_safe_exposure_time') ~ 'min in die
        Sonne\nFrau darf ohne Schutz für ' ~
        states('sensor.skin_type_2_safe_exposure_time') ~ 'min in die
        Sonne\nIch darf ohne Schutz für ' ~
        states('sensor.skin_type_3_safe_exposure_time') ~ 'min in die Sonne'}}

        {% endif %}
      icon: mdi:sun-wireless
      fill_container: false
      icon_color: >-
        {% if(is_state('sensor.current_uv_index', 'unavailable') or
        states('sensor.current_uv_index') | float() < 3.5) %}

        green

        {% elif(states('sensor.current_uv_index') | float() < 5.0) %}

        yellow

        {% elif(states('sensor.current_uv_index') | float() < 6.5) %}

        amber

        {% elif(states('sensor.current_uv_index') | float() < 8) %}

        orange

        {% else %}

        red

        {% endif %}
      tap_action:
        action: none
      hold_action:
        action: none
      double_tap_action:
        action: none
      layout: vertical
      multiline_secondary: true
  target: {}

I can't even get a simple

tap_action:
  action: call-service
  service: browser_mod.popup
  target: {}
  data:
    dismissable: true
    autoclose: false
    content:
      type: entity
      entity: sensor.date

to pop up. Neither in vivaldi browser (chrome based) nor in the app.

[benjycov]

Have you flushed your browser fully?

On Fri, 5 Jul 2024 at 09:38, Ivan Pilipenko @.***> wrote:

This is what I have and it's not working - no popup.

tap_action: action: call-service service: browser_mod.popup data: content: type: custom:mushroom-template-card primary: >- UV Index {% if(is_state('sensor.current_uv_index', 'unavailable')) %} N/A {% else %} {{ states('sensor.current_uv_index') | round(1) ~' / ' ~ states('sensor.max_uv_index') | round(1)}} {% endif %} secondary: >- {% if is_state('sensor.current_uv_index', 'unavailable') or states('sensor.current_uv_index') | float() < 3.5 %}

    Kein Sonnenschutz erforderlich

    {% else %}

    {{ 'Kind darf ohne Schutz für ' ~
    states('sensor.skin_type_1_safe_exposure_time') ~ 'min in die
    Sonne\nFrau darf ohne Schutz für ' ~
    states('sensor.skin_type_2_safe_exposure_time') ~ 'min in die
    Sonne\nIch darf ohne Schutz für ' ~
    states('sensor.skin_type_3_safe_exposure_time') ~ 'min in die Sonne'}}

    {% endif %}
  icon: mdi:sun-wireless
  fill_container: false
  icon_color: >-
    {% if(is_state('sensor.current_uv_index', 'unavailable') or
    states('sensor.current_uv_index') | float() < 3.5) %}

    green

    {% elif(states('sensor.current_uv_index') | float() < 5.0) %}

    yellow

    {% elif(states('sensor.current_uv_index') | float() < 6.5) %}

    amber

    {% elif(states('sensor.current_uv_index') | float() < 8) %}

    orange

    {% else %}

    red

    {% endif %}
  tap_action:
    action: none
  hold_action:
    action: none
  double_tap_action:
    action: none
  layout: vertical
  multiline_secondary: true

target: {}

I can't even get a simple

tap_action: action: call-service service: browser_mod.popup target: {} data: dismissable: true autoclose: false content: type: entity entity: sensor.date

to pop up. Neither in vivaldi browser (chrome based) nor in the app.

— Reply to this email directly, view it on GitHub https://github.com/thomasloven/hass-browser_mod/issues/715#issuecomment-2210450423, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZVQ2COTHCNVFCY7IRHKCLZKZLRVAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGQ2TANBSGM . You are receiving this because you were mentioned.Message ID: @.***>

[Soukyuu]

Yes. On the app there was even a request to reload because the dashboard has changed

[Soukyuu]

Apparently you have to register the browser in browser_mod. That makes it work. But that also means your UI only works as expected on known devices, and the popup opens on ALL known devices simultaneously, which is not really a good thing.

[Soukyuu]

I just tried to use action: fire-dom-event and the editor goes bonkers complaining that it only supports the following:

"none","toggle","more-info","call-service","url","navigate","assist"

Which might be the root cause of the problems.

[tigers75]

I can't even get a simple

tap_action:
  action: call-service
  service: browser_mod.popup
  target: {}
  data:
    dismissable: true
    autoclose: false
    content:
      type: entity
      entity: sensor.date

to pop up. Neither in vivaldi browser (chrome based) nor in the app.

I think you must change something: not "data" but "service_data"

and then start directly with the "content:" section. This works for me:

tap_action:
      action: call-service
      service: browser_mod.popup
      service_data:
        content:
          type: vertical-stack
          cards:
            - type: custom:mushroom-cover-card
              entity: cover.tapparelle_notte
              show_position_control: true
              secondary_info: none
        [...]

Anyway this solution is worse in my opinion because now I have a card inside another card, and I'm loosing the editor (I use the pop-up mainly in a pciture-elements card) and the yaml of the card becomes a mess.

[Soukyuu]

I think you must change something: not "data" but "service_data"

Thanks, that does not change anything for me. I still have to be registered with browser mod and then it still opens the popup on all active registered browser. So for example me pressing on my app will open the popup on my laptop and my wife's app.

The docs do state you should use the fire-dom-event to only open the popup on your screen, even if the browser is not registered, but for some reason my instance of home assistant insists it's not supported.

[Lucif3r945]

I think you must change something: not "data" but "service_data"

Thanks, that does not change anything for me. I still have to be registered with browser mod and then it still opens the popup on all active registered browser. So for example me pressing on my app will open the popup on my laptop and my wife's app.

The docs do state you should use the fire-dom-event to only open the popup on your screen, even if the browser is not registered, but for some reason my instance of home assistant insists it's not supported.

Hey, I struggled with the same thing for quite a while. What you (I have to at least) do is leaving action: as-is(e.g. call-service), type out all code as if it were set to fire-dom-event, THEN when the code is complete, you change action: to fire-dom-event, and hit save. If you start with typing out action: fire-dom-event, without the browser_mod: section filled out already, it will sh*t itself and refuse to work. Why? idk...

[AndiFidi]

The solution shown above doesn't work for me. Is there perhaps a need for an update from Thomas Loven?

[tigers75]

The fire-dom solution works fine for me. Please read carefully the instructions since the setup is slightly different data Vs service_data, different indentation, etc