Smart Plug not detected by Alexa

[Joel Ashman]

Hello,

I have flashed two Brilliant smart plugs with Tasmota 6.5.0 basic

I can access the web interface, and have set them both to PowerOnState 1 so that they turn on by default.

I have the template saved and activated for the Brilliant device

However, my Amazon Echo Plus can't discover them on my network.  

Is there a trick to this, or some missing setting?  I have enabled both Belkin and Hue emulation, and neither work.  I've followed the advice in the wiki, but nothing seems to work.

Cheers

[Phil]

FYI since i have node red hosted alongside mosquitto mqtt broker on a pi-0-w creating a device instance that alexa can discover and turn on/off involves adding an Alexa-local node to a flow  and connect it to an MQTT publish node to issue/relay the command to the device.

https://flows.nodered.org/node/node-red-contrib-alexa-local

This is a dead-simple node for adding Alexa capability to your flow.
NO extra Alexa Skills required.
NO account linking required.

How to use

• Add this node to your flow
• Give it a unique Name
• Ask "Alexa, discover devices"
• That's it!

[Joel Ashman]

Hi,

Thanks for the response.

This link
https://github.com/arendst/Sonoff-Tasmota/wiki/Alexa

Seems to indicate that Alexa should be able to communicate with the device directly.  Am I wrong in my interpretation of that?

"To control a Tasmota device with Alexa, enable emulation (Configure Other on the Tasmotat web UI).

Use Belkin WeMo for devices with a single relay or Hue Bridge for devices with one or more relays or for lights. Tasmota devices will be discovered by the Alexa app."

Cheers,

Joel

[Michael Ingraham]

What version of Tasmota is on your device. Recent Alexa changes changed discovery of emulated devices . The newest development version of Tasmota is updated to work with the Alexa update.

--
You received this message because you are subscribed to the Google Groups "SonoffUsers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonoffusers...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/sonoffusers/90bf1cd6-6b71-4762-8c06-7b014ba7401a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Joel Ashman]

I've just loaded 6.5.0.13 on to the device.  Problem still remains

To unsubscribe from this group and stop receiving emails from it, send an email to sonof...@googlegroups.com.

[Michael Ingraham]

Can you give Hue emulation (even if it says single relay, etc.) a try just to eliminate/confirm if the problem is exclusively Wemo emulation?

Mike

To unsubscribe from this group and stop receiving emails from it, send an email to sonoffusers...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/sonoffusers/0bd6c05b-4e6b-4fa6-82fa-6d5d158f411f%40googlegroups.com.

[Joel Ashman]

I already had Hue emulation set, but to be sure, i've just:

selected wemo emulation, saved, waited for device to come online, then tried alexa discovery

selected hue emulation, saved, waited for device to come online, then tried alexa discovery

with both methods, i've tried the following -setting up as "other device" in Alexa.  Then i tried choosing "plug" -> other in Alexa.  I've tried choosing Light ->philips Hue.  Same issue.  No new devices found

Could it be a core binaries issue?

[Michael Ingraham]

It appears so. There's been a lot of activity around Tasmota Hue emulation to add support for lights. Perhaps some issue has been introduced in the process. Please open a Tasmota GitHub issue, complete the template thoroughly, and provide the information on the testing you've performed. I would encourage you to include a reference to @s-hadinger as he has been heavily involved in these latest Hue emulation updates.

Mike

Michael Ingraham
Spartanburg, SC

To unsubscribe from this group and stop receiving emails from it, send an email to sonoffusers...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/sonoffusers/0b720dc7-8c65-4849-9617-dfa6bcffcb74%40googlegroups.com.

[Michael Ingraham]

Joel,

As Jason suggests, give the very latest development branch version a try. There was a bug in the Device ID hashing that was modified.

Mike

[Michael Ingraham]

For anyone stumbling on this thread, the issue was related to network configuration. Changing to a wireless router that allows multicast resolved the issue.