1
0

Compare commits

...

12 Commits

7 changed files with 24 additions and 8 deletions

View File

@@ -89,7 +89,11 @@ authentication by setting it to `true`.
Manually override which ESPHome version to use in the add-on.
For example to install the latest development version, use `"esphome_version": "dev"`,
or for version 1.14.0: `"esphome_version": "v1.14.0""`.
or for version 1.14.0: `"esphome_version": "v1.14.0"`.
This can also be used to specify a branch of a fork of the esphome repository.
For example to install the test_new_component branch of a fork made by user123, use `"user123:test_new_component"`.
This usage assumes the forked repository is named `esphome`.
Please note that this does not always work and is only meant for testing, usually the
ESPHome add-on and dashboard version must match to guarantee a working system.

View File

@@ -42,6 +42,6 @@
"stage": "experimental",
"startup": "application",
"url": "https://beta.esphome.io/",
"version": "1.15.1",
"version": "1.16.0",
"webui": "http://[HOST]:[PORT:6052]"
}

View File

@@ -89,7 +89,11 @@ authentication by setting it to `true`.
Manually override which ESPHome version to use in the add-on.
For example to install the latest development version, use `"esphome_version": "dev"`,
or for version 1.14.0: `"esphome_version": "v1.14.0""`.
or for version 1.14.0: `"esphome_version": "v1.14.0"`.
This can also be used to specify a branch of a fork of the esphome repository.
For example to install the test_new_component branch of a fork made by user123, use `"user123:test_new_component"`.
This usage assumes the forked repository is named `esphome`.
Please note that this does not always work and is only meant for testing, usually the
ESPHome add-on and dashboard version must match to guarantee a working system.

View File

@@ -89,7 +89,11 @@ authentication by setting it to `true`.
Manually override which ESPHome version to use in the add-on.
For example to install the latest development version, use `"esphome_version": "dev"`,
or for version 1.14.0: `"esphome_version": "v1.14.0""`.
or for version 1.14.0: `"esphome_version": "v1.14.0"`.
This can also be used to specify a branch of a fork of the esphome repository.
For example to install the test_new_component branch of a fork made by user123, use `"user123:test_new_component"`.
This usage assumes the forked repository is named `esphome`.
Please note that this does not always work and is only meant for testing, usually the
ESPHome add-on and dashboard version must match to guarantee a working system.

View File

@@ -42,6 +42,6 @@
"stage": "stable",
"startup": "application",
"url": "https://esphome.io/",
"version": "1.15.1",
"version": "1.16.0",
"webui": "http://[HOST]:[PORT:6052]"
}

View File

@@ -89,7 +89,11 @@ authentication by setting it to `true`.
Manually override which ESPHome version to use in the add-on.
For example to install the latest development version, use `"esphome_version": "dev"`,
or for version 1.14.0: `"esphome_version": "v1.14.0""`.
or for version 1.14.0: `"esphome_version": "v1.14.0"`.
This can also be used to specify a branch of a fork of the esphome repository.
For example to install the test_new_component branch of a fork made by user123, use `"user123:test_new_component"`.
This usage assumes the forked repository is named `esphome`.
Please note that this does not always work and is only meant for testing, usually the
ESPHome add-on and dashboard version must match to guarantee a working system.

View File

@@ -56,7 +56,7 @@ esphome-beta:
<<: *base
directory: esphome-beta
name: ESPHome (beta)
version: '1.15.1' # BETA
version: '1.16.0' # BETA
slug: esphome-beta
description: "Beta version of ESPHome Hass.io add-on."
url: https://beta.esphome.io/
@@ -68,7 +68,7 @@ esphome-stable:
<<: *base
directory: esphome
name: ESPHome
version: '1.15.1' # STABLE
version: '1.16.0' # STABLE
slug: esphome
description: "ESPHome Hass.io add-on for intelligently managing all your ESP8266/ESP32 devices."
image: esphome/esphome-hassio-{arch}