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

[DrSpaldo (Doctor Spalding)]

Thanks, looks like you are right and the title is required. Thank you!

[arganto]

Just double-checked again. In both cases

tap_action:
  action: fire-dom-event
  browser_mod:
    command: call-service
    service: browser_mod.popup
    service_data:
      deviceID: this
      title: Wecker
      card:
        type: entities

	
tap_action:
  action: fire-dom-event
  browser_mod:
    command: popup
    title: Wecker
    card:
      type: entities

you are right and it is only working with title here as well.

[vinzcenzo (Vincent)]

I have a question regarding browser_mod integration because I’m facing out an annoying situation.

Each time I reset my browser cache with cookies (which often happens with Home Assistant troubleshooting ), it creates a new device when I log back with the same browser.

After a time, I get a huge list of unavailable devices.

in the above screenshot, I have 12 devices (cache cleared two days ago, Iast time I got until >50 devices), while only 3 browsers still exist.

I can remove manually the entities from the “entities panel”, but I don’t find a way to remove devices easily.

How do people deal with that? By my side, the only solution I found for the moment is to delete the integration and re-add it.

Thanks for your feedback.

[rmertz3282]

I think the trick lies in disabling.

I originally had your same problem until I did this.

[DrSpaldo (Doctor Spalding)]

Thanks again @rmertz3282 & @arganto, I have it working again finally

If you are interested @kazihaha , below is my working card config, if you compare it to my previously posted one above:

          - type: glance
            entities: 
            - entity: switch.fanpower
              name: Dyson Fan
              tap_action:
                action: fire-dom-event
                browser_mod:
                  command: popup
                  title: 'Dyson Fan Controls'
                  card: 
                      type: glance
                      entities:
                      - entity: switch.fanpower
                        name: Power
                        tap_action:
                          action: toggle
                      - entity: switch.master_bedroom_auto_mode
                        name: Mode
                        tap_action:
                          action: toggle
                      - entity: switch.master_bedroom_night_mode
                        name: Night
                        tap_action:
                          action: toggle
                      - entity: switch.oscillation
                        name: Oscillation
                        tap_action:
                          action: toggle

[vinzcenzo (Vincent)]

I think the trick lies in disabling.

I originally had your same problem until I did this.

Thanks for your answer.

This only disables all entities related to devices (available or unavailable), but devices are still there.

If the devices are unavailable (and for sure it will never be back in the future), I’m not able to delete them without removing the integration… that’s my concern.

As browser_mod is probably based on a cookie that is related to the session context, the behavior seems correct: when clearing the entire cache, it will delete the ID related to the device and create a new one when the browser reconnects the next time because it is considered as a new device.

But I would like to clean up the mess without having to remove and re-add the integration.

By looking at the community feed I finally found an old thread that cover this problem : Delete individual device (and entity) from integration - #55 by SnoWake

This is apparently not only related to browser_mod.

[skank]

Hi all,
A question.
Is it possible to make a button when i click on it, i get a popup showing the new energy dashboard or the media browser (with other button) inside the popup?
I’m not sure how.

[suxlala]

Use iframe (web) card inside the popup and put your energy dashboard or media browser address as URL.

[skank]

Why didnt i think of that myself lol
Great will do that

[El_Duderino (Lance)]

I’m having issues with this card. I have the following in my config.yaml:

browser_mod:
  prefix: "browser_"
  devices:
    a1521498_ea1ae31b:
      name: mbp_13_safari
      disable:
        - light
        - media_player
    218f8982_b93c0162:
      name: master_tablet_fully
      disable: 
        - media_player
      enable:
        - camera
        - binary_sensor
        - sensor
        - light
  disable:
    - all

However, in Developer Tools/States, I only see entities with the browser mod ID (i.e. 218f8982_b93c0162) and only camera and media_player with no sensor.

My goal is to manage charging based on the battery of my tablet (Fire HD 10) running Fully Kiosk, so maybe there’s another way that’s a bit simpler. Very curious what I’m missing here.

Thank you!

[rmertz3282]

Please clarify.

Are you trying to use browser mod to determine the battery level of your tablet? If so I used the REST API.

Fully Kiosk Browser

First of all, I know a lot of people have been using the Fully Kiosk Browser on Android for displaying HA, or Floorplan, which works great (I use it myself). But I haven’t come across a write up describing what else you can do with Fully, so I thought I’d share that here. So, besides installing Fully on an Android device, setting the start URL to your HA URL, and putting it in kiosk mode, it also has a plethora of sensors, and even switches you can control from HA. The Fully browser is also ca…

[El_Duderino (Lance)]

That’s exactly what I’m looking to do! Will the curl commands work on supervised HA (hassio)?

[rmertz3282]

Works perfectly for me. I have an automation that turns off the outlet when it reaches 90% and back on at 20%.

[El_Duderino (Lance)]

@Fully Kiosk Browser

"{{ states.sensor.foo.attributes.batteryLevel }}"

Thank you so much. This is exactly what I was looking for. I would like to figure out the logic to only have it charge during the day (so the switch doesn’t click or light up while sleeping) unless it’s absolutely necessary. I use node red, so will experiment with that when I have a chance.

Thanks again.

[El_Duderino (Lance)]

@rmertz3282 Any idea why I’m not getting more info?

Specifically, I’m not getting screen on data. I can turn the screen on/off with the switch, but it doesn’t recognize if it’s on or not. When I put the same command in my browser, I get much more data back. Do I need to add screen.on to the sensor?

[critical_limit (Dirk)]

Please help me, i´m new to browser mod.

is it possible to do an automation which brings back the first page in Lovelace after last action detected on a wall mounted iPad?

At the moment I use an automation triggered every 2 minutes:

alias: iPad Standardseite nach 2min
description: ''
trigger:
  - platform: time_pattern
    minutes: /2
condition: []
action:
  - service: browser_mod.navigate
    data:
      navigation_path: /lovelace/0
      deviceID:
        - ipad
mode: single

But what I´m searching for is an automation that starts and wait for 2 mins after ipad is touched.

Possible?

[critical_limit (Dirk)]

deleted, sorry

[SgtBatten]

You should try using the mode restart instead of single. The trigger would be any touch and the action would contain the 2 minute wait and then the navigation action.

This way every touch resets the automation and therefore resets the timer.

[critical_limit (Dirk)]

Thats the way I do with my motion sensors. But which trigger is able to detect a touch on the ipad?

[brot123]

I have created 3 pages on my HA Lovelace Dashboard so I don’t overload the single page with information.

How can I achieve that in interaction with the Fully Kiosk Browser App I can achieve an automatic switch between the 3 pages after a defined time and I can also display the Energy Dashboard, this always in Alternation, can the browser mod do that? Thanks