2.1.0

EVERYTHING CHANGES BETWEEN 1.5 and 2.0!
READ THE README!
NOTHING WILL WORK!

Changes in 2.1.0:

• Browser Mod panel can now be seen by non-admin users
• Browser registration can be locked so non-admin users can't unregister their browsers
• Changing sidebar title should work better
• Clear error messages for services (in browser console)
• Add set_theme service
• Add notification service
• Fix dismiss action executing immediately for multi-level popups (HOW did you manage to discover this bug in less than 24 hours, @Protoncek?)
• Align popup cards on mobile
• Custom cards now work in popups
• Map card now works in popups
• Added some functions to the javascript service, like lovelace_reload()

Bugfixes

Remember that Browser Mod 2.0 is breaking from Browser Mod 1.5.

Re-read the readme! Everything is changed.

Browser Mod 2.0! BREAKING!

Introducing Browser Mod 2.0!

Easier to use!

More stable!

Prettier!

Better!

Also with this!:

READ THE README!
EVERYTHING HAS CHANGED!

Yes. Everything. Nothing you used to do with browser_mod will work after installing this.
As for why; please see the explanation in the FAQ at the bottom of the readme when you're re-reading that anyway 😉

Fix cameras

1.5.3

Bump version to 1.5.3

Various tweaks and fixes

1.5.2

Update dependencies. Bump patch version.

Fix browser-player card for 2021.11

1.5.1

Bump patch version number

Improved camera for Fully Kiosk Browser

Camera support for FKB has been added, and does not require any special configuration.

Stability improvements on boot

Also added option to control FKB screensaver instead of screen.

Various tweaks and fixes

1.3.1

Build release 1.3.1

1.3.0 BREAKING RECOMMENDED UPGRADE

This release changes the way browser_mod functions are called from the frontend when you want something to happen only on the current device.

Instead of doing

tap_action:
  action: call-service
  service: browser_mod.toast
  service_data:
    message: Hello, world!
    deviceID: this

you now need to do

tap_action:
  action: fire-dom-event
  browser_mod:
    command: toast
    message: Hello, world!

---

YOU ONLY NEED TO CHANGE THIS IF YOU HAD

deviceID: this

OR

deviceID:
  - this

IN YOUR SERVICE CALL BEFORE

---

This may be a bit tedious to change, but it'll be worth it in the end, as this will allow for adding new cool functionality in the future.
Also, this change will make sure that browser_mod does not break Home Assistant 2021.3.0 (sic!).

There's also a new service for calling multiple services after each other, and one to put delays in between them.

** It's worth taking the time to re-read the readme**

Oh! And browser_mod devices now correspond to Home Assistant Devices. That's very cool!

---

For developers of lovelace plugins

This change makes use of the fire-dom-event tap action.
It's actually been in the code for almost a year, but has never been used (yet).
If your lovelace plugin does not support this, they will not work for direct triggering of browser_mod functions.
Calling a service as before still works, though, it's just the deviceID: this that's gone.

See: https://github.com/home-assistant/frontend/blob/8d13745c6b822a76f6724e32c2b10bf57ae645e7/src/panels/lovelace/common/handle-action.ts#L137