[Bug]: browser_entities template variable is undefined

[jadero]

My Home Assistant Version

Core 2025.9.4
Frontend 20250903.5
Browser Mod 2.5.3

What I am doing

Installed browser mod according to the documentation, registered my browser in browser mod panel, refreshed browser tab (F5).

What I expect to happen

In templates I am provided with a dictionary variable called browser_entities. I want to read this variable to detect if the dark theme is currently enabled or not.

What happened instead

I tried to read this variable in the template editor via {{ browser_entities }} but it only says 'browser_entities' is undefined.

Minimal steps to reproduce

see above

Include any yaml code here

{# this variable is not defined, although my browser is registered and I can see a bunch of new sensors including binary_sensor.browser_mod_<id>_browser_dark_mode #}
{{ browser_entities }}

Error messages from the browser console

-

By checking each box below I indicate that I ...

• Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).
• Have made sure I am using the latest version of the plugin.
• 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.
• If this issue is to do with an Android device losing connection, sensors becoming unavailable etc., please confirm you have read, understood and tried methods described in Wiki Article Andoird Devices 'Always On'

[dcapslock]

Hi, this is expected, {{ browser_entities }} will not be available in the template editor.browser_entities is a special dictionary that can only be passed from the Browser via a Browser call or Frontend settings templates.

If you are wishing to check on a specific browser, then use its sensor directly. For Dark mode the sensor you are looking for is similar in name to sensor.browser_id_browser_dark_mode (e.g. sensor.my_browser_browser_dark_mode).

The use cases for using browser_entities are i) including in a Frontend Browser Mod settings template, ii) including in a Frontend Default action or iii) Passing to a backend script from a Browser call via the using the replacement parameter THIS.

If you can describe what you are trying to achieve then I can guide you more. If you are just wanting to know about a specific Browser, use its sensors directly. You can check out what they are in Services and Devices. If you are wishing to one of the use cases mentioned above but are not sure how to go about it, describe more about what you are trying to achieve and I can guide you further.

[dcapslock]

FYI: PR #1044 has updated the documentation to be clearer on how browser_entities is used and that it is not available i template editor.

EDIT: Documentation now updated in dev branch with availability of 2.6.1-beta.1

[dcapslock]

v2.6.1 Released. Documentation now in master. 2.6.1 requires Home Assistant 2025.10 which will be released shortly.