Honeywell TCC - Inability to Update Username / Only Password

[polskikrol]

The problem

Trying to change the email address for my Honeywell TCC, but cannot find a way to do this via the GUI nor config files. Should be an option via the integration GUI.

What version of Home Assistant Core has the issue?

2023.4.6

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

Honeywell TCC

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

[home-assistant[bot]]

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

Code owner commands

Code owners of `honeywell` 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 honeywell` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

honeywell documentation honeywell source _{^{(message by IssueLinks)}}

[mkmer]

If you need to change the user name, remove the integration and re-add it. I was told this is "normal" behavior for HA when I added the reauth flow.

[polskikrol]

Not all integrations work this way. You should be able to update credentials, including a username/email. Having this possible in the GUI would be very helpful.

On Mon, Jul 17, 2023 at 9:38 AM mkmer @.***> wrote:

If you need to change the user name, remove the integration and re-add it. I was told this is "normal" behavior for HA when I added the reauth flow.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/92896#issuecomment-1638165229, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKAGRDBBG3TH3IUK777W7B3XQU55VANCNFSM6AAAAAAX435DGQ . You are receiving this because you authored the thread.Message ID: @.***>

[joostlek]

When you set up an integration, devices and configuration are made for your account (or device), also things like unique ids. When you want to change that, you would need to change every reference to that old account and add it again. And that can become a very fragile part of the application. (What if some devices don't remove correctly, or if your references don't change) You would end up with an integration with half account A and half account B. So with this in mind, it's always consistent to remove and re-add it again.

[mkmer]

Turns out the username is not part of the unique ID, changing will not pose an issue for this integration.

[polskikrol]

Excellent news. Pretty sure I resolved this myself by modifying the underlying json file where the username is stored. The use case I have is that for testing, I use one email address. However, for home automation, I use another email address. With many migrating from cable to fiber in the next few years, there may be additional email changes for individuals. So having the ability to update an email address for an integration, generally the username for login, is a good idea. In many cases, the actual 3rd party, Honeywell lets you update the email address via the web GUI, Airthings requires a support request and support does it for you, and Ecobee just doesnt appear to support it. Better to be able to do this via the GUI than having to muck around with underlying files ;)

On Tue, Jul 18, 2023 at 10:21 AM mkmer @.***> wrote:

Turns out the username is not part of the unique ID, changing will not pose an issue for this integration.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/92896#issuecomment-1640323985, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKAGRDDLWWWE7PIGXQFRZLLXQ2LWVANCNFSM6AAAAAAX435DGQ . You are receiving this because you authored the thread.Message ID: @.***>