h3n3/NSPanel_HA_Blueprint
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge branch 'dev' of https://github.com/Blackymas/NSPanel_HA_Blueprint into dev

Browse Source
This commit is contained in:
Edward Firmo
2024-01-15 10:41:06 +01:00
parent e0c6fb9810 aae12d0be7
commit a1a2a897c6
2 changed files with 17 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
.github/workflows/validate_yamllint.yml vendored
View File

@@ -7,18 +7,10 @@ on:
paths: paths:
- '**/*.yml' - '**/*.yml'
- '**/*.yaml' - '**/*.yaml'
paths-ignore:
- "nspanel_esphome*.yaml"
- "advanced/esphome/nspanel_esphome*.yaml"
- "nspanel_blueprint.yaml"
pull_request: pull_request:
paths: paths:
- '**/*.yml' - '**/*.yml'
- '**/*.yaml' - '**/*.yaml'
paths-ignore:
- "nspanel_esphome*.yaml"
- "advanced/esphome/nspanel_esphome*.yaml"
- "nspanel_blueprint.yaml"
workflow_dispatch: workflow_dispatch:
jobs: jobs:
@@ -41,6 +33,10 @@ jobs:
run: | run: |
IFS=',' read -ra FILES <<< "${{ steps.changed-files.outputs.all_changed_files }}" IFS=',' read -ra FILES <<< "${{ steps.changed-files.outputs.all_changed_files }}"
for file in "${FILES[@]}"; do for file in "${FILES[@]}"; do
if [[ "$file" =~ ^nspanel_esphome.*\.yaml$ ]] || [[ "$file" =~ ^advanced/esphome/nspanel_esphome.*\.yaml$ ]] || [[ "$file" == "nspanel_blueprint.yaml" ]]; then
echo "Skipping $file"
continue
fi
echo "::group::Validating $file" echo "::group::Validating $file"
yamllint -c "./.rules/yamllint.yml" "$file" yamllint -c "./.rules/yamllint.yml" "$file"
echo "::endgroup::" echo "::endgroup::"

18
docs/error_compiling.md
View File

@@ -1,8 +1,16 @@
# Compiling Errors Guide # Compiling Errors Guide
It seems the issue is due to insufficient resources on your server for compiling.
Here are two suggestions:
## Free Up Server Resources The most common cases for compiling errors are related to build files needing to be cleaned up and to lack of resourced on your ESPHome comoiler host.
These are our suggestions for both cases:
## Clean-up build files
Go to your ESPHome Dashboard, click the 3-dot meny related to your device and then "**Clean Build Files**":
![image](https://raw.githubusercontent.com/Blackymas/NSPanel_HA_Blueprint/dev/docs/pics/esphome_dashboard_clean_build_files.png)
## Limited resources on ESPHome compiler host
### Free Up Server Resources
1. Add the following to your device's YAML to reduce resource usage (this may slow down the compilation process): 1. Add the following to your device's YAML to reduce resource usage (this may slow down the compilation process):
```yaml ```yaml
@@ -19,13 +27,13 @@ Here are two suggestions:
3. Temporarily stop non-essential add-ons in Home Assistant, especially resource-intensive ones like Studio Code Server. 3. Temporarily stop non-essential add-ons in Home Assistant, especially resource-intensive ones like Studio Code Server.
4. Clean up build files (on the ESPHome Dashboard, click the 3-dot meny related to your device and then "**Clean Build Files**"). 4. [Clean up build files](#clean-up-build-files)
5. Try compiling again. 5. Try compiling again.
6. After completion, restart your host system to reactivate the stopped add-ons. 6. After completion, restart your host system to reactivate the stopped add-ons.
## Compile Using Your Computer ### Compile Using Your Computer
1. Install ESPHome on your computer (Windows, Mac, or Linux) following this guide: [Installing ESPHome Manually](https://esphome.io/guides/installing_esphome.html). 1. Install ESPHome on your computer (Windows, Mac, or Linux) following this guide: [Installing ESPHome Manually](https://esphome.io/guides/installing_esphome.html).
2. With ESPHome installed locally, you can use the ESPHome Dashboard or the [ESPHome Command Line Interface](https://esphome.io/guides/cli.html#command-line-interface) for compilation. 2. With ESPHome installed locally, you can use the ESPHome Dashboard or the [ESPHome Command Line Interface](https://esphome.io/guides/cli.html#command-line-interface) for compilation.