You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

HomeKit Not Working with Linksys Velop Wifi

Hi there,


This is an interesting one and it is driving me mad.

I have a mixture of Philips Hue and Lightwave smart home devices on my Apple

Homekit setup.


I have had, for some time Apple Airport Wireless. Sadly Apple don't do it anymore and due to having more and more devices, the Airports

could not cope.


I splashed out and upgraded to two Linksys Velop MX4200 APs - they were not cheap but offered a home mesh setup.

They work like a dream and use an Ethernet backhaul to talk

to one another – one upstairs and one downstairs.


However, ever since I have switched to these, Homekit immediately stopped

working.


After spending some time diagnosing, it is very obvious to me that the problem

is that Homekit will just not work with these Velop APs. Linksys don’t seem to

know what the reason is but here is how I have come to that conclusion:


  1. Factory reset the Linksys system - no change.
  2. Tried a different Wireless SSID - no change.
  3. Identified that this issue occurs on any Apple device with Homekit. I have tested with several iPhones, iPads, two Macbook Pros and a MacMini. All devices were fully up to date with respective iOS or MacOS software versions.
  4. Ensured any local firewalls are disabled.
  5. Ensured the Linksys APs were fully up to date with firmware.
  6. Opened the Linksys iOS app and enabled "Apple Home Integration" - no difference.
  7. Identified that I have three "Homekit Hubs"; an iPad and two Apple TVs in different rooms.
  8. Introduced one of the old Apple Airports to the network with a different wireless SSID. If I connect my Homekit Hub iPad to this SSID and not the Linksys SSID, Homekit works faultlessly, however, occasionally, Homekit Hub status moves from the iPad to one of the Apple TVs. Because these are on the Linksys Wireless, the Homekit stops working again.


The conclusion here is that so long as the Homekit Hub device is NOT connected to the new Linksys WiFi, Homekit will work, even if the iOS or MacOS devices you use to control Homekit are on the Linksys WiFi, but the Homekit Hub will not work with Linksys.


It is impractical for me to be adding all three possible Homekit devices to the Apple Airport AP as the whole point of replacing the Airports was to have an improved wireless signal but it seems at the cost of being able to use Apple Homekit. I have a large number of devices and need this to work.


Please see below images of the exact issue:



Upon opening HomeKit app, this is the view I get if the HomeHub is running on the new Linksys wireless:


If I navigate to My Home within HomeKit App, this is what I see:


Selecting "Home Hubs & Bridges" gives me this:


Note my iPad and two Apple TVs are listed. In this example, the smart devices are showing "No response" because Bedroom Apple TV is currently the "Connected" Home Hub, but this Apple TV uses the Linksys wireless. Only RMT-Mini (iPad) uses the old Apple Airport with a different SSID just to help with this issue.


If I try to control an accessory, this is the error I get:



These are the settings I see on any of my two Apple TVs:



Any help on this issue would be greatly appreciated. As you can see, this is not a basic issue, there is a more complex problem here and Apple and Linksys need to collaborate to get a resolution. I have spent a lot of money with Apple purchasing Apple Homekit enabled smart devices and I need this to be working without using old Apple Airport technology.





Posted on Dec 29, 2021 9:39 AM

Reply

Similar questions

23 replies

Jan 7, 2022 4:49 AM in response to talksrm

I can understand the Linksys is auto changing to the 10.x.x.x IP range.. is this because you still have the EE router plugged into the WAN port?? If so please try removing it.. and you could even set a static WAN IP of 10.x.x.x just to force it back to using 192.168.x.x

The idea I am suggesting is not using the wan connection at all. This is important.. so setting even a stupid public IP for WAN might work.

This is result of them making the setup so automated that you cannot even fix it if you tried.. I have seen this happening recently with a number of brands.. especially phone app controlled mesh devices which are designed for the extremely limited scope of a phone app.


Going back a bit further.

I can’t replace the EE router totally as I have a UK copper phone line bringing in my broadband so the plug would not fit in the Velop.


There are two parts to the EE router. The modem which deals with ADSL/VDSL etc.. and the router..

Unfortunately in Australia we copied the FTTN (VDSL) from UK.. having been told.. don't do it.. its terrible.. the politicians got involved.. and found out it was cheaper.. and refused to listen to reason thereafter.

But we can use a VDSL modem/router bridged and use a different router.. it can be messy depending on the chaos our ISP's then introduced with several different and conflicting systems of authentication. But you need to check if it is possible for the Velop to take over the main router role.. if so the EE box may need to be replaced if it hasn't got ability to bridge. Or even change ISP if your supplier is stubborn .. we have several like that who refuse to allow customers to use their own routers.

