version 0.7.0.beta.12

Welcome to the Momentary 0.7 beta releases...

This is a big update that moves the component over to the config_flow system. The update should be seamless but if you run into any problems:

• You can revert back to the previous version (0.6) and it will still work.
• But if you can re-run the upgrade operation with debug enabled and create a bug report I would greatly appreciate it.

Once it has completed you will have a Momentary integration and you will be able to view your devices like you do every other integration.

After the upgrade you can comment out the momentary pieces from your current config. Don't delete them for now, just in case...

Please look at the README, because this is a virtual system it still uses a YAML configuration file (default /config/momentary.yaml). But going forward you will be able to modify the list on the fly.

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

Then add yaml_config: True to the momentary platform configuration.

momentary:
  yaml_config: True

Difference from beta.12

• use async calls
• allow old config

Difference from beta.11 and before

• fix write meta race condition
• fix event loop warning
• fixed an issue with no switches
• fix async callback issue
• fix import issues
• fix time delta import issue
• Allow multiple switches per device
• Internal code tidy
• Slovakian translations, thanks @misa1515
• Use explicit instance variables

version 0.7.0.beta.11

Welcome to the Momentary 0.7 beta releases...

This is a big update that moves the component over to the config_flow system. The update should be seamless but if you run into any problems:

• You can revert back to the previous version (0.6) and it will still work.
• But if you can re-run the upgrade operation with debug enabled and create a bug report I would greatly appreciate it.

Once it has completed you will have a Momentary integration and you will be able to view your devices like you do every other integration.

After the upgrade you can comment out the momentary pieces from your current config. Don't delete them for now, just in case...

Please look at the README, because this is a virtual system it still uses a YAML configuration file (default /config/momentary.yaml). But going forward you will be able to modify the list on the fly.

Difference from beta.9

• fix write meta race condition
• fix event loop warning

Difference from beta.8 and before

• fixed an issue with no switches
• fix async callback issue
• fix import issues
• fix time delta import issue
• Allow multiple switches per device
• Internal code tidy
• Slovakian translations, thanks @misa1515
• Use explicit instance variables

version 0.7.0.beta.9

Welcome to the Momentary 0.7 beta releases...

This is a big update that moves the component over to the config_flow system. The update should be seamless but if you run into any problems:

• You can revert back to the previous version (0.6) and it will still work.
• But if you can re-run the upgrade operation with debug enabled and create a bug report I would greatly appreciate it.

Once it has completed you will have a Momentary integration and you will be able to view your devices like you do every other integration.

After the upgrade you can comment out the momentary pieces from your current config. Don't delete them for now, just in case...

Please look at the README, because this is a virtual system it still uses a YAML configuration file (default /config/momentary.yaml). But going forward you will be able to modify the list on the fly.

Difference from beta.8

• fixed an issue with no switches

Difference from alpha.7

• fix async callback issue

Difference from alpha.5

• fix import issues

Difference from alpha.4

• fix time delta import issue

Difference from alpha.3

• Allow multiple switches per device

Difference from alpha.2

• Internal code tidy

Difference from alpha.1

• Slovakian translations, thanks @misa1515
• Use explicit instance variables

version 0.6.4

Fix a threading warning

version 0.7.0.beta.8

Welcome to the Momentary 0.7 beta releases...

This is a big update that moves the component over to the config_flow system. The update should be seamless but if you run into any problems:

• You can revert back to the previous version (0.6) and it will still work.
• But if you can re-run the upgrade operation with debug enabled and create a bug report I would greatly appreciate it.

Once it has completed you will have a Momentary integration and you will be able to view your devices like you do every other integration.

After the upgrade you can comment out the momentary pieces from your current config. Don't delete them for now, just in case...

Please look at the README, because this is a virtual system it still uses a YAML configuration file (default /config/momentary.yaml). But going forward you will be able to modify the list on the fly.

Difference from alpha.7

• fix async callback issue

Difference from alpha.5

• fix import issues

Difference from alpha.4

• fix time delta import issue

Difference from alpha.3

• Allow multiple switches per device

Difference from alpha.2

• Internal code tidy

Difference from alpha.1

• Slovakian translations, thanks @misa1515
• Use explicit instance variables

