If it still works with the latest version, then your browser cache is not cleared.
@thomasloven no difference, I tried a complete new browser (firefox), deleted the frontend cache in Home Assistant App on iOS and delete the safari cache on all devices. Popup still not opens on local device for this devices (iPad, Macbook with safari, chrome, firefox) Before the update all this worked, so config is still the same.
Hey! Iām using the script below to display a clock screensaver on an iPad/s. When I tap the screen (clock) it displays a more info dialog for the sensor. Is there any way to remove this tap action or change it to: command: close-popup
Iāve tried to use auto_close: true which does work but it also taps the underlying cards meaning that āwakingā the dashboard from the screensaver also turns lights on/ changes the music etc. (if this makes sense!)
Any genius or obvious solutions that I have may have missed?
command: popup
deviceID:
- b3c5cb7e-4a18ccb1
- 66aded30-cc370c15
title: ' '
hide_header: true
large: true
card:
type: 'custom:bignumber-card'
entity: sensor.time_12_hour
scale: 120px
Solved: Using button-card instead of bignumber-card. duh!
I tried it now on another laptop and an iPhone in privacy mode and after clearing cache. But I can only get it working on my fire tablets. But not on chrome, Firefox or safari. The samples from the readme all do not work on this devices only on the fire tablets. I have no idea what the problem is. Caching can not be because of privacy mode and reset of cache on all browsers and devices.
So, after some more testing I found that the āthisā is not getting correct translated to the deviceID in the script.
service: browser_mod.popup
data:
title: Popup example
card:
type: entities
entities:
- light.bed_light
- light.kitchen_lights
- light.ceiling_lights
deviceID:
- this
- dashboard
the call action is correct working
type: button
tap_action:
action: fire-dom-event
browser_mod:
command: call-service
service: script.popup_test_text
service_data:
deviceID: this
entity: sun.sun
because I could render out the deviceID in a markdown element see here
service: browser_mod.popup
data:
title: Popup example
card:
type: markdown
content: 'Diese deviceID ist {{ deviceID }}'
deviceID:
- tablet_arbeitszimmer
- this
After changing the script to this it works again
service: browser_mod.popup
data:
title: Popup example
card:
type: markdown
content: 'Diese deviceID ist {{ deviceID }}'
deviceID:
- tablet_arbeitszimmer
- '{{ deviceID }}'
and the call needed a change
tap_action:
action: fire-dom-event
browser_mod:
command: call-service
service: script.popup_all_light
service_data:
deviceID: this
From the documentation I saw it should just be - this as deice to show on but that Is not working for me using latest version of browser_mod and latest version of Home Assistant.
1 Like
Why I canāt give device an alias
You can. In configuration.yaml:
browser_mod:
devices:
99980b13-dabc9563:
name: arrakis
Doesnāt work for me
Hello, I have the same problem, someone have a fix ? I do some test with style but I donāt find a solutionā¦
popup_cards:
sun.sun:
title: MƩtƩo
style: |
mwc-icon-button{
margin: 0 0 .35em 0
}
card:
Do not apply it in card-mod theme otherwise the original popup cross will have an offset :
frontend:
themes:
original:
card-mod-theme: original
card-mod-more-info-yaml: |
.: |
mwc-icon-button{
margin: 0 0 .35em 0;
}
$: |
.mdc-dialog {
backdrop-filter: blur(100px) !important;
}
Alias didnāt work for me either. There is a chicken and egg problem where I donāt know the device id until browser_mod runs, but once the device ids are created, browser_mod wonāt name the entities with the alias. I had to delete the entities from the entity registry, then bring up the browser. Only then did the entities get created with the alias.
Pro tip: Add a browser-player card anywhere, and click or tap the device ID in the bottom left of it.
Hey, I still canāt get button cards to use pop upsā¦
For example, I have this set from the Lovelace UI inside of a button card:
tap_action:
action: call-service
service: browser_mod.popup
data:
title: Pop Up Test
fullscreen: true
iron-overlay-backdrop-filter: blur(70px) grayscale(50%)
iron-overlay-backdrop-background-color: 'rgba(41,128,185,0.25)'
deviceID: this
card:
type: entities
entities:
- entity: binary_sensor.test
This used to work, but doesnāt work for me since last updateā¦ I tried to clean cache, it doesnāt work on mobile app either.
Any solution?
If the description of a new release starts with āBREAKINGā, itās a good idea to read the release notes:
https://github.com/thomasloven/hass-browser_mod/releases/tag/1.3.0
3 Likes
cover-popup-card doesnt work anymore since last updates, is anybody else having the same issue?
No issues here. Havenāt had a single breaking popup using browser_mod.
This is running latest updates:
All DBuits popup cards work for me (light and mediaplayer popup-cards).
Can you help me? Where is the problem? Should I check the log??
Are you using browser mod built in pop up? Cuz Iām using cover pop up card. May you send me your yaml?
Hi, Iām really struggling to get this to work.
views:
- title: '1'
path: '1'
cards:
- type: vertical-stack
cards:
- type: horizontal-stack
cards:
- type: 'custom:button-card'
color_type: card
color: 'auto'
icon: 'mdi:thermostat'
tap_action:
action: call-service
service: browser_mod.popup
service_data:
title: Popup example
card:
type: entities
entities:
- light.livingroom_lamp
deviceID:
- this
Without the deviceID section, it works as expected. Adding this breaks it.
Any help would be greatly appreciated.