My advice to people is LEAVE.. (if people left in suitable droves policies of a more rational nature may suddenly become the norm.) .. but that is not always possible.

If that is the case then everything in your setup needs to live behind the Velop as the double NAT will block the two networks functioning.. although there are likely parts that will be fine still connected to the EE router.. eg.. if you have voip phone system can be difficult. Many routers do have DMZ function where you can pass all incoming connections without NAT links to the DMZ device.. ie the Velop. This helps loads to stop the ill effects of double NAT.. but does mean your whole network must be arrange behind the Velop and will take some work to arrange.

If it becomes too messy then I would say the Velop is unfit for use and should go back..

There are cheaper and easier ways to skin the cat!!

Jan 10, 2022 3:32 AM in response to LaPastenague

Hello again, and thanks for your post.


I have not had a chance to go through it yet as Linksys contacted me by phone. I had a long discussion with a very helpful guy who is looking into this for me. He said this is an unusual situation. We spent some time going over what I had tried. He ran a remote session and could see the issue I was facing. Interestingly, despite being connected via ethernet, the two APs are not using an ethernet backhaul - not that this should cause the Homekit issues.


I am waiting for them to get back to me, but will update you with their findings. I mentioned several times about the double nat situation and indeed it could be evidenced on his remote session as they can only do remote sessions to Windows systems. I booted up the windows system which also has ethernet, and he was unable to gain any access to the velop systems as they have their own NAT. Luckily, I had a wireless adapter on the Windows computer and as soon as I enabled that and it obtained an IP from the Velop system, he was able to resolve the two APs. Meanwhile, I was telling him, from my Macbook, I was able to instantly visit the web interfaces of the APs as the Macbook was already on the Velop IP range.


Let's see what they come back with! Thanks again for your help with this.

Jan 24, 2022 12:46 PM in response to talksrm

Thanks for the update.

Great to hear you got it working.

It is helpful to know how a product works when it is sold by Apple for Apple networks.

That a managed switch (without vlans set) should cause failure of the whole Homekit environment is scary considering they worked fine with the Apple Airport routers. I always prefer to use managed switches. Plus the failure of the Velop to use Ethernet backhaul is a good argument to stay away.


I am still looking for the ideal home AP / Mesh setup.

Just installed a TP-Link Omada setup for a friend who runs a business from home and wanted better grade equipment than average domestic. These are very similar to Ubiquiti UAP although cheaper and easier to setup and manage IMHO.

Not a cure all though and the AP units are less flexible than I would like.


I am playing around with a setup of Xiaomi AX1800 and AX3600 routers configured for AP mode. They are dirt cheap, perform very well and offer reasonable setup for home use. They are somewhat limited by firmware which I would rate as poor.

