2.0.11 Release - requires Indigo 7

Passes special character (umlauts) in names such as 'küche' through to Alexa.
Fixes problem with special characters (umlauts) in Alternate name field.

Corrects a duplicate image error in the README documentation.

2.0.9 Release - requires Indigo 7

This release requires Indigo 7. For Indigo 6, use the latest 1.x release.

This release has added in the option to specify the IP Address of the Apple Mac that the plugin is running on.
Changed some detected errors to go to Event Log rather than Debug Log.
Display the Host IP Address being used, in the Indigo Event Log.

Now the official release - 12th January 2017

2.0.8 Release - requires Indigo 7

This release requires Indigo 7. For Indigo 6, use the latest 1.x release.

This release has added in improved error checking for Responder socket errors thereby hopefully facilitating improved problem resolution.

Flagged as pre-Release pending further user testing (by those users experiencing problems)

2.0.7 Release - requires Indigo 7

This release requires Indigo 7. For Indigo 6, use the latest 1.x release.

This release has corrected some issues with discovery and fixed some minor bugs. In addition there is a new plugin config option that can be set to display Discovery Logging in the Indigo Event Log (it is ON by default).

Documentation has been updated for new version :)

2.0.2 Release - requires Indigo 7

This release requires Indigo 7. For Indigo 6, use the latest 1.x release.

This is a big contribution from one of our 3rd party developers. It now supports multiple virtual Hue Bridges so you can now have unlimited Alexa devices.

1.0.3 Release

Added some retry logic to solve an issue where the HTTP thread would fail to start because the previous one had yet to free up the port. This can happen when doing a plugin reload. Python is sometimes finicky about closing down and release network ports.

1.0.2 Release

This release resolved an issue introduced by an update to the Echo on 2/10/2016. It also attempts to resolve at least some of the UPNP port conflicts by opening the port shared. Other apps that do the same can have the port open and each will get a copy of all requests to the port. It may still interfere with other processes that don't open the port shared, but it's an improvement. With this change, we've now started the discovery process at plugin start time and it will run indefinitely. You can still stop/start discovery yourself using the menu items and/or actions.

1.0.1

Adds some extra error logging such that when another process has the UPNP port open, it shows some reasonable errors in the Event Log that will help the user figure out what to do.

Initial Release

This is the initial release of the plugin.