search

originallyus / node-red-contrib-alexa-local

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

more than one device on one bridge #29

Closed martinschki closed 6 years ago

martinschki commented 6 years ago

I know its on your todo, but do you have a timeline here?

Thanks for the awesome node!!!

torinnguyen commented 6 years ago

Why exactly do you need this feature? It is more of an optimization rather than a new feature. It does not affect how you would use the node from user point of view.

On Nov 25, 2017 1:17 AM, "martinschki" notifications@github.com wrote:

I know its on your todo, but do you have a timeline here?

Thanks for the awesome node!!!

— 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/29, or mute the thread https://github.com/notifications/unsubscribe-auth/AAu1WIU8QV0cmAVtgDUeii1me5cVJLxRks5s5wgjgaJpZM4QqGGt .

martinschki commented 6 years ago

Ok, let me rephrase my question. If adding lots of devices, would that have a negative impact in the systems / networks performance compared to lets say 20 devices per bridge?

torinnguyen commented 6 years ago

It is definitely better for system performance when 25 devices (max) are hosted on 1 bridge. However the implementation is challenging and I have not thought to a way to keep the configuration of the node as idiot-proof as it is now.