I have ‘eBUSd Edge’ and ‘Mosquitto broker’ add-on installed.
The MQTT automatically creates 6 MQTT devices.
My Vaillant device VRT380/2 thermosstat has 421 entities.
My Vaillant device Ecotec VHR25 kettle has 97 entities.
I see in the log that lots of entities are updated that I do not use.
EBus is not the fastest bus around.
Is it beneficial to update less entities?
What is the preferred way to get less entities? : change csv, disable entities, filter entities in mqtt?
The hass-mqtt.cfg file (or similar, on mobile right now) supports filtering in various ways. That’s probably the cleanest way, but also the most tedious one.
i start ebusd now with filtername = z1RoomTemp|z1DayTemp.
This solved my problems.
Before when i changed the requested temperature on my thermostate I got the new value with a delay of 15 minutes. Now I get them withing the poll interval (5 seconds).
Glad i found my problem. But what i do not get is: everbody should have this problem. very strange
Sounds like you don’t set your favorite entities to automatic updating, easily done via an MQTT query to .../path/to/entity/get with payload ?1. I have an automation that does that whenever HomeAssistant starts and once per hour for good measure.
I understand this but i feel it is a trick bypassing the real problem.
The real problem is that ebusd add-on creates way too much entities.
So much that updating them takes 15 minutes or more (ebusd doesn’t want to saturate the ebus).
So limiting the number of entities is the only way i think. Too bad that there is not an easy way to do that. I filed a request to the project mananager
I didn’t mean to say you should do the priority marking instead of your filter, I wanted to suggest you could do it on top of it. That said, you may want to add Hc1 (heating circuit) and Hwc (if you do hot water with the system) to your filter and maybe add a negative filter to the scheduling entities for extra cleanup (unless you want to see or modify schedules in HA, of course! I do not.)