version 0.9.3

Welcome to the 0.9.3 Release

This 0.9.x releases adds proper Integration and config flow support to the Virtual component.

What Should Happen when Coming from 0.8

The code will upgrade an older installation to use Config Flow. It will move all your current config
into a single file (/config/virtual.yaml) and it will create a Virtual integration. All your current Virtual
entities should re-appear.

**!!! Argh, I don't want this!!! **

Then add yaml_config: True to the virtual platform configuration.

virtual:
  yaml_config: True

This option allows you to mix old and new config styles.

What will Cause Pain when Coming from 0.8

Any device_tracker entities will need to be recreated. See here for instructions on how to do that.

I tried to fix this but the way the old entries were created is causing the issue.

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

Fixes in 0.9.3:

• Fix some deprecation warnings.
• Tidy up cover and valve code. Many thanks to @mikz

Fixed in 0.9.2

• an unload issue
• deprecated warnings

version 0.9.2

Welcome to the 0.9.2 Release

This 0.9.x releases adds proper Integration and config flow support to the Virtual component.

What Should Happen when Coming from 0.8

The code will upgrade an older installation to use Config Flow. It will move all your current config
into a single file (/config/virtual.yaml) and it will create a Virtual integration. All your current Virtual
entities should re-appear.

**!!! Argh, I don't want this!!! **

Then add yaml_config: True to the virtual platform configuration.

virtual:
  yaml_config: True

This option allows you to mix old and new config styles.

What will Cause Pain when Coming from 0.8

Any device_tracker entities will need to be recreated. See here for instructions on how to do that.

I tried to fix this but the way the old entries were created is causing the issue.

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

Fixed from 0.9.1

• an unload issue
• deprecated warnings

version 0.9.1

Welcome to the 0.9.1 Release

This release adds proper Integration and config flow support to the Virtual component.

What Should Happen when Coming from 0.8

The code will upgrade an older installation to use Config Flow. It will move all your current config
into a single file (/config/virtual.yaml) and it will create a Virtual integration. All your current Virtual
entities should re-appear.

**!!! Argh, I don't want this!!! **

Then add yaml_config: True to the virtual platform configuration.

virtual:
  yaml_config: True

This option allows you to mix old and new config styles.

What will Cause Pain when Coming from 0.8

Any device_tracker entities will need to be recreated. See here for instructions on how to do that.

I tried to fix this but the way the old entries were created is causing the issue.

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

version 0.9.0.beta.18

Welcome to the 0.9.0 Beta Releases

This release adds proper Integration and config flow support to the Virtual component.

What Should Happen when Coming from 0.8

The code will upgrade an older installation to use Config Flow. It will move all your current config
into a single file (/config/virtual.yaml) and it will create a Virtual integration. All your current Virtual
entities should re-appear.

**!!! Argh, I don't want this!!! **

Then add yaml_config: True to the virtual platform configuration.

virtual:
  yaml_config: True

This option allows you to mix old and new config styles.

What will Cause Pain when Coming from 0.8

Any device_tracker entities will need to be recreated. See here for instructions on how to do that.

I tried to fix this but the way the old entries were created is causing the issue.

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

Differences from 0.17

• added virtual numbers; thanks @olegtarasov
• updated Slovakian translation; thanks @misa1515

Differences from 0.16 and before

• switch device tracker to GPS if needed
• Fix warning about POWER_VOLT_AMPERE_REACTIVE
• Fix colo(u)r handling of lights
• Fix restore state of lights
• Add GPS accuracy
• github sale action
• use async interfaces where possible
• fixed threading issues found in debug mode
• added back original yaml support
• added valve support
• tided the docs
• add GPS coordinates to device tracker
• fix fan support
• fix cover service calls
• fix light support
• fix a reload issue
• fix a race condition
• improved cover support (thanks @lodegaard)
• fix I/O in event loop
• fixed set available issue
• fixed startup issue #2
• fixed deprecated issue
• fixed startup issue
• added import notice
• fix availability service
• added Czech translation
• fix time deltas when importing
• fixed device tracker import issue
• added Slovakian translations (thanks @misa1515)
• debug for an import issue

version 0.9.0.beta.17

Welcome to the 0.9.0 Beta Releases

This release adds proper Integration and config flow support to the Virtual component.

What Should Happen when Coming from 0.8

The code will upgrade an older installation to use Config Flow. It will move all your current config
into a single file (/config/virtual.yaml) and it will create a Virtual integration. All your current Virtual
entities should re-appear.

**!!! Argh, I don't want this!!! **

Then add yaml_config: True to the virtual platform configuration.

virtual:
  yaml_config: True

This option allows you to mix old and new config styles.

What will Cause Pain when Coming from 0.8

Any device_tracker entities will need to be recreated. See here for instructions on how to do that.

I tried to fix this but the way the old entries were created is causing the issue.

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

Differences from 0.16

• switch device tracker to GPS if needed
• Fix warning about POWER_VOLT_AMPERE_REACTIVE
• Fix colo(u)r handling of lights
• Fix restore state of lights
• Add GPS accuracy

Differences from 0.15 and before

• github sale action
• use async interfaces where possible
• fixed threading issues found in debug mode
• added back original yaml support
• added valve support
• tided the docs
• add GPS coordinates to device tracker
• fix fan support
• fix cover service calls
• fix light support
• fix a reload issue
• fix a race condition
• improved cover support (thanks @lodegaard)
• fix I/O in event loop
• fixed set available issue
• fixed startup issue #2
• fixed deprecated issue
• fixed startup issue
• added import notice
• fix availability service
• added Czech translation
• fix time deltas when importing
• fixed device tracker import issue
• added Slovakian translations (thanks @misa1515)
• debug for an import issue

version 0.9.0.beta.15

Welcome to the 0.9.0 Beta Releases

This release adds proper Integration and config flow support to the Virtual component.

What Should Happen when Coming from 0.8

The code will upgrade an older installation to use Config Flow. It will move all your current config
into a single file (/config/virtual.yaml) and it will create a Virtual integration. All your current Virtual
entities should re-appear.

**!!! Argh, I don't want this!!! **

Then add yaml_config: True to the virtual platform configuration.

virtual:
  yaml_config: True

This option allows you to mix old and new config styles.

What will Cause Pain when Coming from 0.8

Any device_tracker entities will need to be recreated. See here for instructions on how to do that.

I tried to fix this but the way the old entries were created is causing the issue.

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

Differences from 0.14

• fixed threading issues found in debug mode

Differences from 0.13 and before

• added back original yaml support
• added valve support
• tided the docs
• add GPS coordinates to device tracker
• fix fan support
• fix cover service calls
• fix light support
• fix a reload issue
• fix a race condition
• improved cover support (thanks @lodegaard)
• fix I/O in event loop
• fixed set available issue
• fixed startup issue #2
• fixed deprecated issue
• fixed startup issue
• added import notice
• fix availability service
• added Czech translation
• fix time deltas when importing
• fixed device tracker import issue
• added Slovakian translations (thanks @misa1515)
• debug for an import issue

version 0.9.0.beta.14

Welcome to the 0.9.0 Beta Releases

This release adds proper Integration and config flow support to the Virtual component.

What Should Happen when Coming from 0.8

The code will upgrade an older installation to use Config Flow. It will move all your current config
into a single file (/config/virtual.yaml) and it will create a Virtual integration. All your current Virtual
entities should re-appear.

**!!! Argh, I don't want this!!! **

Then add yaml_config: True to the virtual platform configuration.

virtual:
  yaml_config: True

This option allows you to mix old and new config styles.

What will Cause Pain when Coming from 0.8

Any device_tracker entities will need to be recreated. See here for instructions on how to do that.

I tried to fix this but the way the old entries were created is causing the issue.

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

Differences from 0.13

• added back original yaml support

Differences from 0.12 and before

