Limit HA Entity in MSR

[wmarcolin]

Hi @toggledbits

I'm new to HA, and I just finished integrating it with MSR. It was very easy to configure and interact between platforms.

However, one thing that bothered me is that all HA Entities were sent to MSR, and in my opinion, this generates unnecessary integration overload. I searched the manual and here in the forum for a way to delete everything I don't want to come to MSR, such as all this information from Sun *.

Is it possible to configure this, as we already do with Vera, for example? And if possible, would using a wildcard such as hass>sun* automatically exclude all other entities of this type?

Thanks.

[toggledbits]

@wmarcolin said in Limit HA Entity in MSR:

in my opinion, this generates unnecessary integration overload

What's your basis for that opinion? On the HA side, all entities and events are published for everything on HAs websocket API, without filtering, so the data is coming to Reactor regardless. On the Reactor side, even with thousands of entities in my home environment, the load overall is low to Reactor and its host (load average <0.1 at 1, 5, and 15 minute measurement periods on an RPi 4), and HassController is only a fraction of that total load.

You can filter out entities, but it won't stop HA from sending data about them, and it won't stop Reactor from receiving that data and having to process it enough to know it should ignore it. What you want to know is in the docs, if you're committed to it.

[wmarcolin]

Hi @toggledbits

I understand, I know that the system is very robust and supports thousands of interactions, I even imagine that because the two VMs of Reactor and HASS are on the same computer, the speed of communication is enormous.

So, apart from the overload issue that not have, I'm thinking about the practicality of using it, by removing from the list of HASS entity devices that I'm not interested in viewing in Reactor.

Looking at the manual, excuse my incompetence, I really couldn't identify how to configure not to load the Entity in Reactor, I made several attempts and I can't remove the devices. Below is my last attempt. If you can help me with the correct configuration.

  - id: hass
    enabled: true
    implementation: HassController
    name: Home Assistant System
    config:
      source: 'ws://192.xxx.xxx.xxx:8123'
      access_token: "eyJhbxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxc0N>
      #
      # ignore_cert - If true, suppresses certificate validation when using wss:// (Websocket
      #               with SSL/TLS) and thus allows a self-signed certificate to be used on
      #               the Hass system.
      #ignore_cert: false
      #
      # dump_all_states - This is for troubleshooting. Do not enable unless asked.
      #dump_all_states: false
      exclude_entities:
        - "hass>sensor_sun*"

Thanks.

[toggledbits]

HassController uses filter_entity not exclude_entities. Here are some examples:

  - id: hass
    implementation: HassController
    config:
      source: 'ws://192.xxx.xxx.xxx:8123'
      access_token: "xxxxxxxxxxxxxxxxxxxxxx"
      filter_entity:
        - sun_sun  # using Reactor entity ID, filter out the entire matching entity
        - "sun.sun"  # using HA domain.entity_id form, filter out entire entity

There are no wildcards.

You can also filter down to the HA attribute level. In this form, you use the HA domain.entity_id form combined with HA attribute names (you need to know/discover these from reading HA's integration documentation or examining your hass_states.json log file).

      filter_entity:
        # This is the abbreviated syntax for a single HA attribute
        "sun.sun": "last_updated"  # ignores only this *one* HA attribute
        #
        # This is the full syntax for one or more HA attributes
        "sun.sun":
          - last_reported
          - last_updated

Filtering at the attribute level is intended for when an attribute on the entity changes frequently but isn't of use to your configuration -- by filtering the attribute out, Reactor won't post changes for its interpretation of that attribute, and thus Rules that depend on the entity won't be notified that it may have changed.