Jimmy Everling

@codyc1515 that device seems to have something called nanoe-g, how does it look in the CFC app? Does it say Nanoe-G or Nanoe-X where you activate it?

Hmm, that's completely different from how it works with the nanoe-x... 

Well, I added a feature check so the nanoe switch only get set to available if the devices report the feature as available... Guess I could use the devicetype and...

v1.1.9 has a config option to force enable the Nanoe switch

Does the api nanoe value change if you activate nanoe using the remote? 0 is unavailable 1 is off 3 is unknown, haven't seen any ref to it in CFC...

@BeckerDbgen your devices are reporting nanoe feature as True, but deviceNanoe as 0. If possible, could I get a `[custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/...` log entry where Nanoe is off and...

I did some testing, it seems that they changed some things... the `nanoe` feature flag is now controllable from the device settings in CFC and the `deviceNanoe` value indicates if...

Removing it is not a good option, this will cause a broken sensor to appear. A better way is to change the registry to disabled & hidden depending on if...

It will look like this for everyone that doesn't have nanoe support and have had the integration:  

Setting the registry to disabled & hidden would result in the following:   The reason I didn't implemented this for EcoNavi was I wanted to have some feedback if...