From 41bde936f9d0cea03cbfa71845888da06ff0ccfd Mon Sep 17 00:00:00 2001 From: "Mr. Bubbles" Date: Thu, 20 Jun 2024 10:03:57 +0200 Subject: [PATCH] Add config flow to One-Time Password (OTP) integration (#33031) --- source/_integrations/otp.markdown | 25 ++----------------------- 1 file changed, 2 insertions(+), 23 deletions(-) diff --git a/source/_integrations/otp.markdown b/source/_integrations/otp.markdown index 9954dedf775..7afe598d1df 100644 --- a/source/_integrations/otp.markdown +++ b/source/_integrations/otp.markdown @@ -10,6 +10,7 @@ ha_quality_scale: internal ha_domain: otp ha_platforms: - sensor +ha_config_flow: true ha_integration_type: integration related: - docs: /docs/configuration/ @@ -18,29 +19,7 @@ related: The `otp` {% term integration %} generates One-Time Passwords according to [RFC6238](https://tools.ietf.org/html/rfc6238) that is compatible with most OTP generators available, including Google Authenticator. You can use this when building custom security solutions and want to use "rolling codes", that change every 30 seconds. -## Configuration - -To enable the OTP {% term integration %}, add the following lines to your {% term "`configuration.yaml`" %} file. -{% include integrations/restart_ha_after_config_inclusion.md %} - -```yaml -# Example configuration.yaml entry -sensor: - - platform: otp - token: SHARED_SECRET_TOKEN -``` - -{% configuration %} -name: - description: Name of the sensor to use in the frontend. - required: false - default: OTP Sensor - type: string -token: - description: The shared secret you use in your OTP generator (e.g., Google Authenticator on your phone). - required: true - type: string -{% endconfiguration %} +{% include integrations/config_flow.md %} ## Generating a token