-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable/Disable of device nodes #17
Comments
thank you dear friend, because I just tried to create a new flow and insert there the new devices, disabled the first flow, but the scond Alexa found me instead all devices of the first flow.. |
My friend, thinking about it I think the solution (which is welcome!! For different reasons) do not solve the problem with 2 Alexa into the same network. You can disable and discover, but there will be the unlucky day that you or someone else says "Alexa find new peripherals", it will add the other items configured in node red.. This you have a flat with 2 floors, in everyone you put an echo plus, in both apartments you have light of bathroom, ventilation, etc etc, you would be tempted to use the same names.. and after there will be conflict or undesidered switch on. |
Enable/disable functionality has to be sufficient to cover this case, as the devices are identified by ID. The device name is used only for voice commands, which are later translated to API calls using device ID instead of name. |
Frankly I have to say you that's not, unfortunately, I thought about it later, in experimental way yes.. I have about 40 nodes, a bit long to open all of them and disable, recognise the new ones on the second Alexa, and enable all 40 again, but in the reality.. can be for a mistake I say Alexa "find new devices" and all this effort with be lost.. |
@Barabba11 May be #22 could be a good solution? |
Thanks again, I don't think so because in this way I can't avoid the second Alexa to recognize the devices of the Alexa1, and there will be the same names, Ican't use the same name twice: |
Mate I tried to open your script to try to help you, but there I cannot find the http server code, am I wrong? |
I'm back on this again after another work I finished, I would analize the http server and try to change it somehow.. to see if it is possible to filter the alexa by IP or mac address.. But I can't find the sources of http server. Maybe it is using system's libraries for that? |
I had an idea of sub-hubs that might resolve your issue. I will try to implement it for the next version. |
Hi my friend! Do you have any news here? Can I help you somehow? |
Hi mate, I really need your help, any progress about this? Can I help you? I really would like to help! |
I'm kindly wait for your help, I hope all is ok with you and you can support us in future! PLease let us know, thank you! Thank you a lot! |
Very interesting post that can help:
|
Add feature to enable/disable device nodes.
If device node is disabled, Alexa will not be able to:
All disabled devices that are already discovered will show an error: "Server is not responsive" or |Device malfunction" in the Alexa app
The text was updated successfully, but these errors were encountered: