Jimmy Everling

@alexpb123 Hi, the error message indicates that the credentials you provided are wrong.

It might be some caching going on... though the authentication is very finicky, Panasonic doesn't really support 3rd party access like this integration so they have blocked the OAuth callback...

@jeroenvdd and what error are you getting? You might have to enable the debug logging in the configuration.yaml by adding ```yaml logger: default: info logs: custom_components.panasonic_cc: debug ``` If it's...

@antunespa Can you enable debug logging @miksen You need to update the integration, you are running an old version

@antunespa No you can set the log level of any integration in the configuration.yaml By adding/editing the `logger` section ``` logger: logs: custom_components.panasonic_cc: debug ```

@antunespa you have to click `load full logs` to see all the debug messages They should look like `DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Starting Session`

@antunespa, and the credentials work in the app? And MFA is configured pref with SMS option. It seems to authenticate all the way until getting the client id and then...

I've added better feature support checks in v1.1.0 so only the relevant modes should be available.

Hi @DarrenPIngram, The Panasonic air cons usually show up as Wistron Neweb Corporation (MAC: b8:b7:f1...) But nothing interesting is open on the device itself, there is no local access... all...

I just did a clean install of Home Assistant 2025.10.2 + HACS, I had no issues adding the integration and starting it. Only issue I found was selecting energy sensors...