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

Device could only be switched a few times #151

Closed
Aendrew87 opened this issue Nov 13, 2020 · 7 comments
Closed

Device could only be switched a few times #151

Aendrew87 opened this issue Nov 13, 2020 · 7 comments

Comments

@Aendrew87
Copy link

Aendrew87 commented Nov 13, 2020

Hi, I have a issue like discuessed in #150.

Environment:

  • Tasmota-Devices (Tasmota 8.5.0 by Theo Arends) with emulation (Belkin WeMo single device)
  • ioBroker (4.0.10) with node-red (1.2.2) and sonoff (2.3.3) on a pi 4 4GB
  • node-red-contrib-amazon-echo (0.1.10) (Amazon Echo Hub is running on port 80)
  • Echo Dot (3. Gen.)
  • Fritz!Box 7490 (no VLANs)

I tried to switch the Tasmota-Devices using Alexa app on my phone but after switching them off i could not switch them on.
After waiting a few hours switching on is possible for a few times und then i get error "Das Geräte reagiert nicht" (the device is not responding).

So i used node-red-contrib-amazon-echo to create a new device and switch the Tasmota-Devices using sonoff.
This is working for a few switches und then i also get error "Das Geräte reagiert nicht" (the device is not responding).

I used Amazon Smart Plug in the Alexa app to and this device is switching all the time without any error.

How could i debug / see the requests send to the Amazon Echo Hub?

@jeroenst
Copy link

jeroenst commented Oct 4, 2021

I have the same issue, how did you solve this?

@Aendrew87
Copy link
Author

@jeroenst my problem was, that alexa controlles the devices.
When disconnecting the alexa, which is managing the connections, it is not possible to control the switches.

Solution: Just dont disconnect the "main" alexa.

@Barabba11
Copy link

Solution2: leave this, use virtual smart home node and subscribe each echo to the same account. Switch off any Echo and keep it running

@jeroenst
Copy link

jeroenst commented Dec 4, 2021

Unfortunately I can't use virtual smart home, I get this error in Amazon:
You are not eligible to enable this skill due to geographical restrictions.
I live in the Netherlands...

@Barabba11
Copy link

Not all languages are supported, find your solution anche change the address. For example I'm Italia living in Russia, I declared her I'm loving in Italy, all ok

@jeroenst
Copy link

jeroenst commented Dec 5, 2021

Strange that language creates a geo restriction, I live in the Netherlands but I speak perfectly English....

@Barabba11
Copy link

Barabba11 commented Dec 6, 2021

unfortunately my freind, I also don't understand why. Give you a chance to move Echo in England, hopefully you won't need to ask Alexa for the weather and time services :(
Try to figure out something at Amazon support.

PS: IMHO the module here ins't responsible for such bad behavior, it's just the recent Echo FW creating problems with Philips bulbs, unexpectely

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

No branches or pull requests

3 participants