Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

integration_entities('browser_mod') showing unexpected behavior #780

Open
Dtrotmw opened this issue Jan 5, 2025 · 1 comment
Open

integration_entities('browser_mod') showing unexpected behavior #780

Dtrotmw opened this issue Jan 5, 2025 · 1 comment

Comments

@Dtrotmw
Copy link

Dtrotmw commented Jan 5, 2025

My Home Assistant version: Core 2025.1.0
Supervisor 2024.12.3
Operating System 14.1
Frontend 20250103.0

What I am doing: I'm trying to list all the browser_id's belonging to this integration

What I expected to happen: a list of entities

What happened instead: It varies; it produces a null result immediately after a system reset then is populated each time a new browser logs on

Minimal steps to reproduce:

integration_entities('browser_mod')

Error messages from the browser console: no error messages, but function returns null

By replacing the space in the checkboxes ([ ]) with an X below, I indicate that I:

  • [ X] Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).

  • [ X] Have made sure I am using the latest version of the plugin.

  • [ X] Have followed the troubleshooting steps of the "Common Problems" section of https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins.

  • [ X] 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.

@Dtrotmw
Copy link
Author

Dtrotmw commented Jan 6, 2025

I should add that it behaves differently in developer tools than in a sensor. In developer tools the list of sensors grows each time a browser_mod entity gets updated whereas the same YAML in configuration.yaml defining a sensor periodically gets stuck, at least until the template yaml is reloaded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant