@Mariusthvdb wrote:
Having carefully selected (and removed several ‘default’) integrations/components, I now see the websocket_api in the newly available components list of loaded components under developer-tools/info
since I never needed it, and don’t care about the connected_clients sensor based on this, I had disabled it in the past. Especially since it was suspected to cause many errors in the logs, and maybe even resource hogs.
How come this is now loaded after all, while I have this in the config:
# https://www.home-assistant.io/components/websocket_api/ #websocket_api: sensor: # - platform: websocket_api #creates sensor.connected_clients
Not using default: in configuration.yaml, I like to be very precise in what integrations are loaded.
please have a look what might cause this appearance…
thanks!
Posts: 6
Participants: 2