Skip to content
Alan Tse edited this page Mar 24, 2019 · 33 revisions

Please see configuration for update instructions.

1.2.4 DEV

  • Update online/active based on DOPLER_STATE_CHANGE from websockets (resolves #133)

1.2.3 03/19/2019

  • Fix bug where polling would not resume after websocket failure (resolves #128)
  • Update to alexapy 0.4.2 (resolves #127)

1.2.2 03/17/2019

Fixes:

  • Fix bug where emulated_hue and other smart home device routines failed. (resolves #123)
  • Fix bug where Alexa devices that came online later were not properly updated. (resolves #125)

Changes:

  • Add websocket support (resolves #119) - This allows us to remove most polling and rely on push notifications from Amazon. This also means that media_players should update regardless of how or where you interact with them as last_called should update immediately. As a result alexa_media.update_last_called service may no longer be required. Prior polling methods remain as a fallback mechanism if websocket can't connect which may be based on region. No additional configuration is needed.
  • Update to alexapy 0.4.0 (websocket support)

1.2.1 03/12/2019

Fixes:

  • Fix bugs related to generation of targets for announce (resolves #114, #117, #118)

1.2.0 03/12/2019

Features:

  • Add notification service. (resolves #51)

Changes:

  • Update to alexapy 0.3.0 (announce/mobile push)

Deprecation Warning: media_player.alexa_tts will be deprecated in the next version. Please use the notify.alexa_media service.

1.1.0 03/01/2019

Features:

  • Custom_updater support (resolve #58)
  • alexa_media.update_last_called service to allow manual update of last_called (resolve #83)

Fixes:

  • Entry too long database errors (resolve #88)
  • Display of media position while playing (resolve #91)
  • Routines failing if only one step or presence of non_utterance routines (resolve #90)
  • Configurator failure if no verification options available (resolve #101)
  • TTS failure with multiple accounts (resolve #86)
  • Configurator only able to configure one account per restart (resolve #98)
  • Multiple last_called devices for same account (resolve #97)

Changes:

  • Additional polling on detection of a voice event to handle case where command would be to play on other devices
  • More debugging
  • Update to alexapy 0.2.1 (fixes and announce/mobile push)

1.0.0 2/22/2019

  • Split to platform and pypi API (resolves #14, #62)
  • Add multiple account support (resolves #37)
  • Fix bug where cookie login didn't detect changes in configuration (resolves #63)
  • Reduce media player polling. Polling should restart using HA or voice, but not other Apps. (resolves #70)
  • Add sequence processing for more programmatic support.
  • Add automation routine support.
  • Allow for volume changes when media not playing or paused (resolves #43)

0.10.2 2/20/2019

  • Fix for HA 0.88.0 architecture change (#77)

0.10.1 1/25/2019

  • Typo fix in last_call

0.10.0 1/25/2019

  • Bug fix to use logged in user for media playback
  • Add last_called attribute (thanks @brianhanifin)

0.9.6 12/22/2018

  • Add exclude and include device config (thanks @nuttytree)

0.9.5 9/11/2018

  • Bug fixes on get_bluetooth parsing
  • Change refresh to online devices only

0.9.4 8/31/2018

  • Fix bug where failed cookie login doesn't try config login

0.9.3 8/30/2018

  • Handle Amazon verification method request page

0.9.2 8/25/2018

  • Bug fixes on unavailable data

0.9.1 8/20/2018

  • Bug fixes to improve login robustness and unavailable data

0.9.0 8/13/2018

  • Add 2FA support

0.8.1 8/7/2018

  • Json fixes for python 3.5

0.8.0 8/5/2018

  • Bug fixes
  • Flake 8 lint fixes

0.7.1 8/4/2018

  • Bug fixes
  • Cookie support
  • Play media support

0.6 7/17/2018

  • Fix bs4 issues
  • Add configurator and deprecate addon requirement

0.5 7/10/2018

  • Add bluetooth disconnect controls

0.4 7/10/2018

  • First versioned release
  • Bluetooth device selection

< 0.4 7/3/2018

  • Initial public release

This changelog was manually created based off the commit history after the fact by a contributor (@alandtse) and not the original maintainer (@keatontaylor). Commit history should be considered authoritative.