You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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:
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
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: