Skip to content

Add Kira component documentation #2603

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

Merged
merged 1 commit into from
May 13, 2017
Merged

Conversation

stu-gott
Copy link
Contributor

Description:

Pull request in home-assistant (if applicable): home-assistant/core#7479

Copy link
Contributor

@Landrash Landrash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks god with some minor feedback.

ha_release: 0.45
---

The `kira` component is the main component to integrate Keene Electronics IR over IP [Kira](https://www.keene.co.uk/keene-ir-anywhere-single-worldwide.html) modules with Home Assistant.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would suggest you keep the name in the description and this the same.


The `kira` component is the main component to integrate Keene Electronics IR over IP [Kira](https://www.keene.co.uk/keene-ir-anywhere-single-worldwide.html) modules with Home Assistant.

An empty configuration will create a sensor using the default port that Kira modules use (UDP port 65432).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest some rewording since configuration is in general the whole of the config file and can cause some confusion for non native English speakers.
If anything I would suggest that you skip this line instead since the example configuration is commonly copy and pasted as a start for most new users.

You cover later after the code snippet why and how so that explains it rather well anyway.

Configuration variables:
- **name** (*Required*): The name of this code
- **code** (*Required*): The data for this code (see below)
- **device** (*Optional*): The device this code is associated with. defualt is "unknown".
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spelling: default instead of defualt

```

Configuration variables:
- **name** (*Required*): The name of this code
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

. at the end.


Configuration variables:
- **name** (*Required*): The name of this code
- **code** (*Required*): The data for this code (see below)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

. at the end.


### {% linkable_title Code Types %}

When creating an entry in kira_codes.yaml, a few different kinds of codes can be used.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wrap kira_codes.yaml in ` to get kira_codes.yaml

- **pronto**: Pronto codes are supported.
- **nec**: If the device uses NEC IR codes and the manufacturer has published them, they can be used here.

**NOTE**: NEC codes by themselves do not contain enough information to construct an IR sequence for sending--so codes of this type are receive-only (usable by sensors but not remotes).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"sending--so" unsure what you where going for here.

layout: page
title: "Kira"
description: "Instructions how to integrate Keene Electronics IR-IP modules (Kira) into Home Assistant."
date: 2017-5-7 00:00
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

date should be 2017-05-07 00:00

@Landrash Landrash added the new-integration This PR adds documentation for a new Home Assistant integration label May 10, 2017
@stu-gott
Copy link
Contributor Author

Thanks for the feedback!

@stu-gott
Copy link
Contributor Author

home-assistant/core#7479 has been merged into dev.

Copy link
Contributor

@Landrash Landrash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good and can be merged when parent Pr is merged.

@Landrash Landrash merged commit 10087da into home-assistant:next May 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-integration This PR adds documentation for a new Home Assistant integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants