# Error Panasonic Comfort cloud app

**URL:** <https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935>\
**Category:** Apps\
**Tags:** app\
**Created:** [July 12, 2022, 9:45pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935 "2022-07-12T21:45:07Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![Arnold\_vd\_Linden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnold_vd_linden/32/19336_2.png) [@Arnold\_vd\_Linden](https://community.homey.app/u/Arnold_vd_Linden)\
**Post date:** [January 4, 2023, 3:47pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/81 "2023-01-04T15:47:34Z")

</div>

Just received an update to v1.3.2.  
Hope this will fix this issue because the changelog is

> **1.3.2** 4 jan. 2023  
> Fixed change in panasonic API

---

<div class="post-metadata">

**Author:** ![lumin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lumin/32/28064_2.png) [@lumin](https://community.homey.app/u/lumin)\
**Post date:** [January 4, 2023, 5:09pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/82 "2023-01-04T17:09:35Z")

</div>

Hey guys,

Happy new year!

Panasonic had made a change regarding charsets and also bumping the version of their API. They use two kinds of versioning at their end, which pretty constantly changes. Im not sure about their practices, but i’m sure they have their reasons.

As far as rate limiting go, i have not experienced any. I’m pretty sure the guys at Panasonic found an “excuse” as they were unable to find any other reason for the failures. Looking at the request headers would have made the issue very clear imo.

It is true that the app authenticates on every action made against the API, but that is something that had to be done, as the token provided by Panasonic has an extremely short TTL. Making multiple adjustments to the device would result in token timing out. I have logged in 20-30 times in a row, without any issue. Any rate limiting would have blocked me from doing that. But i will monitor, and please lmk if encountered.

I’m sorry for the late fix (been away for an extended period) and hope it works for you guys as well.

---

<div class="post-metadata">

**Author:** ![James\_Wyatt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/james_wyatt/32/33967_2.png) [@James\_Wyatt](https://community.homey.app/u/James_Wyatt)\
**Post date:** [January 4, 2023, 6:11pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/83 "2023-01-04T18:11:13Z")

</div>

Thanks for all the good work!

I received the update indeed in homey.  
I reset the app  
I can’t connect to the units, they give error 429.

That would that error mean?

---

<div class="post-metadata">

**Author:** ![Robert\_Schmidt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robert_schmidt/32/53755_2.png) [@Robert\_Schmidt](https://community.homey.app/u/Robert_Schmidt)\
**Post date:** [January 4, 2023, 6:49pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/84 "2023-01-04T18:49:31Z")

</div>

> [@lumin](#):
>
> As far as rate limiting go, i have not experienced any. I’m pretty sure the guys at Panasonic found an “excuse” as they were unable to find any other reason for the failures.

Good to see you back @lumin!

Rate limiting was my personal conclusion seeing authentication requests failing with HTTP status 429 (“too many requests”). Once I disabled your app, this stopped happening after a while.

Before I added re-authentication logic, my app ran for at least a day on the same token. Maybe Panasonic has improved the TTL?

---

<div class="post-metadata">

**Author:** ![Martijn\_C](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_c/32/39993_2.png) [@Martijn\_C](https://community.homey.app/u/Martijn_C)\
**Post date:** [January 4, 2023, 6:58pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/85 "2023-01-04T18:58:20Z")

</div>

Same here; error 429. @lumin Seems like there is an issue with the requests.

---

<div class="post-metadata">

**Author:** ![lumin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lumin/32/28064_2.png) [@lumin](https://community.homey.app/u/lumin)\
**Post date:** [January 4, 2023, 7:15pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/86 "2023-01-04T19:15:33Z")

</div>

Hmmm. Weird. Working good with my device 🙈 do you guys by chance have multiple devices?

Allright, let med add some new logic for auth, and lets see if panasonic has improved their handling of tokens 👍

---

<div class="post-metadata">

**Author:** ![Martijn\_C](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_c/32/39993_2.png) [@Martijn\_C](https://community.homey.app/u/Martijn_C)\
**Post date:** [January 4, 2023, 7:21pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/87 "2023-01-04T19:21:15Z")

</div>

I think that might be it. I have three units. But even without sending a command I immediately get the error.

---

<div class="post-metadata">

**Author:** ![James\_Wyatt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/james_wyatt/32/33967_2.png) [@James\_Wyatt](https://community.homey.app/u/James_Wyatt)\
**Post date:** [January 4, 2023, 7:35pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/88 "2023-01-04T19:35:35Z")

</div>

I have 4 units

---

<div class="post-metadata">

**Author:** ![Robert\_Schmidt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robert_schmidt/32/53755_2.png) [@Robert\_Schmidt](https://community.homey.app/u/Robert_Schmidt)\
**Post date:** [January 4, 2023, 7:35pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/89 "2023-01-04T19:35:59Z")

</div>

Guys, once you receive HTTP status 429, your credentials are blocked from authenticating with Panasonic servers.

They will start working again after a while (at most 24 hours, in my experience).

There’s nothing you, @lumin or his app can do to circumvent this - except using other credentials.

The number of units is probably relevant in that more requests will be made (but I also have only 1 device).

---

<div class="post-metadata">

**Author:** ![James\_Wyatt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/james_wyatt/32/33967_2.png) [@James\_Wyatt](https://community.homey.app/u/James_Wyatt)\
**Post date:** [January 4, 2023, 7:43pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/90 "2023-01-04T19:43:26Z")

</div>

Do you know how the relation is between account, Panasonic Id, devices?

As I understand it: account is a Panasonic Id. And a device can be linked to multiple accounts.

Or…

Devices are linked to a Panasonic Id. And an Id can be linked to multiple accounts.

---

<div class="post-metadata">

**Author:** ![Robert\_Schmidt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robert_schmidt/32/53755_2.png) [@Robert\_Schmidt](https://community.homey.app/u/Robert_Schmidt)\
**Post date:** [January 4, 2023, 7:49pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/91 "2023-01-04T19:49:38Z")

</div>

A device is linked to multiple Panasonic IDs, but only one ID (the first?) can be the device owner. (So, your first option.)

Why are you asking about “account”? If you need to use the term, I’d say the Panasonic ID identifies an account.

---

<div class="post-metadata">

**Author:** ![Arnold\_vd\_Linden](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/arnold_vd_linden/32/19336_2.png) [@Arnold\_vd\_Linden](https://community.homey.app/u/Arnold_vd_Linden)\
**Post date:** [January 4, 2023, 7:53pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/92 "2023-01-04T19:53:06Z")

</div>

Same here.  
After the update this afternoon it worked for me with 2 devices.  
Just did a app reset and also get a error 429 and exclamation mark in de device tile.

---

<div class="post-metadata">

**Author:** ![Martijn\_C](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_c/32/39993_2.png) [@Martijn\_C](https://community.homey.app/u/Martijn_C)\
**Post date:** [January 4, 2023, 9:09pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/93 "2023-01-04T21:09:45Z")

</div>

Sure, but that still means it’s the app that’s doing it. I had no issues before. So, I can wait but then the app probably will make too many requests again.

---

<div class="post-metadata">

**Author:** ![James\_Wyatt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/james_wyatt/32/33967_2.png) [@James\_Wyatt](https://community.homey.app/u/James_Wyatt)\
**Post date:** [January 4, 2023, 9:20pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/94 "2023-01-04T21:20:40Z")

</div>

You are right, I should call it Panasonic Id.

So, is it correct that with two Panasonic ID’s you can maintain with one ID a working Panasonic comfort Cloud app (without the internal server error) .

And the other account you use for homey, (getting the 429 error).

At least with this setup you can still control the devices via the original app, correct?

---

<div class="post-metadata">

**Author:** ![Robert\_Schmidt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robert_schmidt/32/53755_2.png) [@Robert\_Schmidt](https://community.homey.app/u/Robert_Schmidt)\
**Post date:** [January 4, 2023, 9:41pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/95 "2023-01-04T21:41:04Z")

</div>

> [@James\_Wyatt](#):
>
> At least with this setup you can still control the devices via the original app, correct?

Exactly, that’s worked for me since this started happening. I’ve kept the owner ID in Android (crucial for the ability to approve device access), and a “guest” ID for Homey.

---

<div class="post-metadata">

**Author:** ![James\_Wyatt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/james_wyatt/32/33967_2.png) [@James\_Wyatt](https://community.homey.app/u/James_Wyatt)\
**Post date:** [January 5, 2023, 11:08am UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/96 "2023-01-05T11:08:08Z")

</div>

Fyi, I deleted the homey Panasonic app. 12 hours ago. And now I can login into the original Panasonic cc app again. (With the same Panasonic Id as I used in homey)

Confirming the hypothesis discussed above. That the homey cc app is disrupting the used Panasonic Id.

---

<div class="post-metadata">

**Author:** ![James\_Wyatt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/james_wyatt/32/33967_2.png) [@James\_Wyatt](https://community.homey.app/u/James_Wyatt)\
**Post date:** [January 6, 2023, 8:03pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/97 "2023-01-06T20:03:00Z")

</div>

I created a second Panasonic id in the Panasonic cc app. I added just 1 of my 4 devices.

On homey I downloaded the PCC app again.  
First I added my second Panasonic id in the app settings.

Then I added a new airconditioner.

I get the error message:  
Sqlite\_contraint: not null  
Constraint failed: device data.

What might I be doing wrong here?

> > Edit1 Oops used wrong password. Trying again.  
> > Edit 2 yes, it works, added 1 device in homey. Now let’s test if this is a stable setup the next 24 hours.

---

<div class="post-metadata">

**Author:** ![James\_Wyatt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/james_wyatt/32/33967_2.png) [@James\_Wyatt](https://community.homey.app/u/James_Wyatt)\
**Post date:** [January 7, 2023, 11:43pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/98 "2023-01-07T23:43:54Z")

</div>

24 hours later, the one device I added in homey gets a 429 error again.

Remarkable is, that I do not get the internal server error when I use the homey Panasonic id, when logging in to the original pcc app.

---

<div class="post-metadata">

**Author:** ![GertCorstjens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gertcorstjens/32/18031_2.png) [@GertCorstjens](https://community.homey.app/u/GertCorstjens)\
**Post date:** [January 13, 2023, 8:09pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/99 "2023-01-13T20:09:34Z")

</div>

Still no update on this? It shouldn’t be so difficult to (re)use the token instead of logging in every time again?

---

<div class="post-metadata">

**Author:** ![Robert\_Schmidt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robert_schmidt/32/53755_2.png) [@Robert\_Schmidt](https://community.homey.app/u/Robert_Schmidt)\
**Post date:** [January 16, 2023, 2:46pm UTC](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935/100 "2023-01-16T14:46:51Z")

</div>

For what it’s worth, [my alternative app is now available on Homey Community Store](https://store.homey.community/app/net.schmidt-cisternas.pcc-alt).  
Technically, this is the same as installing it from the repo using the SDK, it’s just more convenient if you’re not a developer. (Please do not ask me or this thread about HCS.)

[Previous page](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935.md?page=4)

[Next page](https://community.homey.app/t/error-panasonic-comfort-cloud-app/65935.md?page=6)
