Pop-Up no longer works with Home Assistant 2024.7.x #715
Comments
|
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. |
|
Thanks for all your work and this gorgeous feature to HA. I'm loving IT. Core |
|
Same here unfortunately :( Pop up doesnt work and the entities are shown as the screenshot above with the latest HA version. |
|
+1 for this. |
|
Same behaviour for me. |
|
Same here :( |
|
So it looks like the browser_mod.popup method is still working, just the more-info approach is broken? |
|
+1 |
|
For anyone else in the same situation, I've just knuckled down and redone all of mine using: and: I've been meaning to do this for ages, and it does seem a better way and more importantly it still works! |
|
Me Too! |
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 |
|
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? |
|
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:
***@***.***>
|
|
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 |
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 |
This is how I ended getting one of mine to work with @benjycov help. This works fine if you are trying to get a popup of a custom card other than popup-card it seems... |
|
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
<#715 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQZVQ2AYCZXXLYU2IRTJAGTZKZJKRAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGQZDAOJRGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
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
> <#715 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AQZVQ2AYCZXXLYU2IRTJAGTZKZJKRAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGQZDAOJRGY>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
|
This is what I have and it's not working - no popup. I can't even get a simple to pop up. Neither in vivaldi browser (chrome based) nor in the app. |
|
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
<#715 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQZVQ2COTHCNVFCY7IRHKCLZKZLRVAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGQ2TANBSGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Yes. On the app there was even a request to reload because the dashboard has changed |
|
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. |
|
I just tried to use Which might be the root cause of the problems. |
I think you must change something: and then start directly with the "content:" section. 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. |
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 |
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. |
|
The solution shown above doesn't work for me. Is there perhaps a need for an update from Thomas Loven? |
|
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 |
|
You are right, it does trigger all browsers to open it. |
|
I had solved the pop-ups in the more-info variant from a custom:minimalistic-area-card and this is exactly what suddenly doesn't work anymore. Is there a solution or another mod for this? Unfortunately, Thomas Loven doesn't seem to have provided an update here for months. |
I've been looking into |
I tried bubble card but it requires you to set up the popups and buttons in certain orders and by doing so breaks my other add on layout cards. Sadly it breaks it and forces everything into a center 1 tile layout. Once the new home layout is more mature I'll probably be able to move over to it but it's still got some weird problems they are working on sorting. |
|
Me as well, but it doesn't support templates and that's what I mostly use. Not switching to JS for templating...
05.07.2024 22:28:07 KJThaDon ***@***.***>:
…
I had solved the pop-ups in the more-info variant from a custom:minimalistic-area-card and this is exactly what suddenly doesn't work anymore. Is there a solution or another mod for this? Unfortunately, Thomas Loven doesn't seem to have provided an update here for months.
I've been looking into
https://github.com/Clooos/Bubble-Card
*type: vertical-stack
cards:
- type: custom:bubble-card
card_type: pop-up
hash: '#test'
*
—
Reply to this email directly, view it on GitHub[#715 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAP7PTS3P6UX4BTFEYZNMKLZK36VFAVCNFSM6AAAAABKHWGU4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRGM3TSMZVHA].
You are receiving this because you are subscribed to this thread.
[Verfolgungsbild][https://github.com/notifications/beacon/AAP7PTTIL5UEBYFRSGIODDLZK36VFA5CNFSM6AAAAABKHWGU4KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUDZ34J4.gif]
|
|
Still no fix available? :( |
|
This is how I solved it, the call_service method made it popup on ALL my HA installs which wasn't good for me. This works only in the browser where it's clicked:
|
|
I can confirm that problem comes with Frontend 20240705.0 |
|
I think it's time to request for removal. Author is MIA and plugin hasn't had a real update in years |
This fix is working for the localze in the panel but does not fix the popupcard issue. When we talk about the popup there are 2 differents on how to call / trigger them. The one you call via service: browser_mod.popup which are working fine. But when you call a popup via custom:popup-card this part is broken. |
can you post a sample code? i dont have popups so just did a quick test... |
Because you have browser_mod installed, you have alrdy installed the popup card. In you dashboard simply create a card (search for popup). Under Settings as entity you have to select the entity which should trigger the popup. and under the Card Tab you can do the cards you want to show in the popup. here is a example: create 2 cards, one with: and the popup card self: if you click on the sensor card, it should trigger the popup card. the entity in the popup card is the trigger. |
|
Yup, it's only the custom popup-CARD that's broken. The popup-SERVICE(s) still work just fine. |
Yes, I got it to work now, but with this HUGE caveat that you can not use the graphical editor. Even after saving, if you then open the editor by clicking "edit" on the widget, it will cr*p its pants and replace the |
|
So, the most easy fix I got for this one right now, is to just add a layout-card around the pop-up cards on all places you use it. So I've the following 'old' pop-up card here: I've changed that piece of code with a surrounding layout card: For me this is the quickest fix to at least get the cards going again. Wife isn't happy about this otherwise :) |
Thank you! We appreciate the straight forward example. |
This definitely works but we still lose the ability to visual-edit the card. Still better than inserting the popup cards inside the main card code, but not perfect yet. |
For sure, this isn't a fix for this problem. Just a workaround so at least the popups are working again ;) |
|
I´ve made a fork that fixes this issue until/if we ever get an actual update. This is a combined fork of:
NOTE: Pop-up cards still show as blank in edit mode_ Steps to implement:
Done! It should work immediately. |
|
That's nice bunti find it not optimal: what if anyone starts a new fork? Is @thomasloven not willing to maintain this anymore? Can he at least pass the project to someone else? |
I tested this and it doesn't seem to work. Works for the first time then doesn't work again. |
hmm, did you remove every instance of original browser mod to begin with? I had some problem when reinstalling/testing Rays version myself but once i removed browser mod everywhere and then installed my fork and then the integration under devices & services it worked. Sounds weird that it worked the first time tho... Try refreshing front-end cache on your phone if not done already? |
Yes deleted everything, restarted, installed, restarted, set up browser mod, restarted, cleared cache, still same results. |
|
I have changed all mine to bubble pop-ups and couldn't be happier! They are easy to make and display in edit mode so you can see what you are doing!Sent from my Galaxy
-------- Original message --------From: KyleStilkey ***@***.***> Date: 31/07/24 16:57 (GMT+12:00) To: thomasloven/hass-browser_mod ***@***.***> Cc: Tobi-Wheeler ***@***.***>, Comment ***@***.***> Subject: Re: [thomasloven/hass-browser_mod] Pop-Up no longer works with Home Assistant 2024.7.x (Issue #715)
I´ve made a fork that fixes this issue until/if we ever get an actual update. https://github.com/mellamomax/hass-browser_modpop/
This is a combined fork of:
raymercury's repository with #619, which addresses pop-ups showing in fullscreen on mobile.
For the popup not working with HA 2024.7.X, @sebastian-bartkowiak had a solution with #732.
NOTE: Pop-up cards still show as blank in edit mode_
Steps to implement:
Remove the original Browser_mod in HACS by clicking "ignore".
Then delete it under "devices & services"
Restart HA
Install the fork as a custom repo within HACS
Restart HA
Add "Browser_mod" under "devices & services" as usual
EDIT: refresh cache on mobile
Done! It should work immediately.
I tested this and it doesn't seem to work. Works for the first time then doesn't work again.
hmm, did you remove every instance of original browser mod to begin with? I had some problem when reinstalling/testing Rays version myself but once i removed browser mod everywhere and then installed my fork and then the integration under devices & services it worked. Sounds weird that it worked the first time tho... Try refreshing front-end cache on your phone if not done already?
Yes deleted everything, restarted, installed, restarted, set up browser mod, restarted, cleared cache, still same results.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
|
sweet a fix has been made |
|
I don't think this can be marked as completed in this repository: it involves installing a fork, it's not been merged. Also the cards not showing in edit is still a problem. |
Agree, this isn't closed here. There are workarounds though. |
|
This is merged I guess my response didn't post. If you are having trouble with it working on mobile like I did through the app I had to actually go into my phone and delete the cache and data and sync back up with my home assistant for it to work. I have no idea why even though I was clearing the cache from the app it just wouldn't work and clearing the apps cache and data under setting or reinstalling fixed it for me. Give this a shot and see what happens. On other devices clearing your cache and cookies will resolve it through the browser. I've tested this across multiple devices and this has worked for me on 5 different mobile devices and 8 different computers through a browser. |
and others
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.
The text was updated successfully, but these errors were encountered: