ha-tahoma: Error fetching device events data: Invalid event listener id

Did you read the instructions?

I have read the README, including the advanced debugging section.

The problem

The latest version of the Overkiz integration seems to have an issue with unique IDs. In my case this causes an automation script to fail. The individual screens can be manipulated without an issue.

What version of this integration (ha-tahoma) has the issue?

2.5.0

What version of Home Assistant Core has the issue?

core-2021.9.6

Which gateway / hub do you use?

Somfy TaHoma

Device model

No response

Home Assistant log

Logger: custom_components.tahoma
Source: helpers/update_coordinator.py:219
Integration: Overkiz (by Somfy)
First occurred: 18:52:16 (1 occurrences)
Last logged: 18:52:16

Error fetching device events data: Invalid event listener id : 23735bb8-ac10-3e01-7473-4d3599bd1989

Additional information

Logger: homeassistant.components.scene Source: helpers/entity_platform.py:566 Integration: Scène (documentation, issues) First occurred: 18:52:17 (3 occurrences) Last logged: 18:52:17

Platform tahoma does not generate unique IDs. ID 1fb57201-c007-4f04-875f-f5eabd8806b8 already exists - ignoring scene.terrace_xyz Platform tahoma does not generate unique IDs. ID 9e33fdd6-4827-4d6b-a667-4a44e15369fb already exists - ignoring scene.terrace_abc Platform tahoma does not generate unique IDs. ID b41d5241-c38b-4b19-a995-ac8fe1f05099 already exists - ignoring scene.terrace_efg

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 15 (7 by maintainers)

Most upvoted comments

@Wiggum127 maybe good to keep this issue for Error fetching device events data: Invalid event listener id and to create a new issue for the issue you mention. Currently there is not enough information and it is pretty unclear. Especially since you mention you are not using the cover._2 entities, while you mentioned before that in your automation it gives that error. If you can share some logs and your automations YAML in a new issue, we could have a look, but it is probably a wontfix since this is no priority at the moment. Only when it happens more often with the latest version.

iMicknl on Sep 30, 2021