HomeKit Not Working with Linksys Velop Wifi

Question

talksrm Author

Level 1

21 points

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:

Factory reset the Linksys system - no change.
Tried a different Wireless SSID - no change.
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.
Ensured any local firewalls are disabled.
Ensured the Linksys APs were fully up to date with firmware.
Opened the Linksys iOS app and enabled "Apple Home Integration" - no difference.
Identified that I have three "Homekit Hubs"; an iPad and two Apple TVs in different rooms.
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

Answer 1

Top-ranking reply

talksrm Author

Level 1

21 points

Jan 24, 2022 6:04 AM in response to talksrm

Just a further update...

After a lengthy time dealing with some very helpful people at Linksys (John & Edward), there has been some progress.

It seems that the APs will only work on un-managed switches. Due to the layout of my house, the two Velop Nodes were connected via ethernet cables and between those ethernet cables was a managed switch.

It appears that the way in which these APs work means that some (in my case two different) managed switches cause issues with the communications between these APs.

The switches I had did not have any Vlans set up on them, however, once these were replaced with cheap, un-managed switches, the Homekit component started to work.

This has been a very frustrating and long resolution but this does go back to what several people mentioned either on here on Reddit which is that these APs are very basic in terms of what you can do with them when setting them up. The features they offer are very limited. If you have issues such as mine, the only option is to replace your expensive switches with cheap ones.

For the record, I have:

HPE Office Connect 1810 J9902a
NetGear GS110TP

Whilst both APs are now working (with the double NAT) and Homekit is working, I have been unable to join both APs with the ethernet backhaul as both refuse to connect and the child inevitably goes to red which means to connection.

There are still issues with this, but I am so grateful to finally, after over half a year, be able to use Apple Homekit again.

I will provide further updates if anything changes.

Thanks to everyone who helped with this and also to the two guys at Linksys who knew their stuff. Unfortunately, you have to go through a lot of not so experienced, script readers with Linksys support before you get to deal with the guys who really know their stuff and these guys did.

Reply

Answer 2

Jan 6, 2022 1:33 PM in response to talksrm

I think you should return the Velop as unfit for use..

Tesserax was correct .. the issue is double NAT.

The solution is to use Velop as your only router which means bridging the EE smart router.. or even replace it with the Velop. If that is not possible, then the following might get things working.

Just work on the router first.

Use WAN bypass.

If the mesh products do not support AP or repeater mode that does not mean they won't work.. just that Linksys did not build in the functionality. But most devices can actually work in the required mode by manual configuration.

I cannot help much with the practical how to because the lack of setup via browser in user manual.

You will need to setup the router with a fixed LAN IP .. and turn off DHCP.

Both parts are important. Start with a reset to factory. Nothing but the computer connected to the Velop to do the configuration.

Login to the Linksys on your browser and go to the LAN configuration. Change the IP from 10.215.1.1 ?? or whatever it is.

Use an IP address from the EE Smart Router. So make it simple.. 192.168.1.200. Turn off the DHCP server if it is on the same setup page. If not you must save the IP change first.. then you will lose connection to the router. Make sure your computer also changes IP to match the new address. If it fails simply set the IP in the computer manually.. say 192.168.1.10.

Go back into the Velop setup page at the new IP, and turn off the DHCP server.

I am taking these numbers from here.

It would appear that the Velop system has it's own DHCP server enabled whereby any devices connecting via the Velop Wifi get their own IP address starting 10.215.1.10 with a max user count set at 245.

My EE Router has DHCP enabled with a server address range of: 192.168.1.64-192.168.1.253.

Now plug your EE smart router LAN port to LAN port on the Velop. Do not use the WAN. (hence the name WAN bypass)

This configures the Velop as a dumb AP.. and you can always access it on 192.168.1.200 if you use my numbers.

This helps no end to use AP in a network where they do tend to disappear.

If you test things and this works.. then the node may or may not work the same way.. if it does have the same setup use IP like 192.168.1.201.. If you cannot get the node to work over wifi it may work via ethernet.. worth a try at least.

