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

Current status of the NAD library and HA integration #57

Open
rrooggiieerr opened this issue Apr 12, 2023 · 2 comments
Open

Current status of the NAD library and HA integration #57

rrooggiieerr opened this issue Apr 12, 2023 · 2 comments

Comments

@rrooggiieerr
Copy link
Contributor

Hi!

So I recently replaced my NAD T 752 with a T 755 because of the serial port and my wish to integrate the receiver with HA.

Can anyone (@joopert, @gladhorn?) tell me the current status of the NAD library and NAD HA integration? Doesn't look like there has been much work on recently, am I right?

Who are the maintainers of the HA integration? The manifest.json doesn't mention anyone. I'm assuming it's @joopert, but maybe more?

I'd like to improve the integration somewhat by improving the stability and adding an integration flow. Then later I'd like to add more entities.

@joopert
Copy link
Owner

joopert commented May 6, 2023

Hi @rrooggiieerr,

Sorry for the late reply. I've been AFK for a while :)

You are right, not much has been done recently. I do monitor the issues and PR's here, but I've not been checking the HA integration for quite some time.

You're certainly welcome to improve the integration.

@rrooggiieerr
Copy link
Contributor Author

Good to hear back from you. I've already been programming last couple of weeks, have now all options of my receiver available in HA and also a config flow. Not sure how backwards compatible it is though, it's very specific for my model of receiver. You can have a look on my github: https://github.com/rrooggiieerr/homeassistant-nad

Did you know it's actually possible to get the names of the input source from the receiver, so the don't have to be configured in the configuration yaml. There is an undocumented command Source<1-9>.Name=? that gives back the name for that source.

Screenshot 2023-05-06 at 19 25 12

Screenshot 2023-05-06 at 19 39 12

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

2 participants