SmartThings Hub is no longer discoverable using mDNS (Jan 2024)

My SmartThings Hub is no longer discoverable using mDNS.

Until recently, a call to for the “smartthings” service discovered my SmartThings Hub.
It has stopped working.

This has broken a number of my applications.

Is there a way to turn it back on?

@nayelyz can you help with this please.

Many Thanks Tim

Hi, @Tim99
You’re referring to edge drivers that use mDNS, right? So, you no longer can create connections with devices using this protocol?

Yes I have a number of edge drivers and external applications that do an mDNS scan for any smartthings services (provided by a SmartThings Hub).
This used to work fine but somewhere in the last month it has stopped working.

This feature is key to a number of drivers and automations I have.

Please can you find out how we can re-instate this feature.

Many Thanks Tim

1 Like

Thank you for the info, @Tim99. Can you confirm which firmware version is your Hub using, please?
Are you part of the Beta program?

1 Like

My Hub firmware version = 000.051.00002

No. What Beta programme?

There is a customer Beta program where Hubs get an early release of the firmware and it helps to detect issues that could affect users. Here’s the latest announcement:

I shared this info with the engineering team, to see if the issue can be investigated or if we need further info from you. I’ll let you know.

Hi, @Tim99

Following up, the engineering team mentioned this needs further info, could you provide the following, please?

  1. Hubcore logs from a period where your driver is running mDNS Discovery. These can be sent as follows:
  1. In the Advanced Users app, enter the “Hubs” section
  2. Enter the corresponding Hub and click on “Dump Hub logs”
  3. Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
  4. You’ll get a green box at the top confirming the Hub logs were requested.
  1. Any information about changes to network topology (new router, new configurations, moving device(s) from wired to wireless or vice versa)
1 Like

@Tim99, before sending the info I requested above, can you let us know if you have a V3 Hub connected through Wi-Fi, please?

Hi @nayelyz thanks for your help on this one.

  1. My Hub is a V2 SmartThings Hub which is hardwired to my router.

  2. My home network is very mature, so no changes have been made to the network topology recently.
    no new router
    no new configurations
    no moving device(s) from wired to wireless or vice versa

I will setup the logs later today.

Many Thanks Tim

Ok, I have just this minute dumped my logs. (9:1am UK time)

I have used an edge Driver called mDNS Explorer to perform the following:

  1. Perform a mDNS scan for the smartthings service
    No records returned. This used to return 1 record of my hub

  2. Perform a mDNS scan for the http service
    A number of records returned. This is consistent with the past.

  3. Perform another mDNS scan for the smartthings service
    No records returned. This used to return 1 record of my hub

Hope this helps.

Let me know if you need any further data.

Many Thanks Tim

Do I need to turn Dump Hub Logs off?

Hi, @Tim99
The process that sends the logs is a one-time thing, that’s why they must be sent after replicating an issue before they get replaced by the logs of the new events.

Can you also provide access to your SmartThings account, please? Sorry, I forgot to mention it earlier.

  1. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
  2. Enable support access to your account:
  1. Go to the SmartThings Web (
  2. Log in to your Samsung Account
  3. Select Menu (⋮) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

Yes the account registered is my account.

I have provided support access for 1 week.

Ps. I dumped the log and then did the mDNS operation is that the right way round?

1 Like

No, first you need to replicate the issue and then send the logs. Sometimes they last up to 12 hours but it depends on how many devices you have and how “chatty” they are.
You can click on the button again and I’ll ask the team to see if they are still there, if not, you’ll have to replicate the issue.

Its ok . I’ll do it again the right way round.

Ok all done.

  1. I did a mDNS scan for the http service
    It returned some records

  2. I did a mDNS scan for smartthings service
    NO RECORDS returned

Then I dumped the logs.

Over to you

Many Thanks Tim

Hi @nayelyz, Any News?

Hi, @Tim99
Not yet, I just asked the engineering team if there are any updates.

@nayelyz can I please have an update this is now urgent.

Have the developers all the information they need?

When can I expect an update?

Many Thanks Tim

Hi, @Tim99
I already shared your comments with the engineering team and they have this case in their backlog.
However, as they currently have a heavy workload, they are taking care of issues based on their priority so we cannot provide an ETA for the solution of this one.

Just as a reference, some fixes require a firmware update, so, if you’re interested in getting it ahead of time, consider enrolling the Beta group as mentioned in the post I linked above: