Omada mDNS with HomeKit
For anyone facing issues with HomeKit and mDNS for homekit devices/accessories in another network/VLAN.
Create the following service under Profiles-> Bonjour Service.
And select the service in mDNS rules.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @nilava
Thanks for posting in our business forum.
Anyone got issues with mDNS and Bonjour Service, refer to the guides:
Troubleshooting mDNS Repeater on the Router Doesn't Take Effect
- Copy Link
- Report Inappropriate Content
@nilava Thanks for this. I have found this made my homekit devices in my IoT network to be more reliable.
However, I still have some issues and not sure if you know of any work arounds. Currently I have 2 homepods that are on my IoT wireless network along with 3 apple tvs on my IoT network connected via ethernet while I have all iphones, ipads and laptops (mac and pc) on my main secure network. I also have all the latest updates on all of my omada hardware. Being that my iphone and homepods or on different wifi networks I have the homepod mismatch warning on the home app. Because of this I do not have full functionallity of the homepods (timers and auto updates). I have tried connecting my homepads to my main secure network (same as my iphones) and the homepod network mismatch warning on the home app goes away. I gain full functionallity of my homepods and can control all of my homekit devices via my iphone both through the home app and through Siri on my iphone. However, with this my homepods are not able to control any of my homekit devices through Siri commands.
Any advice on what to do here?
- Copy Link
- Report Inappropriate Content
@nilava Thanks! Solved my issues.
Any other recommended profies? I added one for spotify ...
_spotify-connect._tcp.local |
- Copy Link
- Report Inappropriate Content
@nilava thank you, it solved my issue. You made my day !
- Copy Link
- Report Inappropriate Content
Hi @nilava
Thanks for posting in our business forum.
Anyone got issues with mDNS and Bonjour Service, refer to the guides:
Troubleshooting mDNS Repeater on the Router Doesn't Take Effect
- Copy Link
- Report Inappropriate Content
supaloop wrote
@nilava Thanks for this. I have found this made my homekit devices in my IoT network to be more reliable.
However, I still have some issues and not sure if you know of any work arounds. Currently I have 2 homepods that are on my IoT wireless network along with 3 apple tvs on my IoT network connected via ethernet while I have all iphones, ipads and laptops (mac and pc) on my main secure network. I also have all the latest updates on all of my omada hardware. Being that my iphone and homepods or on different wifi networks I have the homepod mismatch warning on the home app. Because of this I do not have full functionallity of the homepods (timers and auto updates). I have tried connecting my homepads to my main secure network (same as my iphones) and the homepod network mismatch warning on the home app goes away. I gain full functionallity of my homepods and can control all of my homekit devices via my iphone both through the home app and through Siri on my iphone. However, with this my homepods are not able to control any of my homekit devices through Siri commands.
Any advice on what to do here?
Hi @supaloop
I am facing the same issue. Did you find any solution for this.
Also if both your homepod and iphone is on main network and homekit devices or on IOT neywork, what happens when you need to add new devices to homekit will you need to shift homepod or iphone or both to IOT network?
Thanks
- Copy Link
- Report Inappropriate Content
I've done all these steps, but ER605 V1 absolutely doesn't work.
Most other people say the same - mDNS repeating (and I only need prointer access) should be straight up marked as disabled for ER605.
- Copy Link
- Report Inappropriate Content
Hi @jalexoid
Thanks for posting in our business forum.
jalexoid wrote
I've done all these steps, but ER605 V1 absolutely doesn't work.
Most other people say the same - mDNS repeating (and I only need prointer access) should be straight up marked as disabled for ER605.
So, this is a straightforward feature and there would only be two results of it. Work and don't work. For me, it is way too common to see such comments.
If you want to dig into this, provide the information I need if you have done both links, you should know what I need. BTW, if you want to make the HomeKit work, you also need a hub in your network. What hub do you have?
I don't understand the second line. What are you trying to express?
- Copy Link
- Report Inappropriate Content
Hi @querymaster
Thanks for posting in our business forum.
querymaster wrote
supaloop wrote
@nilava Thanks for this. I have found this made my homekit devices in my IoT network to be more reliable.
However, I still have some issues and not sure if you know of any work arounds. Currently I have 2 homepods that are on my IoT wireless network along with 3 apple tvs on my IoT network connected via ethernet while I have all iphones, ipads and laptops (mac and pc) on my main secure network. I also have all the latest updates on all of my omada hardware. Being that my iphone and homepods or on different wifi networks I have the homepod mismatch warning on the home app. Because of this I do not have full functionallity of the homepods (timers and auto updates). I have tried connecting my homepads to my main secure network (same as my iphones) and the homepod network mismatch warning on the home app goes away. I gain full functionallity of my homepods and can control all of my homekit devices via my iphone both through the home app and through Siri on my iphone. However, with this my homepods are not able to control any of my homekit devices through Siri commands.
Any advice on what to do here?
Hi @supaloop
I am facing the same issue. Did you find any solution for this.
Also if both your homepod and iphone is on main network and homekit devices or on IOT neywork, what happens when you need to add new devices to homekit will you need to shift homepod or iphone or both to IOT network?
Thanks
Of course it does not work if you have set up ACL. Hmm, the link I posted above does not mention that ACL would block this? In the mDNS repeating, if that's blocked, or anything is not under the same network, or has access from the hub to the IoT, you wouldn't be able to manage or control them.
And HomeKit is local network-based controlling, and you have to make sure the phone, hub, and IoT have access to each other. This is MUST. If one is missing out, you don't get it working.
- Copy Link
- Report Inappropriate Content
Clive_A wrote
Hi @jalexoid
Thanks for posting in our business forum.
jalexoid wrote
I've done all these steps, but ER605 V1 absolutely doesn't work.
Most other people say the same - mDNS repeating (and I only need prointer access) should be straight up marked as disabled for ER605.
So, this is a straightforward feature and there would only be two results of it. Work and don't work. For me, it is way too common to see such comments.
If you want to dig into this, provide the information I need if you have done both links, you should know what I need. BTW, if you want to make the HomeKit work, you also need a hub in your network. What hub do you have?
I don't understand the second line. What are you trying to express?
1. ER605 V1 firmware at 1.3.1 - mDNS forwarding config doesn't work. It doesn't repeat the queries. I tried all options and troubleshooting.
Getting on the same network as all of my IoT devices - I can query everything.
Switching to another VLAN - queries don't get forwarded, but networks are reachable.
I setup Avahi Repeater - and everytrhing works perfectly.
2. Omada Controller UI should disable mDNS for ER605 V1. Because it doesn't work in any capacity.
- Copy Link
- Report Inappropriate Content
Hi @jalexoid
Thanks for posting in our business forum.
jalexoid wrote
Clive_A wrote
Hi @jalexoid
Thanks for posting in our business forum.
jalexoid wrote
I've done all these steps, but ER605 V1 absolutely doesn't work.
Most other people say the same - mDNS repeating (and I only need prointer access) should be straight up marked as disabled for ER605.
So, this is a straightforward feature and there would only be two results of it. Work and don't work. For me, it is way too common to see such comments.
If you want to dig into this, provide the information I need if you have done both links, you should know what I need. BTW, if you want to make the HomeKit work, you also need a hub in your network. What hub do you have?
I don't understand the second line. What are you trying to express?
1. ER605 V1 firmware at 1.3.1 - mDNS forwarding config doesn't work. It doesn't repeat the queries. I tried all options and troubleshooting.
Getting on the same network as all of my IoT devices - I can query everything.
Switching to another VLAN - queries don't get forwarded, but networks are reachable.
I setup Avahi Repeater - and everytrhing works perfectly.
2. Omada Controller UI should disable mDNS for ER605 V1. Because it doesn't work in any capacity.
Test method and details, please.
Wireshark results and port mirror details.
How to capture packets using Wireshark on SMB router or switch
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 3317
Replies: 10