search

datech / node-red-contrib-amazon-echo

Alexa controlled Node-Red nodes supporting latest Amazon Echo devices. NO Alexa Skills required. NO cloud dependencies.
MIT License
140 stars 42 forks source link

Device is not responding / Waiting for Royal Philips Electronics... #177

Closed jeroenst closed 3 years ago

jeroenst commented 3 years ago
SUMMARY

I could control my devices without problem but now suddenly all devices are unresponsive. Discovery works although alexa always finds a device which has already been removed. When I open port 80 I see the module responding with Cannot GET /

Is there any way how I can debug my issue?

ECHO DEVICES
0.1.10
CONFIGURATION
CONSOLE OUTPUT
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
jeroenst commented 3 years ago

I did reset Alexa and it works fine now

Barabba11 commented 3 years ago

I had similar issues, reset helped but after some time it happened again. I wish you not. I think the recent FW of ALexa doesn't manage this protocol well, that's strange because we suppose the Philips bulbs don't have FW update and change the protocols, but this is the reality. This is why I moved to another node and I'm happy, it also much better supprt duplicated names (2 word commands like "kitchen curtains" when there are "kitchen lights" and "bedrooms curtains"). Good luck

jeroenst commented 3 years ago

@Barabba11 which node do you use at this moment?

Barabba11 commented 3 years ago

https://github.com/datech/node-red-contrib-amazon-echo/issues/172

pangklee commented 3 years ago

@jeroenst I’m running into the same issue. What do you mean by reset? Did you delete and rediscover your devices?

jeroenst commented 3 years ago

Hi @pangklee, see: https://www.the-ambient.com/how-to/reset-amazon-echo-1268

pangklee commented 3 years ago

@jeroenst Thanks for the link. I’ll keep this in mind next time this happens. Really odd, my echo devices just started working again this afternoon without any changes after running into this issue for the past 3 days