Closed FairSSL closed 1 month ago
Hi. I have 6 AC’s and I just have the same error today :(
I have 1 AC and since this morning it is no longer working for me, same error HTTP 429
Just checked my HA log, and since 2 am local time the integration gets a 503 every 5 minutes and it appears that the 503 is retried several times (?). So seeing this I can understand the 429
Same for me. So something change this night at panasonic side
All my AC's stop to work in HA today (but the panasonic app works) so all my automation didn't work this morning and woke up in a polar cold :(
I deactivate the plug in in HA and I hope a fix :(
Same issue here with 5 ACs. I disabled automations. the panasonic app seems to be working.
Same here with 3 ACs. Panasonic app is still working.
To everybody , did you try to reconnect the plug in or not ? I disabled it and I plan to wait 48h before trying again
Same situation here: 3 ACs, App Ok, remote OK, Home Assistant returns 42901 error since last night, reloaded plug and whole server and nada. Last known working was 23.00 - 10. dec.2023 (Rome) switched of by automation.
hi, Same problem today, Panasonic App works
Try logout from Panasonic app and login again - can you login? I have error : Suspicious activity and account blocked for 24h.
I'm afraid to try because if the app bans me even for 24 hours I won't be able to manage my heaters (unless I find the battery and remote control) :-)
I suspect that if you have a ban, they will log you out right away. I had it too - that it did not work through the API, in the application it worked for a while and then ban for 24h. So better find battery and remote ;)
OK, the ban on the account is lifted after 24 hours, You can then use the account in the app, but NOT in HA, I get '''pcomfortcloud.session.ResponseError: Invalid response, status code: 500 - Data: {"code":5001,"message":"DB system error due to db system"} """ The account is not banned and is still usable via the app. Suspect for as long as I dont force the code 500 I will not be banned.
Hi, This morning I just reloaded the Panasonic integration on HA and it works again. hoping it holds
They blocked my account again for 24 hours due to incorrect login attempts. 😓
May be solved by #152 if we could disable polling.
Hi there! This issue has been marked as stale due to inactivity. If you believe this is still relevant, please let us know. Otherwise, it will be closed soon.
This issue has been automatically closed due to inactivity. If you still need help, feel free to reopen or create a new issue. Thank you!
Hi,
After installing in HA thru HACS and entering a login for Panasonic comfort cloud, all my AC's (3 locations) are visible and give data to HA. Interaction with the AC is possible, I can turn it on-off, etc. I see temperature. All seems ok.
After 2-3 interactions with the AC, I get errors and I am unable to use or access the AC's thru HA but also get blocked/logged out in the app. Note the app was not open or active at this point, I have also tried logging out of the app first to avoid both interacting at the same time, it makes no difference, the account with multiple AC's gets locked after a little while (<1 hour).
Having tried to research the errors I find other people making interaction with this API service, experiencing this if they have more than one AC in the account and it seems something is triggering Panasonics systems that there is too many hits within a certain amount of time and they then block the account for x number of hours before opening again. But without more AC's it becomes difficult for the developer to test/experience.
In my case my account had 3 locations with a total of 10 AC's, I tried removing 2, it did not help. I tried disabling all but two, it did not help.
I then found some people solved the problem for a similair script for Homey by making a new account and giving access only to a few AC's for this account and using it only to automate. I have created an account with 2 AC's in now. But when I connect this account, it shows me that it found the 8 AC's from the previous account. Most likely something in configuration or cache is not removed when deleting the hub?
To be clear just like in the other threads I have found with people having this problem, the mobile app can interact without any problems, including with 10 AC's and even with two phones active on the same app and account. It is only when using the scripts and this component that after 2-3 interactions everything is logged out and blocked for hours before being restored.
I have tried uninstalling, installing, deleting, etc. multiple times it makes no difference, the new account with access to only 2 AC's (confirmed in the app), when I connect it in HA hub, it shows 8 AC's from the previous account that is no longer connected.
I even tried connecting the old primary account, then adding a secondary account as the next hub, thinking I would disable or delete the first after, but when connecting the second I get an error, possibly due to being the same AC ids'?
I can possibly solve this myself, if you help me with information on how I can add the secondary account, without it getting mixed in the old data, i.e. how do I remove the old data when uninstalling the component is not enough. As I think the secondary account will not get locked out, as it only has two AC's. I can then add a third account for the next two, etc.
If anyone knows how to remove the cached information let me know.
Alternatively if there is a way to test limiting how many calls of certain types or just in general that are made within x time, we can test what triggers it and what does not?
I am happy to do more debugging, including I can do tests directly on the code or with remote work. I do normally work with programming, but I don't normallyt work in Python or Home Assistant, so my knowledge there is not enough to fix it without help/tips.
Thank you. Regards Sole
Using HA Core OS Core 2023.11.3 Supervisor 2023.11.6
I see errors getting http status code 429 I get messages saying suspicious acitivity detected from Panasonic Account blocked in the app
A few logged errors to choose from: