Comments (3)
Well, I asked the same..
chances are Echo devices becoming cheaper, it would lovely to have other Echo in other rooms/floors.. but only one Wifi, and only one Raspberry running Node Red an all automations needed.. and say to every floor "Alexa turn down curtains".. but only curtains of that room/floor will go down..
Unfortunately Alexa will search for devices on port 80 on all the IP domain broadcast.. so if we this module running all the Alexa in that WiFi will recognize all devices that are connected to the Echo HUB in Node Red..
yes we can delete it by our app later.. or disable the undesidered devices before discovering (I have around 50!), but if one day wrongly we say to one Alexa "Alexa find new devices" it will search all IP again and find all, and our list will be dirty again. And what about if we use the same names? For example "curtains"? Wich one has to be deleted? Which one appear in the list is the one of the second floor?
Even if we use multiple IP addresses on Raspberry and open for each IP an 80, to be routed somehow to the main IP with a different TCP, and load on that TCP a different Echo HUB in Node red, the Alexa will anyway find all the Eco HUBS and all devices too.. because it scans all the IP of the domain, so it's not a solution.
The only way we have is to chose/filter the Echo device on the http server (by its IP or MAC address) and let that Echo recognize only the devices connected to it (on that HUB on Node Red).
Possible solution:
It may be possible to change a bit the http server to pass also the source IP address of the Alexa incoming, or its MAC address, on Node red the Echo HUB device can contain a field to specify the Echo IP address, this HUB will talk only to that IP address, and let that Echo only recognize the devices connected to that Echo HUB.
We ma add then a second Echo HUB with the IP address of the second Alexa, and connect to it only the devices that the second Alexa should recognize and control.
A device may be connected to two hubs and be recognized and controlled by both.. but this is not mandatory of course
Thank you a lot for considering this
PS: filtering by IP address may be easier to implement, but router can give another day another IP address.. and our Node Red will not work more with that Alexa. We should then reserve an IP address in DHCP of our router to avoid this, maybe some routers don't have this feature. A MAC address can't be changed, so it's more safe to use that, but maybe more complicated to implement
from node-red-contrib-amazon-echo.
I'm not aware of a way to distinguish Amazon Echo devices, because usually all requests are routed trough the master Echo device.
from node-red-contrib-amazon-echo.
It's just needed to use two different Amazon accounts, one for every Echo.
Filter can be set on every device by IP address, hub will pass source IP address to device, if it doesn't match the device will not reply
Thank you
from node-red-contrib-amazon-echo.
Related Issues (20)
- Amazon Alexa Fire Cube kann keine Geräte finden. HOT 5
- Button Entity HOT 1
- Defining different types of devices HOT 3
- node-red-contrib-amazon-echo has 2 Versions? HOT 1
- Device Unresponsive - not all but most "lights" HOT 2
- Alexa says "I'm not quite sure what went wrong" for most commands HOT 1
- alexa discovery not working (NOT USING Home Assistant)
- Add other home assistant entity types HOT 2
- Issue with setting / dimming to 0% HOT 1
- Empty Message from Alexa HOT 1
- New speach feature HOT 2
- Existing devices are "unresponsive" and cannot add new devices HOT 1
- Amazon Echo Hub, Amazon Echo Device on Home Assistant using Node Red (Devices Not Discovered) HOT 3
- Feed brightness % in from MQTT HOT 1
- set color white - does not update hue number
- Issues with dimming, payload is always "on" HOT 3
- Passing Object Status back to Alexa from Home Assistant HOT 1
- Get Alexa Device ID (in msg object) HOT 1
- Suddenly all the virtual devices from Node Red are not available anymore HOT 2
- How to install this plugin in a docker container HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-red-contrib-amazon-echo.