Skip to content

Releases: siggel/WLED

AlexaEnhancementV4

17 Sep 15:23
Compare
Choose a tag to compare

2022-10-27: This feature made it to the official WLED repository, so you may switch to an upcoming official release. Only change there will be that you must configure first, how many presets you want to see as Alexa devices, default will be zero in order not to bother users that do not want to use this feature.

Update: Just merging current master into my fork, Alexa enhancement functions stay unchanged:

Call different presets "by name" using Alexa Echo devices, e.g. "Alexa, turn Rainbow on", "Alexa, turn Firework on" etc. This is achieved by creating individual Alexa devices for up to 9 presets in addition to the one configured in WLED's Alexa configuration.

Usage instructions:

  1. Disable Alexa in WLED.
  2. Name the presets (IDs 1 up to 9) like you want to call them when using Alexa, e.g. Rainbow, Firework, Knight Rider, ...
  3. Re-enable Alexa in WLED.
  4. Delete all devices in Alexa that already exist for this WLED device (including the one configured in WLED's Alexa configuration) and then let Alexa search for devices again. You do not need to delete existing devices if you did not edit existing names/preset IDs but just added new presets. Deleting is mandatory if you updated from version AlexaEnhancementV1.
  5. Switch on your presets by simply calling them by their name, e.g. "Alexa, turn Rainbow on". Switch to another preset by simply calling it by another name, e.g. "Alexa, turn Firework on". Use any name for switching off. Additionally the original device exists, that you configured in WLED's Alexa configuration.
  6. Repeat steps 1 to 5 whenever you change preset names/IDs in WLED.

Of course you may try my code or flash the provided D1 mini firmware if you consider this functionality useful. The same license and disclaimer apply as given for the original WLED project. Be aware that I'm far less familiar with the code than the original authors, so - although it works for me - the risk for harmful bugs may be higher. E.g. sometimes I got a "Cannot connect to light" error after flashing (which may be caused by my quite "experimental" wiring instead of using the right connector), but after a reboot all worked fine afterwards.

AlexaEnhancementV3

09 May 21:02
Compare
Choose a tag to compare

Built again without code changes in my part but having merged with a later version of the original repo (that I had pulled back in February, not today's version but one that I had already built and tested before). Issue #1 disappeared but I'm not sure if that just happened by chance, because V2 had also worked for me before but did not work when testing it again today.

Please confirm after download that sha256 of the firmware image is: 8FBDEAF722EB2F5467E2A7D39D21C2ABB2C38460FE28980EEB18ACACA622CA47

AlexaEnhancementV2

06 Feb 23:34
Compare
Choose a tag to compare
AlexaEnhancementV2 Pre-release
Pre-release

Call different presets "by name" using Alexa Echo devices, e.g. "Alexa, turn Rainbow on", "Alexa, turn Firework on" etc. This is achieved by creating individual Alexa devices for up to 9 presets in addition to the one configured in WLED's Alexa configuration.

Usage instructions:

  1. Disable Alexa in WLED.
  2. Name the presets (IDs 1 up to 9) like you want to call them when using Alexa, e.g. Rainbow, Firework, Knight Rider, ...
  3. Re-enable Alexa in WLED.
  4. Delete all devices in Alexa that already exist for this WLED device (including the one configured in WLED's Alexa configuration) and then let Alexa search for devices again. You do not need to delete existing devices if you did not edit existing names/preset IDs but just added new presets. Deleting is mandatory if you used version AlexaEnhancementV1 before.
  5. Switch on your presets by simply calling them by their name, e.g. "Alexa, turn Rainbow on". Switch to another preset by simply calling it by another name, e.g. "Alexa, turn Firework on". Use any name for switching off. Additionally the original device exists, that you configured in WLED's Alexa configuration.
  6. Repeat steps 1 to 5 whenever you change preset names/IDs in WLED.

Of course you may try my code or flash the provided D1 mini firmware if you consider this functionality useful. The same license and disclaimer apply as given for the original WLED project. Be aware that I'm far less familiar with the code than the original authors, so - although it works for me - the risk for harmful bugs may be higher. E.g. sometimes I got a "Cannot connect to light" error after flashing (which may be caused by my quite "experimental" wiring instead of using the right connector), but after a reboot all worked fine afterwards.

AlexaEnhancementV1

05 Feb 00:22
Compare
Choose a tag to compare
AlexaEnhancementV1 Pre-release
Pre-release

Call different presets "by name" using Alexa Echo devices, e.g. "Alexa, turn Rainbow on", "Alexa, turn Firework on" etc. This is achieved by creating individual Alexa devices for up to 9 presets in addition to the one configured in WLED's Alexa configuration.

Usage instructions:

  1. Disable Alexa in WLED
  2. Name the presets (IDs 1 up to 9) like you want to call them when using Alexa, e.g. Rainbow, Firework, Knight Rider, ...
  3. Re-enable Alexa in WLED
  4. Delete all devices in Alexa that already exist for this WLED device (including the one configured in WLED's Alexa configuration) and then let Alexa search for devices again
  5. Switch on your presets by simply calling them by their name, e.g. "Alexa, turn Rainbow on". Switch to another preset by simply calling it by another name, e.g. "Alexa, turn Firework on". Use any name for switching off. Additionally the original device exists, that you configured in WLED's Alexa configuration.
  6. Repeat steps 1 to 5 whenever you change preset names/IDs in WLED.

Of course you may try my code or flash the provided D1 mini firmware if you consider this functionality useful. The same license and disclaimer apply as given for the original WLED project. Be aware that I'm far less familiar with the code than the original authors, so - although it works for me - the risk for harmful bugs may be higher. E.g. sometimes I got a "Cannot connect to light" error after flashing (which may be caused by my quite "experimental" wiring instead of using the right connector), but after a reboot all worked fine afterwards.