Jason Rumney

I suspect without that change, there may be a conflict causing a failure, and the delay waiting for the device to finish unloading should avoid that

Using the suggested fix from HA dev on #1917 instead of the previous PR #1876 fix for #1871 also seems to fix this.

The schedule values do not appear very useful, and should be moved to attributes, but current and last runtime appear to be more useful.

You shouldn't need to scale sensors with a class of duration. Just set the unit to `s`, and let HA take care of formating

Are the codes combined, or are the fan codes and light codes independant?

I think this is caused by Home Assistant deprecating the battery_level attribute of the vacuum entity last July, and instead instructing integration authors to replace it with a sensor of...

Problem still exists in latest version with vacuums integrations that have been modified to follow https://developers.home-assistant.io/blog/2023/07/10/vacuum-updates

I think this requires something similar to the findBatteryEntity implementation from homeassistant/frontend (maybe you can import that and use it directly) https://github.com/home-assistant/frontend/blob/7a6491a901ade1ed5069f2d26ac9a48c05cf4385/src/dialogs/more-info/controls/more-info-vacuum.ts#L229

The valve state is not missing, it is mapped to hvac_action.

If you attach the diagnostics for the device, I might be able to see more clearly why the hvac_action is not showing as expected.