Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deCONZ does not provide correct api_key #2831

Closed
pawlizio opened this issue Jan 11, 2023 · 2 comments
Closed

deCONZ does not provide correct api_key #2831

pawlizio opened this issue Jan 11, 2023 · 2 comments
Labels

Comments

@pawlizio
Copy link

Describe the issue you are experiencing

Seems that deconz addon is querying devicetype = "Home Assistant", but there is no entry for devicetype = "Home Assistant" in deconz database, even though deconz component was already configured. On each HA reboot, the authentification fails, because Supervisor discovery provides a new api_key which will not be authenticated by deconz addon. See: home-assistant/core#70874

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

deCONZ

What is the version of the add-on?

6.17.1

Steps to reproduce the issue

  1. Install deconz addon
  2. Wait till deconz is discovered -> No automatic authentification
  3. Configure deconz, link via Phoscon UI (Settings -> Gateway -> Extended -> Connect App).
  4. Restart Home Assistant
  5. Shortly after restart deconz can be reloaded and authenticated
  6. After some seconds Supervisor discovery provides a discovery_info with a new api_key, which cannot be authenticated. The components needs to be reauthenticated using the Phoscon UI.
    ...

System Health information

No repairs awailable

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

No response

Additional information

No response

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Feb 10, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 17, 2023
@pawlizio
Copy link
Author

Actually this is still open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant