home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.73k stars 30.85k forks source link

Loqed integration user flow setup missing titles on fields #97048

Closed LordMike closed 1 year ago

LordMike commented 1 year ago

The problem

I'm recreating a Loqed lock, so I tried the user flow to set it up (as opposed to auto discovery), and found the UI confusing and lacking. In the screenshot below, I've selected the Loqed integration, and am now presented with a name and a blank field.

I can guess that the blank field is the API key/token created on their site, but this information isn't present.

image

What version of Home Assistant Core has the issue?

core-2023.7.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

loqed

Link to integration documentation on our website

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

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] commented 1 year ago

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

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

(message by CodeOwnersMention)


loqed documentation loqed source (message by IssueLinks)

mikewoudenberg commented 1 year ago

Hmm curious. I was under the impression that I used a well known key there. I'll create a PR to fix this

mikewoudenberg commented 1 year ago

This has been resolved in the 2023.8 release

mikewoudenberg commented 1 year ago

@home-assistant close