search

originallyus / node-red-contrib-alexa-local

An easy-to-use NodeRED node for adding Alexa capability to NodeRED. NO Alexa Skills required.
106 stars 25 forks source link

Room Awareness #65

Closed skavan closed 5 years ago

skavan commented 5 years ago

Is there any way for this excellent node, to pass the id of the alexa that is sending the message. This way we could implement sophisticated room awareness...

Thanks.

torinnguyen commented 5 years ago

I probably can pass the IP address of the Alexa that is sending the request, but to implement room awareness (aka Alexa isolation) is not that simple.

On Sun, 26 Aug 2018 at 06:27, skavan notifications@github.com wrote:

Is there any way for this excellent node, to pass the id of the alexa that is sending the message. This way we could implement sophisticated room awareness...

Thanks.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/originallyus/node-red-contrib-alexa-local/issues/65, or mute the thread https://github.com/notifications/unsubscribe-auth/AAu1WF83mkxuF4L6SVnpynZw0mxJtxhGks5uUd1zgaJpZM4WMko5 .

-- http://originally.us

skavan commented 5 years ago

Either IP Address or Alexa Id would be cool, because then we could implement "room awareness" inside of node-red. i.e. "Alexa, turn on the lights" from the Living Room, would trigger the flow with a payload that included the alexa ip. Presumable, based on that ip address I can then trigger the Living Room lights from within node-red? This is even better than the Alexa based groups which are flaky and start to come unstuck when there are more than one set of lights within a room (bedside lights, main lights) that need individual control!

Hope that makes vague sense.

s.

On Sat, Aug 25, 2018 at 9:08 PM Torin Nguyen notifications@github.com wrote:

I probably can pass the IP address of the Alexa that is sending the request, but to implement room awareness (aka Alexa isolation) is not that simple.

On Sun, 26 Aug 2018 at 06:27, skavan notifications@github.com wrote:

Is there any way for this excellent node, to pass the id of the alexa that is sending the message. This way we could implement sophisticated room awareness...

Thanks.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://github.com/originallyus/node-red-contrib-alexa-local/issues/65 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AAu1WF83mkxuF4L6SVnpynZw0mxJtxhGks5uUd1zgaJpZM4WMko5

.

-- http://originally.us

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/originallyus/node-red-contrib-alexa-local/issues/65#issuecomment-416006654, or mute the thread https://github.com/notifications/unsubscribe-auth/ACcHOWg4u5bnvoOFDjQtN0_Vl2Gfh0eiks5uUfUFgaJpZM4WMko5 .

torinnguyen commented 5 years ago

There is a 'from' parameter in output message in the latest version 0.3.24. Please give it a try.

skavan commented 5 years ago

Thanks. I've created a couple of nodes and wandered around the house barking instructions at various Alexa's. The commands are coming through fine, but the ip address is always the same: 192.168.1.71. This ip address is the ip address of one of the Alexa's. Neither the first one I spoke to, nor the last. mmmh...

skavan commented 5 years ago

mmmh- this thread has some clues: https://github.com/mabunixda/node-red-contrib-alexa-home/issues/4 Alexa now supports location awareness....but how we get that data is not clear to me.

torinnguyen commented 5 years ago

Using Alexa Skills in the cloud is different from what is being implemented locally with my node.

I know Home Assistant platform has Alexa Isolation feature, but it requires the separation during discovery phase, not later. Meaning, it's masking the Alexa virtual devices, forcing certain Echo to only see certain virtual devices.

This approach has problem. Echo Plus and Echo Gen 2 are not supported by my node. Using that approach won't work for all devices.

On Wed, Aug 29, 2018 at 5:46 AM skavan notifications@github.com wrote:

mmmh- this thread has some clues: https://github.com/mabunixda/node-red-contrib-alexa-home/issues/4 http://url Alexa now supports location awareness....but how we get that data is not clear to me.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/originallyus/node-red-contrib-alexa-local/issues/65#issuecomment-416764968, or mute the thread https://github.com/notifications/unsubscribe-auth/AAu1WMqkpbthFr-Yg9dO4vGB1CB6hiNvks5uVcgrgaJpZM4WMko5 .

-- http://originally.us

MattL0 commented 5 years ago

So with this node Alexa talsk directly to nodered ? By upnp?

I am using homeseer mychs c’oud wich is really fast.

So, does this plugin add any delais with upnp?

MattL0 commented 5 years ago

I would also like to know, Would it be possible to add a node wich would act as a scene ?

Like that, i would not have to rethink all my alexa settup .

torinnguyen commented 5 years ago

Alexa talks directly to NodeRED via my node. That's correct. By UDP/SSDP/Hue protocol. You can google for more information about Hue emulation implementations.

You can use Routines feature in Alexa app instead of Scenes.

On Wed, Aug 29, 2018 at 10:48 AM MattL0 notifications@github.com wrote:

I would also like to know, Would it be possible to add a node wich would act as a scene ?

Like that, i would not have to rethink all my alexa settup .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/originallyus/node-red-contrib-alexa-local/issues/65#issuecomment-416814864, or mute the thread https://github.com/notifications/unsubscribe-auth/AAu1WGCtiFqltJ8smPvdafmAfU11jPSGks5uVg7zgaJpZM4WMko5 .

-- http://originally.us