International version with English firmware is more limited than Chinese version.. in that Mesh only works when one of the nodes is working as router. In Chinese firmware this worked fine in AP mode.. but security?? (keep in touch with CCP to report your activities so is less appealing from let's say a political standpoint.) Security is less of a problem with English firmware.. in AP mode at least. They can be blocked from direct internet access. Hopefully OpenWRT will be able to finally get it working on 3rd party firmware.



Feb 8, 2022 11:16 AM in response to talksrm

All detailed talk of which device is assigning IP addresses aside (my DSL provider allows bridge mode / temporarily assigned me a static ip for the modem to test if that would help make the Linksys MX12600 (3x 4200's) work well)...


Purchased Linksys MX12600 back in September 2021.


First problems happened almost immediately... maybe a day of reasonably stable network / Homekit behaviour...


First call to support at Linksys, the guy basically said these units are junk and at some point there would be a firmware update, but I'd be better off buying one of their more expensive, non-homekit units (can't remember which one)...


Since then, 50-60 hours on the phone, more than that doing my own diagnostics, fine-tuning (to the extent they allow in the web interface, which is better than the app for sure), upgrading/downgrading firmware, pulling ethernet through two stories of challenging routes, so there would be nothing in between the units other than brand new Cat 6E, replacing those ethernet cables, going back to wireless, trying a power line device setup, just because I had them lying around, etc. etc. etc. Never has it worked for more than a day or so and that "worked" is to be taken with a grain of salt - some HomeKit devices would be flaky, very flaky (particularly Belkin Wemo devices, funny enough, since Belkin owns Linksys) but not worth running around the house doing power pulls because a reset via the app or web interface would NEVER bring back the child nodes automatically. I've tried ALL the possible setups, factory resets, disable / enable HomeKit, remove, factory reset and reinstall devices, buy new devices to test...horrible stuff!


Called Apple yesterday and spoke with a guy who said he'd be willing to escalate to engineers, but both of our guts were saying it was all to do with Linksys...


So, to avoid wasting Apple's time or my time, last night, I pulled my old AirPort Extreme and three Express units out of the storage room, did full resets and manually configured my settings... it's only been 12 hours since I completed the return of the Apple network, but I have not had one single moment of "Updating" or "No Response" in HomeKit... my devices are all happily connected, AirPlay works in a second instead of a minute, with three tries in between, the garage door will actually open from CarPlay on the first try and report back that it's open when it's open and closed when it's closed (the last three months it would say closed when open or open when closed and because of the bad reporting in HomeKit would allow the Chamberlain MyQ to close with no warning, thinking it was just opening - locked me out without my keys or phone when I was taking out the recycling).


Linksys is sending me three new units - the whole system - we think... I've sent them another email to suggest that unless they're really very confident that a whole new setup will fix my problems, perhaps they should just buy the system back (sadly too late to return to the retailer).


I have been through four months of awful time wasting, missing important work / family / personal hours and just general calamities with Linksys from phone numbers not working for their support agents, to long (8+ hours once) hold times only to be disconnected, poor VOIP connections to their overseas call centres that only exacerbate the language barriers and the nonsense script reading... Truly the worst technology / customer service experience I have had to deal with personally, EVER.


The last 12 hours have been magical, wonderful, pleasant - downright amazing - things are just working... that said, the Apple Airport units are getting old - there's a reason I figured it was time for a new system and now it's likely back to the drawing board in searching for a new system that includes HomeKit support... wishing the only other option wasn't Amazon / Eero... anyone know of any "promised" support for HK from other vendors?


Good luck to everyone dealing with Linksys and have a little sympathy for the poor folks on the other end of the line - they're supporting a product that no human should have to deal with as an agent, or a customer. In the 90's it was always Linksys... Apparently not anymore. I can only encourage anyone / everyone to stay away, or if you're stuck with a set, call or email Linksys daily to tell them how bad it is and how much needs to be fixed!!!

Feb 8, 2022 1:41 PM in response to ImCanadianEh

a product that no human should have to deal with

Thanks for sharing your experience.


My first response to this thread I stated my grievances with Linksys (at least since Belkin)


Sorry I don't have and never will buy mesh from Linksys as I rate them as Cisco rejects bought by Belkin. One of the worst suppliers of home networking.


Back in the day.. (long long ago .. before the empire) WRT54G.. was amazing router that spawned almost single handed the whole 3rd party router firmware interest. OpenWRT, DD-WRT for example and even some used in other brands AsusWRT.

All carry the Linksys W=Wireless RT=Router badge with honour.

Belkin tie up with Apple has been ongoing over long period. Just makes you want to shake your head and start screaming.. Apple .. Find another partner company.. do it now.. today!!


Feb 8, 2022 3:09 PM in response to LaPastenague

A little update... Yesterday, on the phone with Apple Support, I already strongly suggested they should not be endorsing these devices in any way by selling them through the Apple Store... just a FWIW, I'm going to keep telling them!


Yes to the WRT54G... it wasn't even a question that it was *the* router back then!


And, the important update - I changed a couple of settings on my AirPort Extreme, requiring a reboot... can anyone guess which were the ONLY devices (we have about 50 HK devices) that required a power pull to have them come back online / be responsive to HomeKit... yup, it was all three of the remaining Wemo plugs (the new ones, smaller ones with up to date firmware). Everything else, including the plugs I'd recently replaced with different vendor's units that were trouble with the MX4200's came back right away. Expletive, expletive... Linksys / Belkin!!!

Feb 27, 2022 9:47 AM in response to talksrm

A further update....


Despite all of the help from Linksys support, unfortunately, this product still does not work as expected.


I have removed all expensive managed switches I have in my home and replaced for cheap, gigabit, non-managed switches.

Remember, before I purchased this Velop, my previous Apple Airport wi-fi system, worked perfectly with the managed switches.


Still, the two Velop nodes do not communicate with each other. The Linksys site states that they should be able to speak to each other with a managed network switch between. They just don't. Like I say, I removed the managed switch and added a basic, non-managed switch and still, they do not work with the child node always showing solid red meaning not able to connect to parent.


I have extensively tested the ethernet cables in my home and there is nothing wrong with them. I have gone through 5 different network switches and nothing changes.


This product has never been fit for purpose and I am so angry at the amount of time I have wasted on this.


I am drafting a letter to such that I can return the product as not fit for purpose. Really, this should be done within 30 days, but I have spent so long trying to resolve this issue, it has been more than half a year. I was convinced it must be something that I have here causing the problem, but sadly, these Velop APs just don't do what they are advertised to do. A very frustrating waste of time and effort for no result.


[Edited by Moderator]

HomeKit Not Working with Linksys Velop Wifi

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.