updateFrequency set to zero - but still seem to have throttled messages

[eBoon123]

Hello upgraded from a prior version (version 1.xx??????) and am having a problem with messages being throttled even though I am setting updateFrequency to the default of 0. I am still only seeing 1 message every 1 second or so. In prior version (using update_frequency) - I would get many messages per second. Here is my local.yml file:

global:
  instanceName: garage
  integrations:
    - homeAssistant
    - bluetoothLowEnergy
cluster:
  autoDiscovery: false
homeAssistant:
  mqttUrl: 'mqtt://192.168.1.105:1883'
bluetoothLowEnergy:
    name: garage_presence
    updateFrequency: 0
    processIBeacon: true
    onlyIBeacon: true

Same issue when I just remove the updateFrequency parameter altogether.

Thanks for this great package!

[mKeRix]

The 0.x and 1.x versions of room-assistant made use of MQTT Room in Home Assistant and sent a MQTT message each time an instance discovered a beacon. The 2.x versions of room-assistant handle all that by communicating with each other directly and will only send a new MQTT message once something changed, e.g. when there is a different state or the attributes have been modified. This was actually done to reduce the amount of MQTT messages, as that was a common complaint before.

Are you actually seeing a functionality problem due to the lower amount of messages or was it just unexpected?

[eBoon123]

I am referring to the MQTT message that have the distance payload ({"distance":10.1,"last_updated_at":"2020-11-09T21:54:57.445Z"}) for my iBeacon. I only get one of these MQTT messages every second or so instead of multiple messages per second. I use the distance to determine whether my vehicle is coming or going - so the more records I have the better!

Thank you (I hope this makes sense)

[eBoon123]

Is it possible that this version will only send out a distance payload message a maximum of once every second instead of multiple messages every second?

[mKeRix]

For attributes (like the distance) the only way of limiting the output is setting updateFrequency to a positive number. Other than that the sensor is updated immediately once new values arrive and additionally in an interval of timeout to catch devices that have gone out of range. The Home Assistant integration then receives these new attributes and defers sending a message by a tick to prevent changes to multiple attributes that were done at the same time from creating multiple messages. This equals a setTimeout with a timeout of 0 in JS terms.

None of this should cause a throttling to 1 msg/second. Just to be sure: you are using a single room-assistant instance and a beacon that broadcasts in a sub-second interval?