Happy to help with the limitation as stated.. I do not own Velop mesh products.

Contact me via email you can find here.. I cannot post it directly on this site.

https://sites.google.com/site/lapastenague/

Reply

Answer 3

Dec 31, 2021 2:07 AM in response to talksrm

Same problem here for a few years now. I spent weeks with Apple Support trying to resolve this issue. At first when I set up all my Hue products on HomeKit and my Linksys Velop mesh system I had absolutely no issues at all and then suddenly one day all of my Hue products said “no response”. Apple support were very helpful and tried escalating this up to Cupertino engineers but had no joy at all trying to resolve this, so went onto Reddit and posted this on the HomeKit and was given the suggestion to change the Linksys settings for the Internet to Bridge mode. This immediately activated all of my Hue products. Unfortunately this has a downside in that I cannot link the HomeKit to my Linksys app for the firewall protection, and have no other settings that can be changed on Linksys as a result of being in bridge mode. But the upside is my hue bulbs now work and can be operated. I am frustrated with Linksys that this is the only way that my hue bulbs can work this way. I don’t think it’s an Apple issue, but of course I may be wrong! Anyway hope this helps you with your frustrations as it sort of date with mine!

Reply

Answer 4

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!!!

Reply

Answer 5

Tesserax

Level 10

157,860 points

Jan 2, 2022 10:02 PM in response to talksrm

talksrm wrote:

It would appear that the Velop system has it's own DHCP server enabled whereby any devices connecting via the Velop Wifi get their own IP address starting 10.215.1.10 with a max user count set at 245.

My EE Router has DHCP enabled with a server address range of: 192.168.1.64-192.168.1.253.

That would be because, by default, the WAN-side setting of your "main" Velop module is configured as a DHCP client. That means it would get its IP address (which would be a local address) from the upstream EE router. This also means that you would have a "Double-NAT" condition and why any clients connected to the Velop system cannot communicate with any connected to the EE ... except for Internet access. You an see this by the fact that the Velop (as you surmised) is providing DHCP service in a different subnet range.

The question becomes: Is this what you want or do you want all network clients to be in the same subnet at the EE router? For the latter, you would need to reconfigure your "main" Velop module in bridge mode. This would allow the EE to passthru DHCP services for clients connected to the Velop system.

Unfortunately, the user guide that I downloaded from Linksys, does not provide enough details on how to go about making this configuration change, and I can only guess that you can do so from the Advanced Settings > Internet Settings > Connection Type option.

Reply

Answer 6

talksrm Author

Level 1

21 points

Jan 2, 2022 1:06 PM in response to LaPastenague

Thank you very helpful!

I was already using WPA2 and a short SSID so that is fine.

Have always ensured that AP firmware is up to date, so the useful but now irrelevant info on Reddit re upgrading firmware won't help, but thanks, has been very interesting to read that. I will go through the comments on that thread next, but yes, as you sensibly suggested, I have been focussing just on the one node, rather than using both.

When I set them up, the backhaul was working via ethernet between them both, not sure if there is a way I can check that now to ensure that they are still connected to one another via ethernet. Both lights are blue on them so they are connecting. I had a lot of difficulty when setting them up and found that enabling STP on my network switches which connect between them both solved the issue.

Re your comments on Linksys being more like Cisco rejects... yes I can totally understand this now! The time wasted on this junk has been unbelievable.

Very good suggestion re maybe connecting the Airport onto a Linksys and also disabling 5ghz on the airport. I will give that a try as currently I have turned off Airport and I am seeing that Homekit randomly works, but most of the time doesn't. I have also disabled it on both Apple TVs and put my Hub iPad onto the Velop Wifi so Airport AP and respective SSID is currently not there anymore.

Currently the set up is...

EE (UK ISP) router providing DHCP > 1 ethernet cable to HP 1810 J9902a

From HP 1810 J9902a:

1 ethernet to downstairs
1 ethernet to intruder alarm
3 ethernet to various rooms upstairs
1 ethernet to Powerline Adaptor with other end in loft.
1 ethernet to old Apple Airport AP

Netgear GS110TP Switch in loft connects to:

