Connection error with Homematic IP

[guigel1]

The problem

Since the migration to 2022.7 this appears in the log :+1:

Logger: homematicip.aio.connection Source: /usr/local/lib/python3.10/site-packages/homematicip/aio/connection.py:182 First occurred: 6 juillet 2022 à 23:59:14 (1 occurrences) Last logged: 6 juillet 2022 à 23:59:14

And then

Logger: homeassistant.components.homematicip_cloud.hap Source: components/homematicip_cloud/hap.py:192 Integration: HomematicIP Cloud (documentation, issues) First occurred: 6 juillet 2022 à 23:59:14 (1 occurrences) Last logged: 6 juillet 2022 à 23:59:14

Error connecting to HomematicIP

What version of Home Assistant Core has the issue?

core-2022.07.0

What was the last working version of Home Assistant Core?

core-2022.06.7

What type of installation are you running?

Home Assistant OS

Integration causing the issue

homematicip_cloud

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Problem converting incoming bytes b'{"events":{"0":{"pushEventType":"DEVICE_CHANGED","device":{"id":"3014F711XXXXXXXXXXXXXXXX","homeId":"36dde09f-fb07-4c26-97a9-ac2e99ac5e67","label":"Toto","lastStatusUpdate":1657145238916,"type":"HEATING_THERMOSTAT","functionalChannels":{"0":{"label":"","deviceId":"3014F711XXXXXXXXXXXXXXXX","index":0,"groupIndex":0,"functionalChannelType":"DEVICE_OPERATIONLOCK","groups":["debb38ef-ae20-4d91-82f0-e6f7135ee2dc"],"unreach":false,"lowBat":false,"routerModuleEnabled":false,"multicastRoutingEnabled":false,"routerModuleSupported":false,"rssiDeviceValue":-73,"rssiPeerValue":null,"configPending":false,"dutyCycle":false,"deviceOverloaded":false,"coProUpdateFailure":false,"coProFaulty":false,"coProRestartNeeded":false,"deviceUndervoltage":false,"deviceOverheated":false,"temperatureOutOfRange":false,"devicePowerFailureDetected":false,"supportedOptionalFeatures":{"IFeatureDeviceParticulateMatterSensorCommunicationError":false,"IFeatureDeviceCoProRestart":false,"IFeatureDeviceOverheated":false,"IOptionalFeatureDutyCycle":true,"IFeatureMulticastRouter":false,"IFeaturePowerShortCircuit":false,"IFeatureDeviceDriveModeError":false,"IFeatureDeviceTemperatureHumiditySensorCommunicationError":false,"IFeatureDeviceDriveError":false,"IFeatureRssiValue":true,"IFeatureBusConfigMismatch":false,"IFeatureDeviceOverloaded":false,"IOptionalFeatureDisplayContrast":false,"IFeatureDeviceIdentify":false,"IOptionalFeatureLowBat":true,"IOptionalFeatureMountingOrientation":false,"IFeatureDeviceTemperatureHumiditySensorError":false,"IFeatureDeviceTemperatureOutOfRange":false,"IOptionalFeatureDeviceErrorLockJammed":false,"IFeatureProfilePeriodLimit":false,"IFeatureDeviceCoProUpdate":false,"IFeatureDevicePowerFailure":false,"IFeatureShortCircuitDataLine":false,"IFeatureDeviceCommunicationError":false,"IFeatureDeviceUndervoltage":false,"IFeatureDeviceParticulateMatterSensorError":false,"IFeatureDeviceCoProError":false},"busConfigMismatch":null,"powerShortCircuit":null,"shortCircuitDataLine":null,"profilePeriodLimitReached":null,"mountingOrientation":null,"temperatureHumiditySensorError":null,"temperatureHumiditySensorCommunicationError":null,"particulateMatterSensorError":null,"particulateMatterSensorCommunicationError":null,"displayContrast":null,"lockJammed":null,"deviceDriveError":null,"deviceDriveModeError":null,"deviceCommunicationError":null,"operationLockActive":false},"1":{"label":"","deviceId":"3014F711XXXXXXXXXXXXXXXX","index":1,"groupIndex":1,"functionalChannelType":"HEATING_THERMOSTAT_CHANNEL","groups":["0b9790fb-8952-4e0c-8456-993e528b0870"],"temperatureOffset":0.0,"valvePosition":1.0,"setPointTemperature":30.0,"valveState":"ADAPTION_DONE","valveActualTemperature":25.6}},"automaticValveAdaptionNeeded":false,"manufacturerCode":1,"oem":"eQ-3","updateState":"UP_TO_DATE","liveUpdateState":"LIVE_UPDATE_NOT_SUPPORTED","firmwareVersion":"2.2.8","firmwareVersionInteger":131592,"availableFirmwareVersion":"2.2.8","serializedGlobalTradeItemNumber":"3014F711XXXXXXXXXXXXXXXX","modelType":"HmIP-eTRV-2","modelId":295,"permanentlyReachable":true,"connectionType":"HMIP_RF"}},"1":{"pushEventType":"GROUP_CHANGED","group":{"id":"debb38ef-ae20-4d91-82f0-e6f7135ee2dc","homeId":"36dde09f-fb07-4c26-97a9-ac2e99ac5e67","metaGroupId":null,"label":"Salon TV","lastStatusUpdate":1657145238916,"unreach":false,"lowBat":false,"dutyCycle":false,"type":"META","channels":[{"deviceId":"3014F711XXXXXXXXXXXXXXXX","channelIndex":0},{"deviceId":"3014F711A0000A1D8997F598","channelIndex":0}],"groups":["0b9790fb-8952-4e0c-8456-993e528b0870"],"configPending":false,"sabotage":null,"incorrectPositioned":null,"groupIcon":""}},"2":{"pushEventType":"GROUP_CHANGED","group":{"id":"0b9790fb-8952-4e0c-8456-993e528b0870","homeId":"36dde09f-fb07-4c26-97a9-ac2e99ac5e67","metaGroupId":"debb38ef-ae20-4d91-82f0-e6f7135ee2dc","label":"Toto","lastStatusUpdate":1657145238916,"unreach":false,"lowBat":false,"dutyCycle":false,"type":"HEATING","channels":[{"deviceId":"3014F711XXXXXXXXXXXXXXXX","channelIndex":1}],"windowOpenTemperature":12.0,"setPointTemperature":30.0,"minTemperature":5.0,"maxTemperature":30.0,"windowState":null,"cooling":null,"partyMode":false,"controlMode":"MANUAL","profiles":{"PROFILE_4":{"profileId":"b4836fea-54dd-464d-9172-66071eeda72b","groupId":"0b9790fb-8952-4e0c-8456-993e528b0870","index":"PROFILE_4","name":"","visible":true,"enabled":false},"PROFILE_3":{"profileId":"dac9d418-445a-478b-b3ba-0a9d5cd081e2","groupId":"0b9790fb-8952-4e0c-8456-993e528b0870","index":"PROFILE_3","name":"","visible":false,"enabled":true},"PROFILE_5":{"profileId":"b3bbc9d6-5d36-4b73-b79b-1708943a9257","groupId":"0b9790fb-8952-4e0c-8456-993e528b0870","index":"PROFILE_5","name":"","visible":false,"enabled":false},"PROFILE_2":{"profileId":"bcd544e2-78af-48e5-8ba8-0aef2f098f45","groupId":"0b9790fb-8952-4e0c-8456-993e528b0870","index":"PROFILE_2","name":"","visible":false,"enabled":true},"PROFILE_6":{"profileId":"9a5d5b60-a3f1-4916-9522-8bb590a15fb3","groupId":"0b9790fb-8952-4e0c-8456-993e528b0870","index":"PROFILE_6","name":"","visible":false,"enabled":false},"PROFILE_1":{"profileId":"fcc85143-8fb3-44f3-9b43-b8d9cd778a2b","groupId":"0b9790fb-8952-4e0c-8456-993e528b0870","index":"PROFILE_1","name":"Pi\xc3\xa8ces \xc3\xa0 vivre","visible":true,"enabled":true}},"activeProfile":"PROFILE_1","boostMode":false,"boostDuration":5,"actualTemperature":null,"humidity":null,"coolingAllowed":false,"coolingIgnored":false,"ecoAllowed":true,"ecoIgnored":false,"controllable":true,"boostAllowed":true,"floorHeatingMode":"FLOOR_HEATING_STANDARD","humidityLimitEnabled":true,"humidityLimitValue":60,"humidityLimiterAlarm":null,"humidityLimitPreEnabled":true,"humidityLimitPreValue":60,"humidityLimiterPreAlarm":null,"externalClockEnabled":false,"externalClockHeatingTemperature":19.0,"externalClockCoolingTemperature":23.0,"valvePosition":1.0,"sabotage":null,"valveSilentModeSupported":true,"valveSilentModeEnabled":false,"lastSetPointReachedTimestamp":1655822389886,"lastSetPointUpdatedTimestamp":1657145238916,"heatingFailureSupported":true,"switchClimateFunction":"THERMOSTAT","supportedOptionalFeatures":{"IOptionalFeatureHumidityLimitPre":false,"IOptionalFeatureSwitchClimateFunction":false},"processing":null,"ventilationState":null}}},"origin":{"originType":"DEVICE","id":"3014F711A0000A1D8997F598"},"accessPointId":"3014F711XXXXXXXXXXXXXXXX","timestamp":1657145238916}'

Additional information

No response

[probot-home-assistant[bot]]

homematicip_cloud documentation homematicip_cloud source _{^{(message by IssueLinks)}}

[premutos888]

Same here.

[guigel1]

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

I'll wait for an update then :P

[cyb3rforce]

Same happened here. Even with the existing alert notification in the documentation I never faced that issue. Now with core-2022.07.0 its coming up with this errors and it also blocked the access in the rest API.

I didnt had the time to check it out, I only saw there were some changes in the last 14 days in alarm_control_panel.py and cover.py.

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

[user45876]

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.

[user45876]

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.

[frankie69ha]

Same here since update to 2022.7.0. I hope for a fast update,

[guigel1]

Luckily it's not heating season here, but clearly it's a big problem :D

[Bat-Maniac]

Same here with core v2022.7.0. Just restored to 2022.6.7 and got no issues so far.

[frenck]

🤚 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

[jaydkay]

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!

[user45876]

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

[Vegas2806]

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.

[ChristophCaina]

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

[user45876]

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.

[guigel1]

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.

[ChristophCaina]

oh sorry then... I did somehow lost track on this ... :-(

[cpohli]

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

[user45876]

Hi @cpohli ,

until you get throtteled: Does ot work? Do state changes reflect in HA? If you switch on a light, does it get shown in HA? XCan you switch a light from HA more than one time? Also, do you see the "Problem converting incoming bytes..." error in your logs?

[K3vb3rt]

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.

[cpohli]

until you get throtteled: Does ot work? Do state changes reflect in HA? If you switch on a light, does it get shown in HA? XCan you switch a light from HA more than one time? Also, do you see the "Problem converting incoming bytes..." error in your logs?

Yes, all seems to work normal until i get throttled again after 30 mins or so. I do not see the "converting" error thouh, just getting "banned" from the REST api...

For the time being, rolling back to core 2022.6.7 solves the problem (for now).

[cpohli]

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.

Perhaps you can revert to core 2022.6.7 as this "solves" the problem for me (at least for now). Also have an eye out here: #74662

[ErikSlevin]

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 ..

[K3vb3rt]

Thanks bud, tried this but since 20 minutes the status is "Processing...". Just have to wait patiently?

[ErikSlevin]

for me it took about 15 min with a Raspberry 4

[redzoro01]

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.

[compoundbow83]

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?

[user45876]

@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.

[compoundbow83]

I get back the right status form the sensors, but after a while I get banned. Now I had to disable the integration first

[kerzenmeister]

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

[jaydkay]

Problem still exists with 2022.7.2.

[cpohli]

A downgrade to 6.7 brings Homematic IP back to normal.

It seems, that the last version working is 2022.6.9. The problems are starting with 2022.7.0 and are persistent up to 2022.7.2 (as stated by @jaydkay and others)

[user45876]

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 ?

[Whippie72]

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

[cpohli]

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

Oh, you're absolutely right! It's my mistake, 2022.6.7 is correct. Somehow along the way of updating to 7.0, 7.1 and 7.2 and always going back to 6.7. i got a little confused ;-)

[frenck]

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.

[user45876]

Unfortunately it is beyond my skills. Anybody who is able and willing to help? I am tagging @SukramJ and @coreGreenberet and hoping not to upset anybody. Could you maybe please have a look? Afaics, the error might give a clue:

"Problem converting incoming bytes b'{"events":{"0":{"pushEventType":"DEVICE_CHANGED","device":{"id":"3014F711XXXXXXXXXXXXXXXX",..."

@frenck Is it also due to the change to python 3.10? you tagged it as 'problem in dependency', do you have an idea?

Sorry, I am really grabbing for straws here :-/

[frenck]

Please don't tag people. We have bots taking care of that when appropriate. When you tag people like that, even if your intentions are good, can come across demanding or entitled.

So, therefor we don't allow for that.

Thanks!

[user45876]

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

[compoundbow83]

Is there a chance that this problem will be solved soon?

[frenck]

@compoundbow83 That question cannot be answered, as said, this is an open source project, we rely on contributions. Nobody can guess when someone takes their spare time to offer/contribute a fix for this.

That said, if you want to help to fix it, please go ahead and feel free to provide PRs for it.

[hahn-th]

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.

[moviele]

This is my error log with core 2022.7, 2022.7.1 and 2022.7.2 installed! Core version 2022.6.7 works fine no errors!

---

Protokolldetails (FEHLER) Logger: homematicip.aio.connection Source: /usr/local/lib/python3.10/site-packages/homematicip/aio/connection.py:182 First occurred: 15:58:21 (6 occurrences) Last logged: 16:01:11

Problem converting incoming bytes b'

[gtawelt]

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

[guigel1]

I had also the ban from the app.

I just deactivate the integration in HA.

[NeoTrace82]

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

[saschaabraham]

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

[hahn-th]

Not yet. Tests are failing

[guevara777]

Lucky to See Progress Here. I will Just wait Till it is fixed. Thank you!

[emontnemery]

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