what is the unique identifier between alexa and fauxmo? How does fauxmo know what device alexa wants to talk to through fauxmo?
Imagine, i want to build a fauxmo device which is connected via 868mhz to different nodes. how does fauxmo know which of these device alexa wants to talk to? is it the name of the fauxmo device? is it the id?
if it is the id: it seems that it is not possible to set the fauxmo id during fauxmo device creation. if i have some nodes and existing pairing info and I want to load those settings and initialize the fauxmo devices accordingly, the IDs might get mixed up.
any thoughts?
Comments (2)
Lucas Neumann REPORTER
ok, dug a bit deeper into this. it all seems to come down to the fauxmo id which is the index of the vector _devices. that's not really pretty, allthough it seemed reasonable for the initial scope of fauxmoesp.
in my scenario, where I'm adding and removing alexa-capable nodes to and from my 868mhz rf gateway, the fact that the fauxmo ID changes everytime messes everything up.
do you think you might implement something like persistent IDs for the fauxmo devices or would I be better off to make my own version of this library which suits my needs? not completely sure though, how I'd realize my requirement in an elegant way. don't really want to end up for looping through the _devices vector all the time, searching for the correct id....
2019-04-20
Lucas Neumann REPORTER
as there was no reaction whatsoever, I did copy the fauxmo library locally on my pc and did the modifications for the persisting ID thing. works like a charm but is quite a change so I guess that won't make it into the official library.
Issue imported from: https://bitbucket.org/xoseperez/fauxmoesp/issues/89
Lucas Neumann created an issue 2019-04-20 Hi
what is the unique identifier between alexa and fauxmo? How does fauxmo know what device alexa wants to talk to through fauxmo?
Imagine, i want to build a fauxmo device which is connected via 868mhz to different nodes. how does fauxmo know which of these device alexa wants to talk to? is it the name of the fauxmo device? is it the id?
if it is the id: it seems that it is not possible to set the fauxmo id during fauxmo device creation. if i have some nodes and existing pairing info and I want to load those settings and initialize the fauxmo devices accordingly, the IDs might get mixed up.
any thoughts?
Comments (2) Lucas Neumann REPORTER ok, dug a bit deeper into this. it all seems to come down to the fauxmo id which is the index of the vector _devices. that's not really pretty, allthough it seemed reasonable for the initial scope of fauxmoesp.
in my scenario, where I'm adding and removing alexa-capable nodes to and from my 868mhz rf gateway, the fact that the fauxmo ID changes everytime messes everything up.
do you think you might implement something like persistent IDs for the fauxmo devices or would I be better off to make my own version of this library which suits my needs? not completely sure though, how I'd realize my requirement in an elegant way. don't really want to end up for looping through the _devices vector all the time, searching for the correct id....
2019-04-20 Lucas Neumann REPORTER as there was no reaction whatsoever, I did copy the fauxmo library locally on my pc and did the modifications for the persisting ID thing. works like a charm but is quite a change so I guess that won't make it into the official library.
2019-04-21