I’ve got the gateway configured through yaml for a year or so, this just started popping up. Should I remove the yaml config?
See the latest HA blog 0.111 and inside:
Release 0.111.1 - June 11
- Xiaomi Miio gateway: add ip to zeroconf discovery title (@starkillerOG - #36653) (xiaomi_miio docs)
And see the explanation in #36653
It seems to me that it is only necessary if you have more than one Xiaomi gateway. I have only one and everything is working correctly in release 0.111.3 (I use the Xiaomi gateway only for 1 item, all other Xiaomi devices are connected by Zigbee2mqtt)
1 Like
Great, thanks for the info. I’m also just using the gateway as a night light and alarm sound. Everything zigbee goes through zigbee2mqtt as well 
Nice to see these add-ons, but a word to the developers - have you ever heard of “non-breaking change”? How about checking the config.yaml file and not automatically destroying everything is there is a Xiaomi entry there? It’s a real pain to have to be on your toes every time you updated HA just in case something breaks…
That has been addressed so many times now that it becomes boring. HA is not at product release level. It is still in beta if you wish. Breaking changes are bound to happen all the time. Everyone will urge you to take a good look at the changelog and breaking changes section for every release post 
I feel your pain, the devs feel your pain, without breaking changes, things are stuck in the past and can’t become better before setting them in stone
Hope it didn’t mess up your HA too much! That’s what we get for ‘living on the edge’ using a beta product for our home automation. And even in beta, I’m very happy with each and every new release even if it means having to fiddle around a bit with configurations
I get that, and that the architecture of HA does not permit non-breaking change for core changes but it’s all in the mindset. In this case, it would be possible, surely, for the new integration to check the config file first?