Description
I am using the ioBroker.hass adapter (v1.4.0) to sync entities from Home Assistant to ioBroker. My Home Assistant instance has a very large number of entities (over 6,000), including many temporary or technical entities (e.g., from the browser_mod integration or mobile devices).
The Problem
The adapter currently synchronizes ALL available entities via WebSocket. This causes the ioBroker object tree to bloat significantly. Having 6,000+ objects in the hass.0 namespace leads to massive performance issues and lag within the ioBroker Admin UI (especially when searching or expanding the object tree).
Manually deleting objects in ioBroker is not a solution, as the adapter recreates them instantly as soon as HA sends a state update.
Proposed Solution
It would be extremely helpful to have a filtering option in the adapter instance settings.
Specifically:
- RegEx Filter: An input field to define which entities should be included or excluded (e.g., a "Blacklist" for unwanted prefixes like
light.browser_mod_*).
- Selective Sync: The ability to ignore certain domains (e.g., exclude all
automation or binary_sensor entities).
Additional Context
Many users with complex smart home setups face this issue. Implementing a filter would make the adapter much more scalable for large installations and improve the overall performance of the ioBroker Admin interface.
Thank you for your great work on this adapter!
Description
I am using the ioBroker.hass adapter (v1.4.0) to sync entities from Home Assistant to ioBroker. My Home Assistant instance has a very large number of entities (over 6,000), including many temporary or technical entities (e.g., from the
browser_modintegration or mobile devices).The Problem
The adapter currently synchronizes ALL available entities via WebSocket. This causes the ioBroker object tree to bloat significantly. Having 6,000+ objects in the
hass.0namespace leads to massive performance issues and lag within the ioBroker Admin UI (especially when searching or expanding the object tree).Manually deleting objects in ioBroker is not a solution, as the adapter recreates them instantly as soon as HA sends a state update.
Proposed Solution
It would be extremely helpful to have a filtering option in the adapter instance settings.
Specifically:
light.browser_mod_*).automationorbinary_sensorentities).Additional Context
Many users with complex smart home setups face this issue. Implementing a filter would make the adapter much more scalable for large installations and improve the overall performance of the ioBroker Admin interface.
Thank you for your great work on this adapter!