Apple Homekit and mDNS
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Apple Homekit and mDNS
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I am very new to home networking so appologies if I do not use the correct terminology. My setup consists of ER605 router, OC200 controller, SG2210P switch, EAP660 HD and EAP655 wall. We are a Apple household and use Apple Homekit for all of our smart devices which we have 26 homekit devices. All of these are on an IoT VLAN including my 2 homepod minis and 3 Apple TVs which are connect to ethernet on the IoT network. All of our iPhones, iPads and macbooks are on the main network.
Here are my curent ACLs below
When I turn on mDNS through the Gateway device type, the HomePod network mismatch goes away and my Homepods gain full functionality int the Home App which is great. However, I also have a few clients that become unresponosive in the Home App. Mainly my doorbell (Logitech Circle View Doorbell) and my 2 thermostats (Honeywell T6 Pro Smart Thermostat). I disable mDNS and the devices become responsive again in the Home App. I have tried resetting the devices while mDNS is enabled but that did nothing.
I have tried to get my neighbor to help with my setup but he uses a Ubiquiti setup in his home and is very unfamiliar with Omada and Apple for that matter.
Can anyone help with this or can someone point me in the right direction for this mDNS issue I am having with my clients to go unresponsive in the Home App?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Update:
Earlier today - due to the service ticket that was created, I received an early release of version 1.3.0 Firmware for my TP-Link R605 v1 Gateway. I installed and tested it to:
- ensure that my Apple clients (iPhone, iPads) are not renamed with a (1) or (2), etc. like they were on the previous firmware.
- ensure that the mDNS function works for my requirements. Initially, for me, this means that I can successfully use Airplay from my iPhones and iPads to my (3) Roku Ultras and my (2) AppleTV devices on different VLANs. I do not have any Airplay printers or scanners to test.
In both cases, the new firmware passed my testing and the firmware worked well.
- Copy Link
- Report Inappropriate Content
I have similar issues and also all my apple devices started renaming themselves with (1), (2) and etc... I've turned off mDNS for now.
The only smart devices that appears to have issues on Omada system is Meross Garage Door Opener. Most other devices have been OK.
Would be great to hear from Tplink what they think?
- Copy Link
- Report Inappropriate Content
Like yours, all my Apple devices have renamed themselves with (1), (2) and etc too. I've turned off mDNS too.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
>> May I know the model number and firmware version of your Omada Gateway and the Controller?
Gateway:
Model: TL-R605 V1.0
Firmware: 1.2.3
Controller:
Model: OC200 V1.0
Firmware: 1.24.0 Build 20230328 Rel.52384
- Copy Link
- Report Inappropriate Content
Gateway:
Model: ER605 v.2.0
Firmware: 2.1.2
Controller:
Model: OC200 1.0
Firmware: 1.21.7 Build 20221206 Rel.58608
- Copy Link
- Report Inappropriate Content
Hello @supaloop,
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID230439206, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Hello @shano81，
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID230439219, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Hello @lflorack,
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID230439220 , please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Update:
Earlier today - due to the service ticket that was created, I received an early release of version 1.3.0 Firmware for my TP-Link R605 v1 Gateway. I installed and tested it to:
- ensure that my Apple clients (iPhone, iPads) are not renamed with a (1) or (2), etc. like they were on the previous firmware.
- ensure that the mDNS function works for my requirements. Initially, for me, this means that I can successfully use Airplay from my iPhones and iPads to my (3) Roku Ultras and my (2) AppleTV devices on different VLANs. I do not have any Airplay printers or scanners to test.
In both cases, the new firmware passed my testing and the firmware worked well.
- Copy Link
- Report Inappropriate Content
I've had similar success with the beta version of the firmware. No more devices with (1), (2) and etc..The only issue I've got is devices do not resolve to their .local DNS address when DNS is pointed to Omada Router or AdGuard. I can add DNS rewrites on AdGuard and get around this.
Previously on older firmware or a while back didn't need this and .local was found but might be something to do with the firewall or VLANs now used.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3434
Replies: 13
Voters 0
No one has voted for it yet.