'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'

[t0bse]

The problem

This error is flooding my Log since a few Versions of Home Assistant, and i can't get rid of it:

2021-05-13 20:42:16 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:42:16 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:42:39 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:42:39 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:45:08 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:45:08 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:49:41 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:49:41 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:51:15 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:54:50 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:54:50 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:57:33 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:57:33 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:57:37 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:57:37 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:57:47 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:57:47 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:58:10 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:58:10 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:59:50 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 20:59:50 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:05:18 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:05:18 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:09:00 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:10:17 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:10:17 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:13:03 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:13:03 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:13:05 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:13:05 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:13:16 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:13:16 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:13:39 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:13:39 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'
2021-05-13 21:14:47 WARNING (MainThread) [homematicip.base.enums] 'ACCESS_CONTROL' isn't a valid option for class 'FunctionalHomeType'

What is version of Home Assistant Core has the issue?

2021.5.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Homematic IP

Link to integration documentation on our website

https://www.home-assistant.io/integrations/homematicip_cloud/

[szatan81]

Got the exact same spam as described above.
Using HmIP-HAP with couple of HmIP-eTRV-2

[schiegg]

Can also confirm this behavior with 2021.2.3, 2021.4.6 as well as 2021.5.5

Additionally the alarm control panel is not recognizing changes.
Other entities monitored such as motion detectors change their state without issues.
Updates sent to alarm control panel via lovelace or automations, such as activating armed_home, get performed although not visualized.

[schiegg]

Somehow the bot isn't notifying @SukramJ about this as it did in other issues within this integration.
I hope its okay to mention you manually. Could you may have a look?

I tried myself yesterday but as I am no python developer, I couldn't fully understand how this code is even working 😄

[SukramJ]

@schiegg That correct. I don't want to be notified!
I no longer use the AP and don't maintain this integration any longer.

I think the warnings from @t0bse are related to the new HmIP-DLD. This requires a new lock related component for the HmIP integration, and that means a lot of work.

To get rid of the log spam you can configure your logger in HA.

Good luck.

[schiegg]

@Hoytron and me found the root of this problem in changes of the HomematicIP Cloud API as also referenced in this issue and already created a pull request which is currently pending for the respective project. As soon as it gets accepted, we will have to update the version of the homematicip dependency in the homeassistant integration accordingly, creating a pull request here.

This also fixes the alarm_control_panel to work again as expected.

[schiegg]

If anyone depends on this functionality before there will be a stable release, PR and so on:

Changing the requirements of the manifest.json to "requirements": ["homematicip==1.0.0.post0.dev23"] should fix the problem temporary. Note that you need to restart homeassistant after that change to load the new library version. Feel free to comment if this destroys any functionality.

[bobcat422]

If anyone depends on this functionality before there will be a stable release, PR and so on:

Changing the requirements of the manifest.json to "requirements": ["homematicip==1.0.0.post0.dev23"] should fix the problem temporary. Note that you need to restart homeassistant after that change to load the new library version. Feel free to comment if this destroys any functionality.

How to modify the manifest.json? I have HA on Synology and no idea where to find this file?! Sry for stupid questions just starting to learn.

[schiegg]

@bobcat422 No stupid question, just the wrong place 😉 In my opinion, this here is for developers contributing while there is a Discord chat room with a broad community to help you with your question. I don't own any Synology device and can't help you with that. If you can access your homeassistant docker container somehow you can manipulate the file inside it. Alternatively you can add a custom_component overriding the original integration, which should be preferred. Please review the documentation for more info about this.

[web-dc]

@schiegg There's now a 1.0.1 Version in HmIP Rest API Repository

[schiegg]

Great job creating a PR for this @web-dc 👍

The new version was published after i asked the code maintainer for it so this was no news to me but thanks for mentioning that 😆
I just hadn't had the possibilities to set up a test environment, following this massive development checklist till today. Now that you already created the PR I think this is kind of obsolete. If I can do anything to support you, feel free to comment.