version 0.7.0.alpha.6

Welcome to the Momentary 0.7 alpha releases...

This is a big update that moves the component over to the config_flow system. The update should be seamless but if you run into any problems:

• You can revert back to the previous version (0.6) and it will still work.
• But if you can re-run the upgrade operation with debug enabled and create a bug report I would greatly appreciate it.

Once it has completed you will have a Momentary integration and you will be able to view your devices like you do every other integration.

After the upgrade you can comment out the momentary pieces from your current config. Don't delete them for now, just in case...

Please look at the README, because this is a virtual system it still uses a YAML configuration file (default /config/momentary.yaml). But going forward you will be able to modify the list on the fly.

Difference from alpha.5

• fix import issues

Difference from alpha.4

• fix time delta import issue

Difference from alpha.3

• Allow multiple switches per device

Difference from alpha.2

• Internal code tidy

Difference from alpha.1

• Slovakian translations, thanks @misa1515
• Use explicit instance variables

version 0.7.0.alpha.5

Welcome to the Momentary 0.7 alpha releases...

This is a big update that moves the component over to the config_flow system. The update should be seamless but if you run into any problems:

• You can revert back to the previous version (0.6) and it will still work.
• But if you can re-run the upgrade operation with debug enabled and create a bug report I would greatly appreciate it.

Once it has completed you will have a Momentary integration and you will be able to view your devices like you do every other integration.

After the upgrade you can comment out the momentary pieces from your current config. Don't delete them for now, just in case...

Please look at the README, because this is a virtual system it still uses a YAML configuration file (default /config/momentary.yaml). But going forward you will be able to modify the list on the fly.

Difference from alpha.4

• fix time delta import issue

Difference from alpha.3

• Allow multiple switches per device

Difference from alpha.2

• Internal code tidy

Difference from alpha.1

• Slovakian translations, thanks @misa1515
• Use explicit instance variables

version 0.7.0.alpha.4

Welcome to the Momentary 0.7 alpha releases...

This is a big update that moves the component over to the config_flow system. The update should be seamless but if you run into any problems:

• You can revert back to the previous version (0.6) and it will still work.
• But if you can re-run the upgrade operation with debug enabled and create a bug report I would greatly appreciate it.

Once it has completed you will have a Momentary integration and you will be able to view your devices like you do every other integration.

After the upgrade you can comment out the momentary pieces from your current config. Don't delete them for now, just in case...

Please look at the README, because this is a virtual system it still uses a YAML configuration file (default /config/momentary.yaml). But going forward you will be able to modify the list on the fly.

Difference from alpha.3

• Allow multiple switches per device

Difference from alpha.2

• Internal code tidy

Difference from alpha.1

• Slovakian translations, thanks @misa1515
• Use explicit instance variables

version 0.7.0.alpha.2

Welcome to the Momentary 0.7 alpha releases...

This is a big update that moves the component over to the config_flow system. The update should be seamless but if you run into any problems:

• You can revert back to the previous version (0.6) and it will still work.
• But if you can re-run the upgrade operation with debug enabled and create a
  bug report I would greatly appreciate it.

Once it has completed you will have a Momentary integration and you will be able to view your devices like you do every other integration.

After the upgrade you can comment out the momentary pieces from your current config. Don't delete them for now, just in case...

Please look at the README, because this is a virtual system it still uses a YAML configuration file (default /config/momentary.yaml). But going forward you will be able to modify the list on the fly.

Difference from alpha.1

• Slovakian translations, thanks @misa1515
• Use explicit instance variables

version 0.7.0.alpha.1

This is a big update that moves the component over to the config_flow system. The update should be seamless but if you run into any problems:

• You can revert back to the previous version (0.6) and it will still work.
• But if you can re-run the upgrade operation with debug enabled and create a
  bug report I would greatly appreciate it.

Once it has completed you will have a Momentary integration and you will be able to view your devices like you do every other integration.

After the upgrade you can comment out the momentary pieces from your current config. Don't delete them for now, just in case...

Please look at the README, because this is a virtual system it still uses a YAML configuration file (default /config/momentary.yaml). But going forward you will be able to modify the list on the fly.