-
Notifications
You must be signed in to change notification settings - Fork 195
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
Echo Dot Gen 3 Compability #61
Comments
I have seen this js happening in latest firmware updates from Amazon.
Have you tried using the Sinric Skill? Sinric.com
…On Fri, 2 Nov 2018 at 5:14 AM fhschmitt85 ***@***.***> wrote:
The code itself seems to work fine with Amazon Dot Generation 3. There are
no problems adding new devices in the Alexa App.
But there are apparently communication probelms. If you are giving
commands for switching operation, the MCU runs the callback functions and
sends the proper xml file to Alexa. Alexa did not response immediately and
states finally that there is a problem with the device. After some
getBinaryState requests the Alexa App shows the right device state.
Does anyone have an idea dealing with this issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#61>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHIM5qzfkjX8QCneLeddEmFfPcN--tReks5uq3IugaJpZM4YJt5_>
.
|
Not yet. |
@fhschmitt85 Using skills and AWS IoT is also my plan, as MQTT will be usefull for all kind of devices ! Like if you design a connected switch using AWS IoT and your skill you have to tell "Alexa, ask {my_skill} to turn on the switch" Is it true or do you have an idea to make your items recognized as smart home object ? So it will be possible to say directly "Alexa, turn on the switch" |
If you are using a smart home skill, you don’t have to use the skill name
in front. You can just say Alexa, turn on the tv
…On Wed, 28 Nov 2018 at 9:18 PM Pierre-Marie Ancèle ***@***.***> wrote:
@fhschmitt85 <https://github.com/fhschmitt85> Using skills and AWS IoT is
also my plan, as MQTT will be usefull for all kind of devices !
But i understood that when creating a skill you have to use its name
before each Alexa command ..
Like if you design a connected switch using AWS IoT and your skill you
have to tell "Alexa, ask {my_skill} to turn on the switch"
Is it true or do you have an idea to make your items recognized as smart
home object ? So it will be possible to say directly "Alexa, turn on the
switch"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHIM5oMyhy_KNyNu_R2f9OmprAdJxyClks5uzpsXgaJpZM4YJt5_>
.
|
I had the same issue with 3 gen dot echo, commenting several Serial.println (above all in the UPNPBroadcasterResponder file) improved Alexa's response speed a lot |
Hello, |
Have you tried Sinric skill?
…On Tue, 26 Mar 2019 at 7:54 PM Arkajyoti Chatterjee < ***@***.***> wrote:
Hello,
I have an Echo Dot Generation 3. The same code was working flawlessly with
Echo Dot Generation2 but the 3rd generation seems not to find / discover
any devices.
The Smart Home Skill I am using is YeeLight ( both in Gen2 and Gen3).
Any help would be appreciated.
Thanks,
Arka
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHIM5lRFRto-RN0aGrZcTNf-Am3Huvdfks5vahiagaJpZM4YJt5_>
.
|
Hello Aruna, |
This is kind of the reason why I made the skill. New Alexa updates stopped
sending the UDP unicast on the network
Do you see the Alexa UDP requests in the Serial terminal? If not using the
skill is your only option
…On Tue, 26 Mar 2019 at 8:12 PM Arkajyoti Chatterjee < ***@***.***> wrote:
Hello Aruna,
I wanted to use this multiple wemo code. So any way to make that happen?
Thanks ,
Arka
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHIM5smMN0mq82e12DH_s5um-WdxGHPsks5vahy1gaJpZM4YJt5_>
.
|
Hi, I am also facing the same issue. I have enabled sinric skill also. Thanks, |
@sourabhjaiswal emulating a Belkin switch is unpredictable now. You should consider switching to Sinric Pro Skill (https://sinric.pro) . |
Hi Kakopappa, Thanks a lot for the update. Regards, |
try Home Assistant or domoticz |
The code itself seems to work fine with Amazon Dot Generation 3. There are no problems adding new devices in the Alexa App.
But there are apparently communication probelms. If you are giving commands for switching operation, the MCU runs the callback functions and sends the proper xml file to Alexa. Alexa did not response immediately and states finally that there is a problem with the device. After some getBinaryState requests the Alexa App shows the right device state.
Does anyone have an idea dealing with this issue?
The text was updated successfully, but these errors were encountered: