core: Connection error with Homematic IP

I have fixed it and all tests passed. Locally @gtawelt and me tested it against 3.10. Now the owner @coreGreenberet has to merge my pullrequest.

1.0.4 with the PR is released

🤚 I have the same issue! 👇 Read below

Hi there! Sorry to read you are experiencing the same issue as more people here. Nobody likes having issues 😞

Finding an issue on a GitHub issue tracker that matches your problem is kinda nice: At least you know you are not alone. So, let’s leave a commit with: “Yeah, I have the same issue”, or “+1!!!”. 🚫 No!

Please do not create “I have the same issue” comments!

Not just this issue or this project, but anywhere on GitHub or any issue tracker on the internet even. It doesn’t add to triaging the issue. It only generates noise when reading / triaging the case.

What to do instead?

Instead, go to the top of the issue, and add a 👍 emoji reaction. That way, we can still see that you (and how many others) experience this issue while keeping the issue threads nice and clean.

Thanks! ❤️

…/Frenck

Problem still exists with 2022.7.2.

Special thanks to @hahn-th for taking this up and fixing it! Many of us simply rely on knowledgeable contributors to keep their systems running. Thanks again and stay healthy!

Problem still exists with 2022.7.1. A downgrade to 6.7 brings Homematic IP back to normal.

I was getting the message in my HMIP App “Throttling REST active. Due to an unusually high number of accesses, further server communication is temporarily suspended.”

After reverting to Home Assistant Core 2022.6.7 everything works as normal and no log entries so far.

Edit: Updating core to 2022.7.x once more - the issue arises again within half an hour, starting with the “Throttling REST active” message in the HMIP app.

So i would expect an issue with 2022.7.0 and 2022.7.1 as i can “solve” the problem by just switching the core back.

Upon further inspection of my logs i got this:

Logger: homeassistant.components.homematicip_cloud.hap
Source: components/homematicip_cloud/hap.py:192
Integration: HomematicIP Cloud ([documentation](https://www.home-assistant.io/integrations/homematicip_cloud), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+homematicip_cloud%22))
First occurred: 10:56:49 (9 occurrences)
Last logged: 11:01:06

    Error connecting to HomematicIP with HAP xxx. Retrying in 16 seconds
    Error connecting to HomematicIP with HAP xxx. Retrying in 32 seconds
    Error connecting to HomematicIP with HAP xxx. Retrying in 64 seconds
    Error connecting to HomematicIP with HAP xxx. Retrying in 128 seconds
    Error connecting to HomematicIP with HAP xxx. Retrying in 256 seconds

I had not much knowledge about it. But it was fun to learn 😃 You’re welcome

Just been blacklisted by homematic for too many connection (REST).

I’ll wait for an update then 😛

So, if i read the bump above correctly, this should be inherited in 2022.7.4. Thank you very much for your effort!

The problem in the library is fixed, now we have to wait for the version of the library

https://github.com/coreGreenberet/homematicip-rest-api/issues/443

Same here, same log entry. I am, however, not blacklisted and rolling back to 2022.6.7 instantly makes it work again (so not being blacklisted). I mentioned it here ( https://github.com/home-assistant/core/issues/74241 ) as well.

I am currently try to fix it. But first of all i have to learn a lot about dev containers, python and the home assistant development environment.

I can confirm, that since the update to 2022.7.4 everything works as expected again. No more bans from the REST API.

There was one error in the logs "Error connecting to HomematicIP with HAP xxx. Retrying in 1 seconds", but that seemed to be a one timer and all is shiny so far.

Thank you again! 😃

Not yet. Tests are failing

Test need to be Updated, Test wait for respond in form “on_message(msg.decode())” but after fix it gets “on_message(self, msg.decode())” style The fix is working flawless

Can confirm that it is working (simply edited the file to test it, however this is not ‘the way’, as it might get replaced. I do not recommend others to do so but simply wait).

I restored from the core only backup which was made prior to the upgrade.

@frenck Frenck, may I kindly ask what the usual workflow from here on is? Can we do anything else to help debugging? It is easy to reproduce (which is a good thing).

@compoundbow83 Besides from getting blocked after some time, does it work from HA? When you change a switch in hardware or the hmip app, does it get reflected into HA? Do you have the logfile entry ‘Problem converting incoming bytes’?

I am seeing two separate symptoms here:

• OP @guigel1 and me (and others) are unable to control hmip, state changes do not get reflected into HA from hmip and a logfile entry ‘Problem converting incoming bytes’ - i never got banned but maybe I just never waited long enough. I am having a quite extensive hmip setup with many different devices (60+).

• others say that they can control hmip entities fine from HA and state changes get reflected but they get banned after a while

For new participants in this issue, can you maybe check for that? If state changes get reflected, what is in the log and if you get banned.

I have the same issue here. Updating from HA 2022.6.7 to 2022.7.1 caused blocking by HomaticIP Cloud because of to many accesses to their cloud. Disabling the HomaticIP integration in HA allows access again via HomaticIP app after 15 minutes. Enabling the integration in HA immediately causes that blocking with an error message in the app again. Setting my Homeassistant VM back to HA 2022.6.7 solves the issue and all works fine. There are to many access to the HomematicIP Cloud. I guess the scan_intevall maybe every second or so. It might be a good idea to make it configurable, so that users can adjust it themselves.

The issue described in the OP is clearly related to 2022.7.0. I can ‘switch it on and off’ (the issue) by changing between 2022.6 and 2022.7 in minutes. Also, I am not blocked. From your log I can also not see the relevant error (“Problem converting incoming bytes b’…”).

It seems that it might lead to being blocked when you leave it on 2022.7 for some time.

I am, however, not blacklisted and rolling back to 2022.6.7 instantly makes it work again (so not being blacklisted).

@user45876: Can you explain in a few words HOW you rolled back to the previous version? Did you restore from a backup?

In the comments of the new HA release the following command was mentioned, avoiding restoring from a backup:

ha core update --version 2022.6.7

Thank you!

Disabled the integration for now to hopefully got unblocked on Homeatics API

When this had happened to me in the past, I have simply forced a change in my ip-address (in the router) - depending on your internet connection, this might work. I will also ask EQ3 (company in germany behint hmip) nicely about it to try making them aware of the issue.

I failed to find a possibility to buy @hahn-th a coffee (or a beer 😉 ). Would you mind sharing a possibility, dear hahn-th? This is not about paying but simply saying thanks, no strings attached. What I would do in real life as well.

for me it took about 15 min with a Raspberry 4

If you really think you have to do it. https://ko-fi.com/hahnth But it’s really not necessary:

reverting the container image back to 2022.6.7 fixes it for now. so i don’t get banned in the app

https://github.com/hahn-th/homematicip-rest-api/commit/59cfa2215a9c442205bb9559407076cdefa639f8

I have the same issue since this night. Only deactivating the Homematic IP integration removes the blocking.

Is there really no what to change the scan_intervall?

I’ve got the same issue and I’m no longer able to contact my devices over HA, nor HMIP-App. Had to deactivate the Integration in HA.

Use the SSH AddOn: ha core update --version 2022.6.7

make an Downgrade and after this skipped the 2022.7.x Update …

this seems not to be related to an 2022.07 specific problem. I’m getting this log event also while still using 2022.06.07

Logger: homeassistant.components.homematicip_cloud.hap
Source: components/homematicip_cloud/hap.py:192
Integration: HomematicIP Cloud ([documentation](https://www.home-assistant.io/integrations/homematicip_cloud), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+homematicip_cloud%22))
First occurred: 11:25:46 (1 occurrences)
Last logged: 11:25:46
Error connecting to HomematicIP with HAP 3014F711A00003D8A990ED40. Retrying in 2 seconds

I’ve observed the issue frequently - so it might be, that there was a change on the side on Homematic Cloud Poll which is causing this issue. As mentioned in the integration, a “blacklisting” can always happen due to the cloud poll

Hello,

It’s clearly not the same : I had also sometimes these errors, it seems that the problem is related to the Problem converting incoming bytes b which is a new issue.

@chrizzlibaer Watch 2022.7.4

https://www.home-assistant.io/blog/2022/07/06/release-20227/#release-202274---july-13

Thanks. Must have overread. 😁

@chrizzlibaer Watch 2022.7.4

https://www.home-assistant.io/blog/2022/07/06/release-20227/#release-202274---july-13

Would it be an alternative to use this custom instead of the native integration?

No, unfortunately not. This custom integration is for the use with a CCU or another local Hub, not for the HMIP Cloud.

Since we have a fair amount of homematicip users here, I’ll take the opportunity to ask if any of you have one of the supported weather sensors and can confirm if the weather sensor reports wind speed in km/h? Please add a comment here: https://github.com/home-assistant/core/pull/74385

Sorry. I do not want to be demanding or appear entitled. Sorry Frenck, Sukram and coreGreenberet, no intention to bug you.

Frenck, may I kindly ask what the usual workflow from here on is?

Sure! This is an open source project. Anyone that knows how to fix this, and wants to fix this can open up a pull request to fix it. This project relies on contributions.

Just to be sure, there is no 2022.6.9 release afaik? 2022.6.7 was the last after 2022.7.0b0.

2022.6.7

Just to be sure, there is no 2022.6.9 release afaik? 2022.6.7 was the last after 2022.7.0b0.

Everybody in this thread made his thumbs up 👍 on the first post of @guigel1 ?

oh sorry then… I did somehow lost track on this … 😦

Hi i have the problem with the Homematic app Web socket throttling active

Due to an unusually high number of server accesses through your Homematic IP installation, further server communication is temporarily blocked.