Skip to content
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

Alexa devices getting mixed up and controlling other espurna devices #1738

Closed
clueo8 opened this issue May 25, 2019 · 14 comments
Closed

Alexa devices getting mixed up and controlling other espurna devices #1738

clueo8 opened this issue May 25, 2019 · 14 comments
Labels

Comments

@clueo8
Copy link

clueo8 commented May 25, 2019

All of a sudden my sonoffs with espurna 1.13.3 stopped working reliably with Alexa (haven't updated or touched config in months). I tried adding/removing from Alexa and rediscovered them but it appears they are crossing paths now. For example, I have a few sonoff basics and a dual. Alexa finds them all but when it discovered the basic, turning the basic on and off is actually controlling one of the dual switches! It's like Alexa is mixing up the devices. I updated the dual to 1.13.5 to see if that would help but it didn't. HA is able to control them fine still, just the Alexa is messed up now...

@Alferez
Copy link

Alferez commented May 25, 2019

I have the same problem since Wednesday when I saw that alexa lit her circle of light alone. It seemed like it was updating.
I have tried to delete the devices in alexa and rediscover them, but it keeps on turning on and off the ones you want without having anything to do. My version is 1.13.5 and my Echo Dot 3rd firmware version is 2382875524

@clueo8
Copy link
Author

clueo8 commented May 26, 2019

I did notice my Echo Show updating last week as well...

@mcspr mcspr added the alexa label May 26, 2019
@jemarr
Copy link

jemarr commented May 27, 2019

Seems that all Hue emulators has the same issue....
Fauxmo, Espalexa, Tasmota,...

Aircoookie/Espalexa#72

arendst/Tasmota#5849

Aircoookie/Espalexa#71

@jemarr
Copy link

jemarr commented May 27, 2019

Same problem since five days ago... Amazon has changed something.

I tried Fauxmo, Espalexa libs as well with same issue.

I have three ESP8266 boards with 1, 2 and 4 devices each. The last discovered devices board is which Alexa takes as 1st, 2nd.... device on Routines and Groups, doesn't matter the device name.

When you call by voice all devices runs well, the problem is just with Groups and Routines.

I've 2 Echo Dot 3rt Gen.

@rmcbc
Copy link
Contributor

rmcbc commented May 28, 2019

I have the same problem, probably a Alexa update, everything was working ok, now it's all mixed.
Does any one knows how to solve this?
I have 2 Alexa Echo Dot 2nd Gen. with the same problem.

@anrada73
Copy link

in Germany too.(

@rmcbc
Copy link
Contributor

rmcbc commented May 29, 2019

I install 1.13.2 and it seems to work, I have only one device active, but it works, I give more feedback when I flash all the other modules.
Wemo emulation seems to work. I don't know the code, but I'm going to try to replace Philips by Wemo.

@rmcbc
Copy link
Contributor

rmcbc commented May 29, 2019

After configuring the firmware for more than 30 devices all are working ok with firmware 1.13.2
The Wemo emulation works and for me it's better because you can chose if the device is a light or a plug.
@xoseperez if it's possible make it possible to compile Wemo or Philips emulator with latest version, I don't know if I'm asking too much but I think it's a good thing to make it possible to choose one emulation or the other.
Thanks for your great job.

@jemarr
Copy link

jemarr commented May 31, 2019

With Tasmota they have found a solution. What they do to solve the issue is to assign a unique LightId for each device based on the iP adress or MAC adress of the esp8266 board.

arendst/Tasmota#5890 (comment)

Is it possible to do the same with Espurna o Fauxmo lib ???

@PieBru
Copy link

PieBru commented Jun 3, 2019

+1 for a solution non involving the DHCP variable part of the IP address.
IMO, fixed definitions cause maintenance workload over time, I prefer plug & play things.
Let's make DHCP things and Alexa happy toghether :)
Piero

@rmcbc
Copy link
Contributor

rmcbc commented Jun 3, 2019

Use MAC address is diferent for each device and don't change with DHCP.

@PieBru
Copy link

PieBru commented Jun 4, 2019

Even the MAC address can change when the LAN isn't wired or 802.11s
In my experience, some WDS implementations are flawed and don't solve completely the variable-MAC problem.
Piero

@jemarr
Copy link

jemarr commented Jun 16, 2019

Amazon already fixed the issue... now is working fine again.

@clueo8
Copy link
Author

clueo8 commented Jul 5, 2019

Confirmed; I'm not having this issue anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants