core icon indicating copy to clipboard operation
core copied to clipboard

Already configured. Only a single configuration possible.

Open ghost opened this issue 1 year ago • 5 comments

The problem

How can I add another account? Unfortunately, I have two accounts in my household. Unfortunately, this cannot be avoided. How can the problem be solved? So that I can use two accounts. Thanks

What version of Home Assistant Core has the issue?

core-2023.11.2

What was the last working version of Home Assistant Core?

supervisor-2023.11.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Only a single configuration possible.

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

ghost avatar Nov 21 '23 13:11 ghost

Hi, any details ? Log ?

chemelli74 avatar Nov 21 '23 20:11 chemelli74

Already configured. Only a single configuration possible.

image

ghost avatar Nov 21 '23 22:11 ghost

Hey there @markperdue, @webdjoe, @thegardenmonkey, mind taking a look at this issue as it has been labeled with an integration (vesync) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of vesync can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign vesync Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


vesync documentation vesync source (message by IssueLinks)

home-assistant[bot] avatar Nov 22 '23 08:11 home-assistant[bot]

As far as I understand it, it is not possible to use multiple accounts with the integration. However, levoit/vesync offers the ability to share devices. If you go to the settings of any device in the vesync app you will find "share device" where you can share device control to another account.

Keep in mind that you will have to reset the integration because new devices will not sync after initial connection as far as I am aware.

MrGamy avatar Dec 10 '23 00:12 MrGamy

Is it possible to use multiple of the same Govee products with this integration? For example I have two H6087’s however when I add the integration, only one of them is found and thereafter I cannot add anymore with the error message: “ Already configured. Only a single configuration possible”

Nyctobello avatar Feb 17 '24 00:02 Nyctobello

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.

Hi, seem to have the same problem with the 'single configuration' but my issue is due to me having to do a factory setting on my pair of Sonos Era100s due to connections issues. Having got the speakers configured (with latest Sonos iOS app) they weren't recognised by the HA Sonos integration, on reinstalling I have the 'single configuration' issue. Anyway around this? Thanks.

haydes1956 avatar May 17 '24 04:05 haydes1956

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.