Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessory name shound't contain "_" #141

Open
yangm97 opened this issue Jul 10, 2019 · 7 comments
Open

Accessory name shound't contain "_" #141

yangm97 opened this issue Jul 10, 2019 · 7 comments

Comments

@yangm97
Copy link

yangm97 commented Jul 10, 2019

It seems like hc converts spaces into underlines, but homekit doesn't like it.
HAS actually uses spaces on names so I guess it's the way to go.

@brutella
Copy link
Owner

@yangm97
Copy link
Author

yangm97 commented Jul 19, 2019

I see. Hope it gets fixed soon, the fact home.app hates _ is actually what makes this issue a bigger problem than it should be.

Great work on the library btw, been using it flawlessly.

@brutella
Copy link
Owner

hc only replaces spaces with "_" for the published dns-sd service name. The accessory should still appear without spaces in HomeKit. Can you please check that.

@yangm97
Copy link
Author

yangm97 commented Jan 27, 2020

Last time I checked (long time ago, iOS12) it was showing up "_"s at the Home.app. Gonna try again with the latest hc version.

@brutella
Copy link
Owner

brutella commented Feb 2, 2020

Apple Home should only show an underscore when you add the accessory to HomeKit.
Once added to HomeKit, the name should be correct.

@travishaagen
Copy link

travishaagen commented Feb 9, 2020

Something in iOS12 may have changed recently to make this worse. Yesterday, with hc v1.2.1 I added my bridge accessory to HomeKit and it complained about the underscore in the name. It would not let me click Next unless I changed the name in the UI. This wasn't happening when I was testing a couple weeks back.

I was able to rename my bridge accessory to have hyphens instead of spaces, so that works for me.

@brutella
Copy link
Owner

Hm, I never seen that error. I will try to reproduce it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants