Request data more often?

[apbarratt]

I regularly find I can go hours without an update on certain values that have undoubtedly changed, but it's never any specific value that I'll have trouble with. Like, I'll know I've run out of hot water, but the hot water temperature won't reflect it for another hour, or at times the hot water temperature will just become marked as unknown because it just hasn't received an update in so very long (I've turned on retain to at least handle this, but still not ideal). Right now I can see that I've used 4kWh of energy using my heat pump, but some how used 10kWh only on heating water. This is because the hot water energy usage didn't update for several hours, so it includes a large chunk of usage from yesterday when the kids were in the paddling pool, but that should have been known about yesterday when it happened.

If I check on the nonsense thermostat unit I was provided, I can see that it's received up to date data at all times, what can I do to make ebusd get it more often too? There's a polling field that supposedly checks for updates every 15 seconds, but that's clearly not doing what I need.

Here's my config so far:

scanconfig: true
loglevel_all: notice
mqtttopic: ebusd
mqttint: /etc/ebusd/mqtt-hassio.cfg
mqttjson: true
network_device: 192.168.0.166:9999
latency: 10000
mode: ens
pollinterval: 15
accesslevel: "*"
http: true
mqttvar: >-
  filter-direction=r|u|^w,filter-name=status|temp|humidity|yield|count|energy|power|runtime|hours|starts|mode|curve|^load$|^party$|sensor|timer
configpath: /config/ebusd-configuration_jonesPD/latest/en
loglevel_other: error
loglevel_network: error
loglevel_bus: error
loglevel_update: error
loglevel_main: notice
mqttretain: true

I feel I must be missing something obvious and hope whatever it is can be implemented in add-on options to avoid the frustration of merge conflicts in settings when pulling latest changes to config files from repos.

If it's only doable by editing files though, let me know what I'm doing wrong and I suppose I'll just have to do it until this add-on can handle it itself. I recall a piece of documentation somewhere once suggesting I'd need to edit every single line for the hundreds of sensors involved, I'm seriously hoping that's not necessary. Just gimme all the datas and all the time 😅

[LukasGrebe]

This depends on when your ebus hardware broadcasts / sends the values. You can also configure a polling with your config csvs. See the official ebusd repository for more info.