Emulated_hue deprecated warning but if I follow instructions it breaks my emulation

Configuration
1

I have messages in my log that say

'emulated_hue' is deprecated. Please rename 'emulated_hue' to 'emulated_hue_hidden' in your configuration file.

But if I follow the instructions and repalce emulated_hue with emulated_hue_hidden in my configuration then hue emulation stops exposing the input booleans I have exposed.

2
3

wow, did you upgrade from ancient times?

4

No I have been keeping it up to date. I guess I just got the configuration from an outdated post. But I still canā€™t get the ā€œcorrectā€ version to work. I added the emulated_hue recently and it was working so I didnā€™t look at the logs. Then I upgraded to 0.80 from 0.79 and I always check the logs after an upgrade so I got mis-directed into into thinking it was a new issues.

Actually what was the point of deprecating this in version 0.55 if they still have no removed it? Usually when you deprecate something it is with the intent to remove it in a few versions later.

@anon43302295 thanks. They should have mentioned in the error message that you need to switch from true to false :slight_smile: I just did what the instructions said and switched emulated_hue to emulated_hue_hidden: in customize.yaml and then my switches went offline in my harmony.

Iā€™ll try switching again tonight and change true to false this time. I guess it makes sense given the hidden part of the name but I didnā€™t know what to do based on the error message. I searched for the solution but didnā€™t find the link you posted. Thanks for helping out!

5

Theyā€™ll remove it at somepoint (I think?)ā€¦ I think we will see a lot of changes to the customize section in the future so it may get removed sooner than later.

6

They havenā€™t deprecated any of the features, they deprecated a way of configuring it in favour of a way that was consistent with other components.

1 Like
7

Thanks, I understood that. Still seems strange that 25 releases later it is still deprecated and not yet removed. The point of deprecated features is usually to give folks time to switch to new method, in this case a new tag with the opposite value, before you remove the old method. I am sure they will get around to it some day. :slight_smile: