Lots of errors: Updating panasonic_cc sensor took longer than the scheduled update interval

[TheDK]

Good morning,

I noticed that the sensors for power, temperature, etc. had not been updated for ~3days (while the attributes of the climate entity still are?!) and seeing this in the log over 10000 times in less than four days:

2021-08-03 08:53:27 WARNING (MainThread) [homeassistant.components.sensor] Updating panasonic_cc sensor took longer than the scheduled update interval 0:00:30
2021-08-03 08:53:57 WARNING (MainThread) [homeassistant.components.sensor] Updating panasonic_cc sensor took longer than the scheduled update interval 0:00:30
2021-08-03 08:54:27 WARNING (MainThread) [homeassistant.components.sensor] Updating panasonic_cc sensor took longer than the scheduled update interval 0:00:30
2021-08-03 08:54:57 WARNING (MainThread) [homeassistant.components.sensor] Updating panasonic_cc sensor took longer than the scheduled update interval 0:00:30
2021-08-03 08:55:27 WARNING (MainThread) [homeassistant.components.sensor] Updating panasonic_cc sensor took longer than the scheduled update interval 0:00:30

I don't know if the Panasonic cloud service is maxed out or if it's a problem on my side. Anyone else seeing this?

[sockless-coding]

Hi @TheDK, from what I can tell this is an issue with the Panasonic cloud, and it only affects the energy reading (different api call). It seems to occur when the HVAC device is connected to one of their servers and HA is connected to one of the other server. This can even be reproduced in their own app, the result is that the energy and temp graph is blank. One thing you can try is locking the accsmart.panasonic.com to just one ip.

[TheDK]

Hi @sockless-coding and thanks for the quick reply! It appears that this is a problem with all sensors (current power, daily energy and inside / outside temperature, possibly also Nanoe) - at least those stopped working for 4 days ago. But that is in line with your observation in the app.

After a restart it does work again (possibly briefly - will keep an eye on it...). I currently do not have a DNS server that I can change - and I am not quite sure if that would be a good idea depending on the dynamics of AWS IPs.

So best course of action would be to deactivate the other sensors and read inside temp from the attribute of the climateentity to avoid flooding of the log? Just out of curiosity: What do you do in your setup?

[TheDK]

I kept an eye on it and the option to turn on the daily energy sensor led to the integration to fail at setup:

2021-08-09 21:05:55 WARNING (MainThread) [custom_components.panasonic_cc] Failed to setup device: AC ('energyConsumption')

I disabled the option and reloaded the integration - working again (no sensors of course...)

I will look into reading the temperature from the attributes of the climate entity. Pity about the energy readings, but I won't be messing with DNS for this... :)

[gulli1986]

Hi @TheDK, from what I can tell this is an issue with the Panasonic cloud, and it only affects the energy reading (different api call). It seems to occur when the HVAC device is connected to one of their servers and HA is connected to one of the other server. This can even be reproduced in their own app, the result is that the energy and temp graph is blank. One thing you can try is locking the accsmart.panasonic.com to just one ip.

@sockless-coding I was also looking for that explanation, thanks!

What do you mean by locking the "accsmart.panasonic.com" to just one IP? I am using PiHole and can see that HA is quering this address. Do you mean we should block other devices like the HVAC to access this address?

[sockless-coding]

@gulli1986 by locking I meant if you have a router where you can enter DNS settings you can specify what IP should be returned. If I run a DNS lookup on accsmart.panasonic.com I get

Non-authoritative answer:
Name:    e024-alb-rac-web-prd-1578900232.ap-northeast-1.elb.amazonaws.com
Addresses:  54.238.149.15
          54.199.130.225
Aliases:  accsmart.panasonic.com

Then you could pick one of those IPs and lock accsmart.panasonic.com to that.

[TheDK]

Then you could pick one of those IPs and lock accsmart.panasonic.com to that.

...and set a sensor to that DNS lookup so when they change the IP(s) of the service you'll notice and reconfigure your DNS accordingly.

[TheDK]

Btw: I still get tons of errors as the Panasonic Cloud does not seem to be very responsive. I now just filter them out of the log...

[gulli1986]

@sockless-coding , @TheDK , understood, I will give it a try. Would be good to use the energy sensor without being afraid it will fail to start up the integration.