• added valve support
• tided the docs
• add GPS coordinates to device tracker
• fix fan support
• fix cover service calls
• fix light support
• fix a reload issue
• fix a race condition
• improved cover support (thanks @lodegaard)
• fix I/O in event loop
• fixed set available issue
• fixed startup issue #2
• fixed deprecated issue
• fixed startup issue
• added import notice
• fix availability service
• added Czech translation
• fix time deltas when importing
• fixed device tracker import issue
• added Slovakian translations (thanks @misa1515)
• debug for an import issue

version 0.9.0.beta.13

Welcome to the 0.9.0 Beta Releases

This release adds proper Integration and config flow support to the Virtual component.

What Should Happen when Coming from 0.8

The code will upgrade an older installation to use Config Flow. It will move all your current config
into a single file (/config/virtual.yaml) and it will create a Virtual integration. All your current Virtual
entities should re-appear.

What will Cause Pain when Coming from 0.8

Any device_tracker entities will need to be recreated. See here for instructions on how to do that.

I tried to fix this but the way the old entries were created is causing the issue.

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

Differences from 0.12

• added valve support
• tided the docs

Differences from 0.11 and before

• add GPS coordinates to device tracker
• fix fan support
• fix cover service calls
• fix light support
• fix a reload issue
• fix a race condition
• improved cover support (thanks @lodegaard)
• fix I/O in event loop
• fixed set available issue
• fixed startup issue #2
• fixed deprecated issue
• fixed startup issue
• added import notice
• fix availability service
• added Czech translation
• fix time deltas when importing
• fixed device tracker import issue
• added Slovakian translations (thanks @misa1515)
• debug for an import issue

version 0.9.0.beta.12

Welcome to the 0.9.0 Beta Releases

This release adds proper Integration and config flow support to the Virtual component.

What Should Happen when Coming from 0.8

The code will upgrade an older installation to use Config Flow. It will move all your current config
into a single file (/config/virtual.yaml) and it will create a Virtual integration. All your current Virtual
entities should re-appear.

What will Cause Pain when Coming from 0.8

Any device_tracker entities will need to be recreated. See here for instructions on how to do that.

I tried to fix this but the way the old entries were created is causing the issue.

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

Differences from 0.11

• add GPS coordinates to device tracker
• fix fan support
• fix cover service calls

Differences from 0.10 and before

• fix light support
• fix a reload issue
• fix a race condition
• improved cover support (thanks @lodegaard)
• fix I/O in event loop
• fixed set available issue
• fixed startup issue #2
• fixed deprecated issue
• fixed startup issue
• added import notice
• fix availability service
• added Czech translation
• fix time deltas when importing
• fixed device tracker import issue
• added Slovakian translations (thanks @misa1515)
• debug for an import issue

version 0.9.0.beta.11

Welcome to the 0.9.0 Beta Releases

This release adds proper Integration and config flow support to the Virtual component.

What Should Happen when Coming from 0.8

The code will upgrade an older installation to use Config Flow. It will move all your current config
into a single file (/config/virtual.yaml) and it will create a Virtual integration. All your current Virtual
entities should re-appear.

What will Cause Pain when Coming from 0.8

Any device_tracker entities will need to be recreated. See here for instructions on how to do that.

I tried to fix this but the way the old entries were created is causing the issue.

If It Goes Wrong

Then revert back to an older install. And for this reason I recommend keeping your old config around, Home Assistant will complain about it but it won't affect anything.

But if you can raise a bug telling me what you were doing, what you expected to happen and what happened that would be great.

Differences from 0.10

• fix light support
• fix a reload issue
• fix a race condition
• improved cover support (thanks @lodegaard)

Differences from 0.9 and before

• fix I/O in event loop
• fixed set available issue
• fixed startup issue #2
• fixed deprecated issue
• fixed startup issue
• added import notice
• fix availability service
• added Czech translation
• fix time deltas when importing
• fixed device tracker import issue
• added Slovakian translations (thanks @misa1515)
• debug for an import issue