Philips Hue Hub Box
Lightwave Box
CCTV NVR for house

Velop AP1 in on downstairs connection
Velop AP 2 is on one of the upstairs connections

It would appear that the Velop system has it's own DHCP server enabled whereby any devices connecting via the Velop Wifi get their own IP address starting 10.215.1.10 with a max user count set at 245.

My EE Router has DHCP enabled with a server address range of: 192.168.1.64-192.168.1.253.

The Velop APs have the following network IP addresses:

192.168.1.103 WAN Address - I can access this from devices not connected to the Velop WiFi, so ones connected on ethernet. I can also access this address from devices connected to the Velop WiFi.

10.215.1.1 - I can only access this address from a device on the Velop Wifi. This takes me to the parent AP

10.215.1.19 - I can only access this address from a device on the Velop WiFI. This takes me to the child node AP.

Note that there are no Velops in loft relying on Powerline connection, however I had to enable STP on loft switch to get the Velops to behave when first setting them up as they would not talk to each other.

@Lordothers mentions below about changing to bridge mode - I tried this, utter nightmare, couldn't connect to either APs, ended up having to factory wipe and start again so this 100% did not work for me. But thanks for the suggestion.

Reply

Answer 7

Jan 5, 2022 12:44 PM in response to talksrm

There is apparently a hidden onboard setup on the Velop.. instead of being forced to use the Phone App.

See Mr Dong.. who is very helpful on some of these things.

In his review of the MX4200 there is a link to an earlier review of the issue of phone Apps.

https://dongknows.com/linksys-velop-mx4200-ax4200-mesh-router-review/

This happens to be the Velop and might give you better controls.

https://dongknows.com/web-interface-vs-mobile-app/

The details are near the bottom of the article specific to the Velop.

I would never recommend these products to anyone with Smart Home devices

Matches my view on Belkin (which now covers Linksys) products perfectly.

Whatever testing they do for firmware upgrades is clearly inadequate.

Reply

Answer 8

talksrm Author

Level 1

21 points

Jan 7, 2022 2:57 AM in response to LaPastenague

Thanks again for your very helpful post and further info.

I am about 75% now that this is going to have to go back as not for for use.

I had two chats with Linksys support yesterday, I got cut off of the first incredibly long one. In total, I was in a chat with them for four hours something. Just ridiculous that this would all take so long and still no positive result.

They can’t help me so have escalated it to someone else who is going to call me. Everything they suggested, I have already done and incidentally, what you suggest in your last post, I also did try.

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.

If I try and do as you said and give the Velop a dynamically assigned IP, that works fine, however as soon as I go to the DHCP section to turn off DHCP (Connectivity>Local Network), Under Router Details, I notice that the “Router IP” starts with 10.something or another when it should be 192.168.1.x.

It allows me to edit this which I do. I went with 192.168.1.240 every time as I know this is clear and not leased out.

If I wait a few minutes, the 192.168 address changes back to a 10.x. Every single time. It refuses to keep the address.

Every single time I edit the address, it just changes it back. It doesn’t matter if you have DHCP on, off or you try a different address, in this area so it does not match the Velop dynamic IP address, it refuses to keep the IP you give it.

In the below photo, I have set the 'Router IP' to the address I want it to be and then within seconds, it changes back to a 10. Address again. This section is not the section you use to give the Velop a dynamic IP address, you do that in the basic tab, there is another section for that and I have ensured it had the right subnet and gateway as well as a free IP from the EE router DHCP range.

Every time I hit apply on this, within a minute, it goes back to the 10. IP range for the IP address under Router Details. It just will not accept this IP address. This is at the same time as it having a dynamically assigned IP. If I leave the Velop as DHCP, I still can change the IP address under Router Details but again, it will revert back not long after applying.

Reply

Answer 9

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!!

Reply

Answer 10

talksrm Author

Level 1

21 points

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.

Reply

Answer 11

babowa

Level 9

78,556 points

Dec 29, 2021 11:03 AM in response to talksrm

