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.
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.
My Hub is a V2 SmartThings Hub which is hardwired to my router.
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
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.
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
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.
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.
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: