I purchased new Kasa Plugs model KP125 because I wanted native integration with Matter.
I setup with Alexa as instructed, and then I went to "other assistants and apps" and got a setup code. I then go to my hub (via web browser), click add device, choose matter, and type in the code and enter master setup code and click start pairing. it does nothing.
I also tried resetting and in apple home and tried to pair - same issue. So went back to Alexa, as that is my preferred setup.
What am I doing wrong? Why can't I pair my device using the setup code provided from Alexa?
That should work, but I'm curious what, exactly, you mean when you say "it does nothing." Can you share the specific message you see and whether it changes over time, as you should definitely at least see something indicating that it has started?
Some other general troubleshooting:
Make sure Alexa is connected to the same network as your hub (the hub doesn't have to be connected via Wi-Fi if Alexa is, as most consumer equipment treats wired and wireless as the same network, but it's worth checking whether you're using a guest network or advanced setups like an IoT VLAN)
Anything that might prevent mDNS from reaching your hub, perhaps the above?
If there's literally nothing when you start pairing, see if a different device or browser helps. (This wouldn't be a problem with your smart plug.)
So after I click the pairing button, the screen pauses a second, then refreshes. The setup code I entered is still in the box, and there is no error message or confirmation, it just returns to the same screen (hence, it does nothing). Hope that helps. I would expect to see some sort of action, or confirmation, or error message, but nothing appears.
I also tried on my mobile phone/browser and in the app - all do the same thing,
Alexa is definitely connected to the same network. Not sure about mDNS (we have everything connected to an eero mesh).
It briefly switches to a screen that shows the setup code and a cancel pairing button, and then quickly switches back to the previous screen (no error message or confirmation).
Check the Settings > Matter Details page to make sure Matter is running, i.e., no errors or "starting" status there (and enabled, though you shouldn't even get a far as you didn't).
You could also try a hub reboot to see if that helps: Settings > Reboot.
Also, it's always good to check "Logs" for any errors, though I'm not sure you'd see anything revealing in this particular case.
You will not be able to pair any devices until that is resolved.
If a reboot did not solve the problem and you cannot identify any problems from Logs or other culprits such as high hub load, I'd put in a ticket at support.hubitat.com with the details you have provided here, or send a PM to @support_team with the same information and your hub ID. Hopefully you can get this fixed!
How do I do this? I don't see a way on the support site to open a ticket.
Also, does anyone else have any ideas? I still cannot get Matter to start. I have not yet done a database rebuild (afraid to do that), but from what I've read on other topics, it doesn't work.
I have a similar problem, wifi over matter works but thread over matter refuses I have discovered my router is not up to the job, I am expecting a replacement router upgrade is due to be delivered tomorrow
Submit a Warranty Request which will cause a ticket to be created.
I am also tagging @support_team as this issue has been reported a couple of other times already. Looks like it is something that the Hubitat Team will need to address.
I’m sorry for the frustration this has caused. Based on the age of the hub, this would be outside the warranty period for a C-7 that is several years old.
That said, the Matter server not starting is unlikely to be a hardware-related issue and is instead the result of a software problem. We’ve identified the underlying issue, and our engineering team is actively working on a fix. An update will be released as soon as the issue is resolved (this is applicable only to C5/C7 hubs).
Quick update. This issue will be resolved in the next (major) update - 2.4.4. If you experience this problem on older hub models (C-5 and C-7), please send a private message to @support_team.