Just so you know, this is not Apple support - we are all other users here, so if you wish to troubleshoot with Apple, you need to use the link in the upper right corner of this page.

I did a search and found this:

https://www.apple.com/ios/home/accessories/

It lists a linksys velop - but a different model number being compatible.

Reply

Answer 12

talksrm Author

Level 1

21 points

Jan 5, 2022 3:53 AM in response to Tesserax

Thanks for your post.

Yes, this seems to be the case, though some connections do seem to go through. As an example, a wireless device connected to the Velop WiFi system can access my NetGear NAS drive which is connected to ethernet to the EE Router and thus gets an EE Router DHCP address, but the systems on the Velop WiFi are obtaining an IP from the Velop WiFi system and not the EE Router, so some connections seem to go through.

I had already tried twice what you suggested in terms of setting the AP to bridge mode and every time, it completely cuts out and shows a red light, as does the child node. I am then totally unable to gain any access, the WiFi is not able to be connected to and I am not able to proceed at all. The App will not open the APs and I am not able to access them via the web interface. The only option was to factory reset and re-set them up with the app which does not provide any options to set them up in Bridge Mode thus I am going round in circles.

I ordered this duo pack of APs in July 2021 and I am on the verges of returning them as "not fit for purpose" under the Sale of Goods Act. I have spent well over 2 days in my own personal time messing around with these devices and have got absolutely nowhere with them and on most occasions, actually worse off than if I had just left them alone. They clearly do not reliably support Apple Homekit, the support Linksys provide is not much better than my own technical knowledge. I made a posting on Reddit and it seems I am not the only frustrated user with several people saying they have ended up rolling back the firmware on their Velop to be able to make it work with Homekit. Surely, you should be ensuring your devices have the latest firmware, not reversing and going back to older versions.

I would never recommend these products to anyone with Smart Home devices who is planning on using Apple Homekit. Apple should remove these devices from their retail store.

Reply

Answer 13

talksrm Author

Level 1

21 points

Jan 6, 2022 12:09 PM in response to talksrm

And another update, having spent almost three hours on this issue yet again this evening with zero result,

I finally got through to Daisy Jane P at Linksys Support. I am getting one sentence responses from her every 10-15 minutes which basically say "I am still checking things at my end". First she told me it is my EE Smart Router at fault. I pointed out that HomeKit worked faultlessly with the same EE Smart Router and Apple Airport APs before so this is certainly not a router issue. She then just keeps saying she is checking, 10-15 minutes later, I message again...still checking. This has been going on for around 40 minutes so far.

I noticed the following on the help section for the router...

Wireless Bridge Mode isn't even supported on this router. The only option available with Bridge in the name is Bridge Mode which is says: 'Select this to use Bridge Mode if your ISP requires it. You can choose to obtain an IP address automatically, or enter the information for your internet address, subnet mask, default gateway and DNS entries. This information will be provided by your ISP'.

Every time I select this option, the router goes offline, I can connect to the setup SSID but I am completely unable to obtain a DHCP IP address on my client machine, if I try and enter in manual ones, I still can't locate the AP.

I have never known such a frustrating and impossible situation. Anyone reading these posts, DO NOT BUY A LINKSYS VELOP. The time that has been wasted on this trash is just unbelievable. It is quite obvious that their tech support are dealing with more than one customer at a time and expect you to wait 10-15 for a response, to which they give you a one sentence reply and then leave you waiting another 10-15 minutes.

Reply

Answer 14

talksrm Author

Level 1

21 points

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]

Reply

Answer 15

Dec 29, 2021 12:27 PM in response to talksrm

You have posted on a user-to-user support forum for the Apple routers.......the AirPort Express, AirPort Extreme and AirPort Time Capsule pictured below. No one from Apple will respond to your post.

It is possible that there might be a Linksys user on this user support site for Apple AirPort routers that might be familiar with HomeKit and Linksys, so you can wait to see if someone might respond.

Your best bet would be to contact Apple Support directly regarding HomeKit compatibility with Linksys products. The link is just below:

Get Support

Reply

HomeKit Not Working with Linksys Velop Wifi

Similar questions