Skip to content

Releases: twrecked/hass-virtual

version 0.9.0.alpha.6

13 Dec 23:06
197dc96
Compare
Choose a tag to compare
version 0.9.0.alpha.6 Pre-release
Pre-release

Welcome to the 0.9.0 Alpha Releases

WARNING: This is a very alpha release and intended for experienced Home Assistant users.

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

What Should Happen

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

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.5

  • added import notice

Differences from 0.4

  • fix availability service
  • added Czech translation

Differences from 0.3

  • fix time deltas when importing

Differences from 0.2

  • fixed device tracker import issue
  • added Slovakian translations (thanks @misa1515)

Differences from 0.1

  • debug for an import issue

version 0.9.0.alpha.5

09 Dec 17:21
1a5460d
Compare
Choose a tag to compare
version 0.9.0.alpha.5 Pre-release
Pre-release

Welcome to the 0.9.0 Alpha Releases

WARNING: This is a very alpha release and intended for experienced Home Assistant users.

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

What Should Happen

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

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.4

  • fix availability service
  • added Czech translation

Differences from 0.3

  • fix time deltas when importing

Differences from 0.2

  • fixed device tracker import issue
  • added Slovakian translations (thanks @misa1515)

Differences from 0.1

  • debug for an import issue

version 0.9.0.alpha.4

27 Nov 20:37
640469f
Compare
Choose a tag to compare
version 0.9.0.alpha.4 Pre-release
Pre-release

Welcome to the 0.9.0 Alpha Releases

DANGER: This is a very alpha release and intended for experienced Home Assistant users.
DANGER: This is a very alpha release, please try on a test system first if possible.

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

What Should Happen

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

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.3

  • fix time deltas when importing

Differences from 0.2

  • fixed device tracker import issue
  • added Slovakian translations (thanks @misa1515)

Differences from 0.1

  • debug for an import issue

version 0.9.0.alpha.3

24 Nov 19:40
627a541
Compare
Choose a tag to compare
version 0.9.0.alpha.3 Pre-release
Pre-release

Welcome to the 0.9.0 Alpha Releases

DANGER: This is a very alpha release and intended for experienced Home Assistant users.
DANGER: This is a very alpha release, please try on a test system first if possible.

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

What Should Happen

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

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.2

  • fixed device tracker import issue
  • added Slovakian translations (thanks @misa1515)

Differences from 0.1

  • debug for an import issue

version 0.9.0.alpha.2

23 Nov 12:12
1f15209
Compare
Choose a tag to compare
version 0.9.0.alpha.2 Pre-release
Pre-release

Welcome to the 0.9.0 Alpha Releases

DANGER: This is a very alpha release and intended for experienced Home Assistant users.
DANGER: This is a very alpha release, please try on a test system first if possible.

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

What Should Happen

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

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.1

  • debug for an import issue

version 0.9.0.alpha.1

09 Nov 16:51
88b0320
Compare
Choose a tag to compare
version 0.9.0.alpha.1 Pre-release
Pre-release

Welcome to the 0.9.0 Alpha Releases

DANGER: This is a very alpha release and intended for experienced Home Assistant users.
DANGER: This is a very alpha release, please try on a test system first if possible.

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

What Should Happen

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

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.8.0.1

08 Nov 12:50
9f3eda9
Compare
Choose a tag to compare

There are no changes.

This moves the branch out of beta, I'm getting ready to put the config flow version into alpha.

version 0.8.0.beta.1

06 Feb 19:55
26c94df
Compare
Choose a tag to compare

Added restore state to the entities.
thanks to SergeyPomelov for the push on this

Added "locking" and "unlocking" states to the lock mechanism. Added a random jamming ability.

Tidied the underlying code. The classes are now much simpler and better follow the
Home Assistant examples.

Added device_tracker restore state.

version 0.8.0.alpha.3

25 Jan 04:15
4805502
Compare
Choose a tag to compare
version 0.8.0.alpha.3 Pre-release
Pre-release

This is an ALPHA release, I'm running at home and it's working great but I've not had chance to test every device fully.

Added restore state to the entities.
thanks to SergeyPomelov for the push on this

Added "locking" and "unlocking" states to the lock mechanism. Added a random jamming ability.

Tidied the underlying code. The classes are now much simpler and better follow the
Home Assistant examples.

Added device_tracker restore state.

version 0.8.0.alpha.2

10 Jan 19:52
4679a4c
Compare
Choose a tag to compare
version 0.8.0.alpha.2 Pre-release
Pre-release

This is an ALPHA release, I'm running at home and it's working great but I've not had chance to test every device fully.

Added restore state to most entities. (device_tracker being the lone hold out.)
thanks to SergeyPomelov for the push on this

Added "locking" and "unlocking" states to the lock mechanism. Added a random jamming ability.

Tidied the underlying code. The classes are now much simpler and better follow the
Home Assistant examples.