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

Can not set name as input value #231

Open
Jodameister opened this issue Mar 29, 2020 · 7 comments
Open

Can not set name as input value #231

Jodameister opened this issue Mar 29, 2020 · 7 comments
Labels
enhancement 👍 New feature or request v1.5

Comments

@Jodameister
Copy link

Jodameister commented Mar 29, 2020

I tried to set the characteristic msg.payload.Name individual. But the Name as set in the HomeKit node is showed in the Home-App. When I let the name empty in the HomeKit node, node red said "Name" is invalid, but in the description "Name" is optional.

How can I set "Name" individual with each msg?

@crxporter
Copy link
Member

I don’t remember the exact names for everything but there are two “name” categories.

One is the service name which needs to be set once and left for the duration of the time it exists. When this is changed the device is deleted and re added to home app.

Next is the display name, this is the name you see in your home app on the phone or iPad. This can be changed at any time and will not be overridden if you change it on your home app.

Currently this plugin uses the required name field on setup for both of these. It would be a new feature to separate them. Let me look for the discussion on this so you can specifics from the devs. I’ll post again in a few minutes if I find it.

@Jodameister
Copy link
Author

The displayed name is what I will set individual over the input. So I can create a occupancy sensor and put a value like AirPressure in the displayed name (Airpressure: 1023hPa).

@crxporter
Copy link
Member

I think you will be disappointed with how well that (probably won't) work. That would be a similar approach to the "Service Label Namespace" and "Service Label" services. Last I tried those (about 6 months ago) they were pretty slow to update and didn't like being changed after the initial deploy. Things could of course be better now.

That being said, I believe this would be a new feature with the "service name" and "display name" separated.

@Jodameister
Copy link
Author

Thank you for your reply!

@crxporter
Copy link
Member

I haven’t seen @Shaquu aroind for a few days but I’ll leave him flagged. He may have comments.

@Shaquu
Copy link
Member

Shaquu commented Mar 31, 2020

I haven’t seen @Shaquu aroind for a few days but I’ll leave him flagged. He may have comments.

Sorry for being inactive for such a long period. Online studies are harsh and unfortunately I am on the sick leave for third week.

I see emails though so I will try to follow up in few days.

@crxporter crxporter added the enhancement 👍 New feature or request label Jun 30, 2020
@Shaquu
Copy link
Member

Shaquu commented Nov 1, 2020

Possibly will be resolved by #53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement 👍 New feature or request v1.5
Projects
None yet
Development

No branches or pull requests

4 participants