217b456e75
This was preventing the rendering of other elements on Home page until those elements gets an update on it's statuses. This change also add a input for default icon fallback colors for `on` and `off` states. Solves #1624
32 lines
1.5 KiB
Markdown
32 lines
1.5 KiB
Markdown
# 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
|
|
1. Add the following to your device's YAML to reduce resource usage (this may slow down the compilation process):
|
|
|
|
```yaml
|
|
# Limit the amount of resources used for compiling
|
|
esphome:
|
|
compile_process_limit: 1
|
|
```
|
|
|
|
> [!TIP]
|
|
> Place this in a dedicated customization section in your YAML for easier maintenance,
|
|
similar to [this example](https://github.com/Blackymas/NSPanel_HA_Blueprint/blob/main/docs/customization.md#instructions).
|
|
|
|
2. Restart your host system, not just Home Assistant. Use the advanced options to **Reboot system**, which also restarts add-ons and can free up memory.
|
|
|
|
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**").
|
|
|
|
5. Try compiling again.
|
|
|
|
6. After completion, restart your host system to reactivate the stopped add-ons.
|
|
|
|
## 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).
|
|
|
|
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.
|