supported_hardware:alexa
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| supported_hardware:alexa [2020/02/21 14:39] – edited to add limitation to a single instance of the plugin now. James Sentman | supported_hardware:alexa [2023/02/13 14:52] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| * the simplest solution is to find a generation 1 Echo device on ebay or elsewhere. Note that many that are labeled as such actually aren’t as people don’t really know what they are selling and are re-using descriptions from other similar devices. Please make sure you can identify a version 1 device! It will have the bezel that you can physically turn to change the volume. If if has buttons to adjust the volume then it is not a generation 1 device and will not solve your problem. These gen 1 devices are not eligible for the newer software updates and therefore will not automatically receive the update that breaks everything. Once you have one on your network you can do the discovery for new devices through it and not through one of your newer devices. When that is working all communications to the shared units will go through this older device even if you issue the command from a newer device also on your network. This works without having to make any other changes to your system usually though you may have to re-discover all your units through the new/old device. | * the simplest solution is to find a generation 1 Echo device on ebay or elsewhere. Note that many that are labeled as such actually aren’t as people don’t really know what they are selling and are re-using descriptions from other similar devices. Please make sure you can identify a version 1 device! It will have the bezel that you can physically turn to change the volume. If if has buttons to adjust the volume then it is not a generation 1 device and will not solve your problem. These gen 1 devices are not eligible for the newer software updates and therefore will not automatically receive the update that breaks everything. Once you have one on your network you can do the discovery for new devices through it and not through one of your newer devices. When that is working all communications to the shared units will go through this older device even if you issue the command from a newer device also on your network. This works without having to make any other changes to your system usually though you may have to re-discover all your units through the new/old device. | ||
| * If you do not require port 80 standard web services on your XTension server you can now run the new [[supported_hardware: | * If you do not require port 80 standard web services on your XTension server you can now run the new [[supported_hardware: | ||
| - | * If you do require the standard web port on your XTension mac or you need multiple instances of the plugin to share all the units that you wish to then you can run more instances of the plugin on separate machines. This will work from extra Macs or more easily by putting the plugin code onto a Raspberry Pi. This solution is not released yet, but is available if you contact me directly via email. | + | * If you do require the standard web port on your XTension mac or you need multiple instances of the plugin to share all the units that you wish to then you can run more instances of the plugin on separate machines. This will work from extra Macs or more easily by putting the plugin code onto a Raspberry Pi. See the [[supported_hardware: |
| ----- | ----- | ||
supported_hardware/alexa.1582295987.txt.gz · Last modified: 2023/02/13 14:51 (external edit)