Double reports if the two sensors are updated at different times

[borpin]

I am occasionally seeing double reports from the component within a few milliseconds of each other.

I wonder if this is caused by the 2 sensors being updated at slightly different times?

Does the component wait for both sensors to be updated before doing the calculations?

[borpin]

I think the component needs to check the last_updated times for both sensors to check the values are within a specific time window (as second or so I expect).

[borpin]

@dckiller51 I have worked with the author of the Passive BLE Monitor integration such that the weight and impedance sensors update almost simultaneously. custom-components/ble_monitor#617

However, I am still getting 2 updates of this component. All I can think of is that the few milliseconds between the 2 sensors update is sufficient to trigger the 2 updates.

Can a delay be added in while the component waits for both sensors to update?

[edenhaus]

Currently the component subscribe for states updates for each sensor.

On each sensor update all values are calculated.

bodymiscale/custom_components/bodymiscale/__init__.py

Lines 237 to 244 in d5c03bf

	async def async_added_to_hass(self) -> None:
	"""After being added to hass."""
	async_track_state_change_event(
	self.hass,
	list(self._config[CONF_SENSORS].values()),
	self._state_changed_event,
	)

To avoid the second report, we need to change how we subscribe. Probably introduce a delay

[borpin]

Precisely and you cannot calculate the correct details until both the weight and the impedance are available.