Starkvind auto mode reports "unknown" consumption

[MB901]

System Health details

System Information

version	core-2025.5.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.13.3
os_name	Linux
os_version	6.6.74-haos-raspi
arch	aarch64
config_dir	/config

Checklist

• [x] I have read the FAQ to see if there is a known solution to my problem.
• [x] I have enabled debug logging for my installation.
• [x] I have filled out the issue template to the best of my ability.
• [x] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• [x] This issue is not a duplicate issue of currently previous issues..

Describe the issue

When an IKEA Starkvind air‑purifier entity managed through Zigbee2MQTT switches to auto mode, its fan.<name> entity state changes from a numeric percentage (0‑100 %) to the literal string auto.powercalc currently reads the percentage attribute of the fan entity; as soon as that attribute disappears, the resulting Power and Energy sensors become unknown.

Meanwhile Zigbee2MQTT continues to expose a numeric sensor.<name>_fan_speed (0‑9) that accurately tracks the fan speed regardless of mode. Powercalc has no built‑in fallback to use this sensor, nor a way to map it automatically.

Reproduction steps

1. Zigbee2MQTT + IKEA Starkvind integrated in Home Assistant.
2. Configure Powercalc using the standard fan profile (or any linear profile) against fan.<name>.
3. Set the Starkvind to Auto mode (either on the device or via Home Assistant).
4. Observe the Powercalc sensor state.

Debug logs

irrelevant.

Diagnostics dump or YAML config

No response

[bramstroker]

Thanks for raising this, and for the clear explanation.

It’s unfortunate that the fan.<name> entity doesn’t maintain a numeric state in auto mode, it does feel inconsistent, especially since a usable numeric value does remain exposed via sensor.<name>_fan_speed. If the percentage state attribute had continued updating, the current Powercalc profile would have worked seamlessly.

This isn't a straightforward issue to solve. We’d need to introduce some kind of composite strategy in the model.json to handle fallback logic, but currently, there's no support for referencing a dynamic entity_id in the profile based on the primary entity. Supporting that would require a new feature, and even then, it comes with complexity and risk, especially if the user changes entity IDs, which is a legitimate concern.

@Mariusthvdb, you contributed this profile a couple of months ago. appreciate your input! Could you share how you're integrating the Starkvind in Home Assistant? And how does your setup behave when switching to auto mode, do you see the same issue?

[Mariusthvdb]

It behaves as it should ;-)

And my IKEA devices are integrated via their Dirigera hub over HomeKit and/or Matter

[bramstroker]

@MB901 I suggest you to raise an issue at Zigbee2MQTT so it will behave the same with other integrations where also the fan speed/percentage attribute is updated which is expected behaviour imho. I don't use Zigbee2MQTT myself neither I have these Zigbee devices, so I can't further support or test on this topic.

[MB901]

Thank you for the quick feedback.

Got it. I’ll open an issue on the Zigbee2MQTT repo so that fan speed is always included in the state payload, even when the Starkvind is in auto mode. I’ll reference this Powercalc issue in the new ticket and drop the link back here.

https://github.com/Koenkk/zigbee2mqtt/issues/27719

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.