Upgraded to 2021.12, Hue room entities no longer work

Hi! Thanks in advance for reading this.

The title describes my problem - I upgraded to 2021.12 (HA container in Docker) and my Hue rooms disappeared. I did read the release notes and I see that there were changes around this, but I didn’t think they’d affect me. Apparently they did, though, and I can’t see how to fix it. From the docs:

To enable any (new) light entities for Hue groups: Open settings –> integrations –> Hue –> Entities –> Click one of the disabled entities and enable it.

When I do that, I see my three missing entities with a red circle with ! in the middle, and if I hover over that, a box pops up next to it saying “restored.” I have no idea what that means. If I click the entity, the “enable” switch is already in the “on” state.

In the logs, I see this:

home-assistant  | 2022-04-03 14:52:10 WARNING (MainThread) [homeassistant.components.hue.migration] Skip migration of light.living_room because it no longer exist on the bridge
home-assistant  | 2022-04-03 14:52:10 WARNING (MainThread) [homeassistant.components.hue.migration] Skip migration of light.outside because it no longer exist on the bridge
home-assistant  | 2022-04-03 14:52:10 WARNING (MainThread) [homeassistant.components.hue.migration] Skip migration of light.bedroom because it no longer exist on the bridge

But they do exist on the bridge! They’re right there in the Android Hue app. I assume the last line of the release note section (“Legacy Hue groups of type LightGroup (which are not visible in the official Hue app) will no longer be supported!”) doesn’t apply here since they do show up in the app.

What am I missing here?

Thanks again!

Still haven’t solved this. Any ideas?

Upgrade to the latest version (because there’s less community interest in solving problems found in outdated versions).

I was trying to step through all the upgrades to reach the most recent version. I’ve backed off to 2021.11 for the moment and everything’s working fine again. Maybe I’ll try just jumping to the latest and see if it’s fixed, and I’ll ask the question again if not.