-
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 does not see matter hub when scanning QR code #362
Comments
I have the same issue. If using a version not as an add on - that version works and connects immediately |
Which ports for the bridge is used? Alexa currently ONLY sees bridges/devices on port 5540 for initial com issioning ... afterwards port can change but commissioning is bound to 5540 ... so check the port of the bridge |
Yes 5540 is the port |
Ok then usual question: Alexa hubs are in the same network/segment as the device? So no firewalls or segmentations? |
Yes - as I posted if I use a manual install (all same vlan). It all works as expected but the add on version does notThanksAndrewOn 1 Jan 2025, at 4:19 am, Ingo Fischer ***@***.***> wrote:
Ok then usual question: Alexa hubs are in the same network/segment as the device? So no firewalls or segmentations?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Then you have an MDNS/UDP/IPv6 or such issue ... so check all this part of troubleshooting |
@AJErazzor How do you have home assistant deployed (HAOS on dedicated server/rpi, proxmox, ...) ? How are you testing the "manual deployment" (same or different vm / host) ? @Dogo69Dog Any updates from you? |
Hey, i changed the port back to 5540 and then restarted my router, alexa, and ha. I also linked the matter hub again which worked |
I have haos on a proxmox vm I am testing with a seperate proxmox Debian CT with matter-hub on it ThanksAndrewOn 3 Jan 2025, at 9:31 am, Tobias Glatthar ***@***.***> wrote:
@AJErazzor How do you have home assistant deployed (HAOS on dedicated server/rpi, proxmox, ...) ? How are you testing the "manual deployment" (same or different vm / host) ?
@Dogo69Dog Any updates from you?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
OK i juast had the same issue with the non-add on version and then changed a few things on my network and got that non-add on version operating again - so it looks like its a local issue with my wireless network and alexa devices - please dont spend any more time looking at this but thankyou for replying |
Version
3.0.0-alpha.58
Matter Controller
HA And Alexa
Things you tried
Scan QR Code, Input manual code, bring iphone closer to HA device, restart addon, reinstall addon, create new bridge
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: