[aiounifi.models.event] Unsupported event key EVT_DM_Lost_Contact

[airbone42]

The problem

I'm trying to connect my UnifFi Dream Machine and my U6 APs using UniFi AP. After setting up the configuration.yaml accordingly I went back to the UI and tried to add the integration, but that gives an error message:

Config flow could not be loaded: {"message":"Invalid handler specified"}

Also in the logfile a message with Unsupported event key EVT_DM_Lost_Contact can be found

What version of Home Assistant Core has the issue?

2022.11.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

UniFi AP

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

device_tracker:
  - platform: unifi_direct
    host: 192.168.1.223
    username: myUsername
    password: myPassword

Anything in the logs that might be useful for us?

2022-12-19 17:49:21.656 WARNING (MainThread) [aiounifi.models.event] Unsupported event key EVT_DM_Connected
2022-12-19 17:49:21.658 WARNING (MainThread) [aiounifi.models.event] Unsupported event {'key': 'EVT_DM_Connected', 'dm': '68:d7:9a:24:2e:f4', 'gw': '68:d7:9a:24:2e:f4', 'dm_name': 'Dream-Machine', 'dm_model': 'UDM', 'dm_displayName': 'Dream-Machine', 'gw_displayName': 'Dream-Machine', 'subsystem': 'lan', 'is_negative': False, 'site_id': '60d715b161a2dc04d45b84a2', 'time': 1671468559845, 'datetime': '2022-12-19T16:49:19Z', 'msg': '68:d7:9a:24:2e:f4 was connected', '_id': '63a0960fd3ce1c052bf1a93e'}
2022-12-19 17:53:06.096 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration unifi_direct: No module named 'homeassistant.components.unifi_direct.config_flow'

Additional information

No response

[home-assistant[bot]]

unifi_direct documentation unifi_direct source

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.