Yes, I get the same error. Except the customization page seems to remember the customizations that I set in the UI, but the rest of the UI does not.
For example, when I set an ‘openning’ sensor device_class to ‘lock’, the sensor briefly shows up as a ‘lock’ on the lovelace UI, but quickly goes back to ‘openning’.
The developer tools > states page shows it as ‘openning’ too.
TBH I’m finding the mixture of yaml files and UI configuration annoying - I’d like to take everything out of yaml if possible. Having to add a customize.yaml just to allow me to modify something in the UI seems really strange.
It seems that the message appears when this line evaluates to false.
Can anyone help me understand what that line is doing? Something to do with comparing localConfig and globalConfig? My JavaScript knowledge is not great but if someone could give me a pointer I might be able to fix it.