TypeError: async_update_entity() got an unexpected keyword argument 'device_id'

I’m getting following errors on HA startup for all of the sensors based on entities (lights, media_player with fixed mode). A sensor based on daily_fixed_energy isn’t throwing it. It’s happening for sensors I’m grouping and not. HA version: 2021.12.0 power calculation version: 0.18.3

sensor:
  - platform: powercalc
    manufacturer: ikea
    model: LED1537R6
    entities:
      - entity_id: light.l10
      ...
  - platform: powercalc
    entity_id: media_player.tv
    standby_power: 18.6
    fixed:
      states_power:
        playing: 169
  - platform: powercalc
    name: fridge_energy
    daily_fixed_energy:
      value: 0.73

2022-02-22 22:26:55 DEBUG (MainThread) [custom_components.powercalc.sensor] Binding sensor.l10_power to device ebexxxxxxxxxxxxxxxxxxxxxxxx0
2022-02-22 22:26:55 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback create_individual_sensors.<locals>.<lambda>(<Event homeas...nt_started[L]>) at /config/custom_components/powercalc/sensor.py:438
Traceback (most recent call last):
File "/usr/local/lib/python3.9/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/core.py", line 835, in _onetime_listener
self._hass.async_run_job(listener, event)
File "/usr/src/homeassistant/homeassistant/core.py", line 452, in async_run_job
return self.async_run_hass_job(HassJob(target), *args)
File "/usr/src/homeassistant/homeassistant/core.py", line 433, in async_run_hass_job
hassjob.target(*args)
File "/config/custom_components/powercalc/sensor.py", line 438, in <lambda>
lambda _: bind_entities_to_devices(
File "/config/custom_components/powercalc/sensor.py", line 525, in bind_entities_to_devices
ent_reg.async_update_entity(entity.entity_id, device_id=device_id)
TypeError: async_update_entity() got an unexpected keyword argument 'device_id'

[nikadaika]

Thanks, @bramstroker. I decided to update HA to the most recent version and deal with the breaking changes. It fixed the problem like you predicted.

[bramstroker]

@nikadaika that’s great. Just released v0.19.0 which also contains this fix.