🔹 Browser_mod - turn your browser into a controllable device, and a media_player

kajmaj · February 9, 2021, 6:59pm

FKB has [Remote admin](https://www.fully-kiosk.com/en/#remoteadmin) function

atonyshepherd · February 10, 2021, 12:50am

Just got the 1.3.0 update. I have a popup configured for a button card using the “button-card” repo (https://github.com/custom-cards/button-card). It worked before the update, and no longer does. The normal button card still works fine with popups. Is there something I can tweak on my end to make it work?

If it’s helpful, here’s a snippet of my code.

type: 'custom:button-card'
style: |
  ha-card {
    height: 120px;
  }
color_type: card
label: |
...

tap_action:
  action: fire-dom-event
  browser_mod:
    command: call-service
    service: browser_mod.popup
    service_data:
      title: Alarm System

M1ke · February 10, 2021, 1:27am

Hey Tony,

Even though I’m pretty sure the code is wrong in your snippet, I can’t get it working either. According to the GitHub examples, it should be:

type: 'custom:button-card'
style: |
  ha-card {
    height: 120px;
  }
color_type: card
label: |
...

tap_action:
  action: fire-dom-event
  browser_mod:
    command: popup
    title: Alarm System

Unfortunately no luck on my side

atonyshepherd · February 10, 2021, 1:56am

Ah, yeah you’re right. Thanks! I guess that’s what I get for trying to get what I needed to out of the diff.

Skeletorjus · February 10, 2021, 9:15am

@M1ke @atonyshepherd
It actually seems like the old way with calling the browser_mod.popup-service still works, but if you include

deviceID:
  - this

it does not work anymore. This unfortunately means that the popup will appear on all devices.
I could not get the fire-dom-event for popup to work at all.

thomasloven · February 10, 2021, 9:15am

1.3.0 is a BREAKING release
Please read the release notes

pergola.fabio · February 10, 2021, 9:22am

hey @thomasloven

i see indeed this new update in Hacs, but unable to update, when i click the update button, i see this error message:

2021-02-10 10:19:24 ERROR (MainThread) [custom_components.hacs] No content to download

edit : if i go to the intrgration list , then to browser_mod, the place where you can downgrade/upgrade versions, … then its possible to update
seems the error only comes when updating from the community overview page

ASNNetworks · February 10, 2021, 10:47am

Hi, before updating: does this also work with other cards that use action: call-service?

I see that the action has been changed to action: fire-dom-event. But for instance, I don’t see custom:button-card using that action.

Hi @RomRider, sorry for tagging out of the blue. But I think it’s good for all users to know this since your card and browser mod are two of the most used components of users.

Can you verify that the new action introduced by browser mod actually works with button card?

pollinolas · February 10, 2021, 10:51am

all my popup windows have stopped working after update, I have tried it with the new configuration of version 1.3.0, I was forced to go back to the previous version.
all my popups are called from custom button, could that be the cause?
someone else with this problem?
regards

RomRider · February 10, 2021, 11:47am

None of the custom cards will work with that, wondering where that new format comes from. Any information that you can point to so that we can update the code of custom-cards? Has there been any formal announcement on the core side?

thomasloven · February 10, 2021, 11:51am

It’s been in the core code for almost a year in preparation for future features.
But so far it has never been used.
That’s why it’s also undocumented.

github.com

home-assistant/frontend/blob/8d13745c6b822a76f6724e32c2b10bf57ae645e7/src/panels/lovelace/common/handle-action.ts#L137


          message: hass.localize("ui.panel.lovelace.cards.actions.no_service"),
        });
        forwardHaptic("failure");
        return;
      }
      const [domain, service] = actionConfig.service.split(".", 2);
      hass.callService(domain, service, actionConfig.service_data);
      forwardHaptic("light");
      break;
    }
    case "fire-dom-event": {
      fireEvent(node, "ll-custom", actionConfig);
    }
  }
};

I didn’t even think of custom cards when changing this. Sorry.
But as of now I see no other way to have this functionality without potentially breaking future Home Assistant versions or risk introducing security issues.

RomRider · February 10, 2021, 11:55am

Thanks for the link, I’ll look into that for my cards (cc @pollinolas) . But good luck to all the other devs with that change

Suggestion @thomasloven, to add to the release notes that custom-cards will require to be updated for this to be supported.

thomasloven · February 10, 2021, 12:22pm

I should have been more clear too.
You should only use action: fire-dom-event if you want the action to happen only on the current device.

If you want it on all devices, or a certain device with a given deviceID, you should use action: call-service as usual.

deluxestyle · February 10, 2021, 3:11pm

If I understand the changes correct. I have to wait till all custom cards will use the fire-dom-event if I want to use the popup within a custom card?

thomasloven · February 10, 2021, 3:18pm

The popup_card method should still work.
https://github.com/thomasloven/hass-browser_mod#replacing-more-info-dialogs

deluxestyle · February 10, 2021, 3:19pm

sorry. yes this is still working.
but if I use the service browser_mode.popup, then I have to wait or?

thomasloven · February 10, 2021, 3:20pm

If you previously used

deviceID: this

or

deviceID:
  - this

Then yes.

deluxestyle · February 10, 2021, 3:32pm

thanks.
a different question.
would it be possible to adjust the header of the popup to the standard header of the more-info dialog?

header more-info

header popup

CKRO · February 10, 2021, 4:25pm

Hi @thomasloven,

i use scripts for complex popups to keep the yaml in lovelace small and I can also use variables to use a popup multiple times with different entities:


service: browser_mod.popup
data_template:
  deviceID: '{{ deviceID }}'
  title: Light
  hide_header: true
  large: false
  card:
    type: 'custom:layout-card'
    layout: auto
    cards:
      - type: 'custom:light-entity-card'
        header: Light
        entity: '{{ entityID }}'
...

Now that - DeviceID: this - no longer works, how can I use a script to only display the popup on the current device?

I would be very grateful for every tip, because currently not a single popup works anymore.

Thank you
Chris

dorremez · February 10, 2021, 8:25pm

So for now, there is no way of using only the current device with popup?