User Tools

Site Tools


supported_hardware:alexasudo

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
supported_hardware:alexasudo [2020/02/19 17:19] – created James Sentmansupported_hardware:alexasudo [2023/02/13 14:52] (current) – external edit 127.0.0.1
Line 1: Line 1:
 =====Amazon Alexa Bridge run as Sudo===== =====Amazon Alexa Bridge run as Sudo=====
 +
 +-----
 +**NOTE:** this plugin now requires Python3. This is not installed by default on MacOSX. If you have not already installed it for other plugins, please visit the [[https://www.python.org/downloads/mac-osx/|Python.org Download Page]] and install the latest version of python3 before running this plugin. You can verify that it is installed or not by opening a Terminal window and typing “python3” if you get a not found error then you need to do the above install.
 +-----
  
 The non-cloud based solutions for letting Home Automation systems be controlled from Amazon’s Alexa devices have always relied on emulating another device that Amazon supports directly. Yes it requires a working internet connection to do the voice recognition, but to then do yet another trip up to the cloud, run a huge amount of code, and then send a result back to control a device that is sitting literally 2 feet from your XTension server has always driven me insane as to the stupidity of that plan. The non-cloud based solutions for letting Home Automation systems be controlled from Amazon’s Alexa devices have always relied on emulating another device that Amazon supports directly. Yes it requires a working internet connection to do the voice recognition, but to then do yet another trip up to the cloud, run a huge amount of code, and then send a result back to control a device that is sitting literally 2 feet from your XTension server has always driven me insane as to the stupidity of that plan.
Line 14: Line 18:
  
 ====Create The Interface==== ====Create The Interface====
-If you already have an Alexa interface that stopped working when your Alexa device updated itself you can simply change the plugin type popup from the old Alexa plugin to the “Alexa Plugin With Sudo” and save it. If you’re creating a new interface select the new Sudo Alexa plugin from the start and then follow the original Alexa plugin setup instructions as linked to above.+If you already have an Alexa interface that stopped working when your Alexa device updated itself you can simply change the plugin type popup from the old Alexa plugin to the “Alexa Plugin With Sudo.” Make sure to change the port number to 80 and save it. If you’re creating a new interface select the new Sudo Alexa plugin from the start and then follow the original Alexa plugin setup instructions as linked to above. The default for a new interface should be port 80 as well but verify as that is the only number that will work.
  
 Save the interface before continuing, but do not yet try to enable the interface. Save the interface before continuing, but do not yet try to enable the interface.
Line 87: Line 91:
 Once your devices are back you can re-setup any special phrases or other groups and scenes and such that you had working previously. Once your devices are back you can re-setup any special phrases or other groups and scenes and such that you had working previously.
  
-====Hstory:====+====History:====
 The sudo capable Alexa plugin was first included in XTension 9.4.28 released towards the end of February 2020. The sudo capable Alexa plugin was first included in XTension 9.4.28 released towards the end of February 2020.
supported_hardware/alexasudo.1582132765.txt.gz · Last modified: 2023/02/13 14:51 (external edit)