Skip to content

Add checking whether a device supports the button press - #1201

Merged
frenck merged 1 commit into
mainfrom
frenck/local-auth-supported
Oct 4, 2026
Merged

frenck merged 1 commit into
mainfrom
frenck/local-auth-supported

Conversation

@frenck

@frenck frenck commented Oct 4, 2026

Copy link
Copy Markdown
Owner

Proposed Changes

(Describe the changes and rationale behind them)

Adds LaMetricLocalAuth.supported(), to find out whether a device can hand out its API key with a press on its button, without asking for it.

Requesting a challenge shows it on the screen of the device right away, with a minute to press, so it is no way to probe for support. supported() only checks for the web interface of the device that the button flow uses. Nothing shows on the screen.

Verified on two real devices, with GET requests only:

  • sa8 TIME, firmware 3.2.6: the web interface answers with its page (200), supported() returns True.
  • LM 37X8 TIME, firmware 2.3.9: everything asks for credentials (401), supported() returns False.

This lets Home Assistant hide the button option for a device that cannot do it, or recommend it for one that can, as a follow up to home-assistant/core#184197.

Related Issues

(Github link to related issues or pull requests)

Follow up on #1199.

Asking for a challenge shows it on the screen of the device right away,
so it is no way to find out whether a device supports the flow. The new
supported() only checks for the web interface of the device: an sa8 TIME
serves it, an LM 37X8 TIME asks for credentials. Nothing shows on the
screen. Verified on both.
@frenck frenck added the new-feature New features or options. label Oct 4, 2026
@frenck
frenck merged commit 8bdd6c0 into main Oct 4, 2026
32 checks passed
@frenck
frenck deleted the frenck/local-auth-supported branch October 4, 2026 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-feature New features or options.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant