original_docstring: 
      Wiser uses config flow for configuration.
      But, a "wiser:" entry in configuration.yaml will trigger an import flow
      if a config entry doesn't already exist. If it exists, the import
      flow will attempt to import it and create a config entry, to assist users
      migrating from the old wiser component. Otherwise, the user will have to
      continue setting up the integration via the config flow.
      
docstring: Wiser uses config flow for configuration.
  But, a "wiser:" entry in configuration.yaml will trigger an import flow
  if a config entry doesn't already exist. If it exists, the import
  flow will attempt to import it and create a config entry, to assist users
  migrating from the old wiser component. Otherwise, the user will have to
  continue setting up the integration via the config flow.
docstring_tokens: Wiser uses config flow for configuration . But a " wiser : " entry in configuration . yaml will trigger an import flow if a config entry doesn ' t already exist . If it exists the import flow will attempt to import it and create a config entry to assist users migrating from the old wiser component . Otherwise the user will have to continue setting up the integration via the config flow .
code: async def async_setup(hass, config):
      """
      Wiser uses config flow for configuration.
      But, a "wiser:" entry in configuration.yaml will trigger an import flow
      if a config entry doesn't already exist. If it exists, the import
      flow will attempt to import it and create a config entry, to assist users
      migrating from the old wiser component. Otherwise, the user will have to
      continue setting up the integration via the config flow.
      """
      hass.data[DATA_WISER_CONFIG] = config.get(DOMAIN, {})
  
      if not hass.config_entries.async_entries(DOMAIN) and hass.data[DATA_WISER_CONFIG]:
          # No config entry exists and configuration.yaml config exists, trigger the import flow.
          hass.async_create_task(
              hass.config_entries.flow.async_init(
                  DOMAIN,
                  context={"source": SOURCE_IMPORT},
                  data=hass.data[DATA_WISER_CONFIG],
              )
          )
  
      return True
code_tokens: async def async_setup ( hass , config ) : hass . data [ DATA_WISER_CONFIG ] = config . get ( DOMAIN , { } ) if not hass . config_entries . async_entries ( DOMAIN ) and hass . data [ DATA_WISER_CONFIG ] : hass . async_create_task ( hass . config_entries . flow . async_init ( DOMAIN , context = { "source" : SOURCE_IMPORT } , data = hass . data [ DATA_WISER_CONFIG ] , ) ) return True
short_docstring: Wiser uses config flow for configuration.
short_docstring_tokens: Wiser uses config flow for configuration .
comment: """
      Wiser uses config flow for configuration.
      But, a "wiser:" entry in configuration.yaml will trigger an import flow
      if a config entry doesn't already exist. If it exists, the import
      flow will attempt to import it and create a config entry, to assist users
      migrating from the old wiser component. Otherwise, the user will have to
      continue setting up the integration via the config flow.
      """$SEP$# No config entry exists and configuration.yaml config exists, trigger the import flow.