Script scaffold throwing error

I have forked and cloned the core repo to see how to add an integration, I’ve done the needed steps but when I get to generate an integration using script.scaffold, when it starts running the hassfest part, I get the following error:

I tried removing these 2 lines in the quality_scale.py and it worked after rerunning the command again, but I am not sure that it’s correct this way to remove these lines:

what I am trying to know is why it failed there and how can I avoid that without removing these lines?

I am using WSL on Windows by the way.

I had the same erorr today trying to create my development environment.

Running the script hassfest manually throws the following error:

Integration integration_name:
* [ERROR] [QUALITY_SCALE] Quality scale definition not found. New integrations are required to at least reach the Bronze tier.

i haven’t found a solution yet.

1 Like

Hi

Did you find a solution ? as I hit the same issue and can’t find a solution even here in forum :frowning:

Thanks

Vincèn

I must be honest I don’t understand the change in development flow. You need a quality_scale.yaml file in your integration marking items as done. But I am not sure how it is not a circular dependency – I need to run hassfest script so I can test SSPD integration so I can complete the quality scale requirements but I need to complete the quality scale requirements before I can run the hassfest script. So in the meantime so I can continue working the content of my quality_scale.yaml file is :

rules:
  # Bronze
  action-setup: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  appropriate-polling: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  brands: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  common-modules: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  config-flow-test-coverage: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  config-flow: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  dependency-transparency: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  docs-actions: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  docs-high-level-description: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  docs-installation-instructions: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  docs-removal-instructions: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  entity-event-setup: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  entity-unique-id: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  has-entity-name: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  runtime-data: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  test-before-configure: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  test-before-setup: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.
  unique-config-entry: 
    status: exempt
    comment: |
      This integration is in development and requires a manifest for debugging purposes.

what I did was pulling the latest changes in the dev branch and trying again then it just worked

a dirty workaround posted here for the script failing:

Well you need to a quaility_scale.yaml file in any case so might as well start with one :slight_smile: Otherwise will probably just hit a brick wall later on in the process.