SebasT87

Same problem here, hoping for a quick fix. As a workaround i did a rollback to the former SharepointPnP.

> @SebasT87 what version of SharePointPnP are you using as a workaround? That would be SharePointPnPPowerShellOnline to be exact. Which can be installed using: Install-Module SharePointPnPPowerShellOnline

I'm experiencing the same symptoms. Not sure though it's the same issue. In my case it seems a mdns issue because ,like bdraco says, it disappears within the suggested discovery...

Sure thing, but no issues found. All optimal. Don't know if it's related in any way under the hood, but when the records under hap._tcp disappear home-assistant._tcp also disappears. So...

The default interface option is false atm, but also tried true in an effort to resolve this in the past. Will have another look in the logs to see if...

Enabled zeroconf debug log and my oh my the log is filling up fast. Haven't seen ant obvious errors yet but i do see a lot of these lines DEBUG...

I understand, makes perfect sense. But when default_interface is set to true these should disappear? This should make it listen on one interface only right?

Enabled default interface and still seeing duplicates being ignored, but only on the default interface obviously. But Homekit seems to have stopped completely now because it seems to ignore everything.

My issues have been resolved by adding a decent switch to my network. Before i used the build in switch on the provider modem/router which was the culprit