-
Notifications
You must be signed in to change notification settings - Fork 25
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
[Connection Issue]: Alexa connections #369
Comments
same here, almost all not reachable with Alexa, no errors logged |
I noticed the Problem today too. Since 4 days some entities can't be controlled via Alexa. For what i found Out it seems to affect all my input_booleans aswell AS some switches but Not all of them. An z2mqtt Switch still works while the shellys dont. |
I kind of fixed it by completely removing the bridge from the add-on and from Alexa and repairing it. However I don't know yet how long it will last. |
Now i test with Matterbridge zigbee2mqtt plugin for Matterbridge Home Assistant Add-on. Es spielt keine Rolle von welcher Integration das Gerät ist. Ich habe Mipow, MQTT, ZHA, Helfer, Scripte, Automatisierungen usw. Neu hinzugefügt funktionieren sie, aber irgendwann empfangen sie nur noch den Status in Alexa, können jedoch nicht mehr gesteuert werden. |
Please provide debug log ideally tell when the issue started and provide log from before where it was working till it stopped working |
Here my last log. The test device is Google Lampe. After restarting the lamp worked, but stopped working after a few minutes.
|
Next errors.
|
Same here |
Same problem here. Alexa does appear to have Matter comms problems when the Echo's are in a combined speaker setup though (when it sets up it's own access point on Fire TV), but not sure if this is related to that issue. I've also had HA lock-up frequently (only when running this), and the logs don't seem to show anything, so I've had to disable it for now. When it locks up HA, everything becomes unresponsive (UI, Zigbee, Matter etc), so it makes it unusable for me right now. |
Same problem but without locking |
Is your Alexa in a speaker group with a Fire TV ? The reason I ask is that this sets up its own AP for FireTV (on Wifi 6 networks) and I've seen issues when this is the case. |
I have 7 Alexa and one FireTV. In the bedroom group I have the FireTV and Alexa Bedroom. But not in multiroom. |
I have 6 Echo Dots and an Echo but noch fire TV Stick and still got the Problem. I Made a new Bridge today and deleted the old one. I'll see If it helps |
This is, what I did, too. |
Tried it many times but the behavior came back every time. First encounter was at the beginning of december last year. After this I had to replace the bridge every week or two. I have no Fire TV. Only two Amazon speakers (Dot and Show) and some Sonos with Alexa integration. |
Version
3.0.0-alpha.58
Matter Controller
Alexa
Things you tried
After a few days of testing. Alexa can no longer switch devices, but recognizes the status.
Alexa just says the device is not responding
Even restarting the addon and HA doesn't help.
This affects all controllable devices.
Deleting devices only helps for a short time, but then it happens again.
logs-6.txt
Relevant log output
What deployment method do you use?
Home Assistant AddOn
Did you already check the following?
Documentation & Issues
The text was updated successfully, but these errors were encountered: