Official Support for HTD is coming!

With RC3 and RC5 I am no longer able to manually change the source input from the regular Home Assistant media entity card. It is possible the problem exists before that, but this is when I first noticed it. I can adjust volume, power, etc. But source won’t set. I can set it from an automation that doesn’t use the regular entity media card/interface:

I’m seeing the same thing (source changes not “sticking” when changing it with the media card) with my Lync 12.

i’m trying to replicate this with my Lync12 with the plain Home Assistant card and I can’t. can you guys help me out by creating an issue on my github and filling that out? could i also ask for a video recording of how this actually looks and review the logs just to be sure and send anything that could look suspicious? thanks.

I have opened an issue with a screen recording attached.

@UngluedChalice Please have a look at the issue I opened on GIT and chime in if you would.
https://github.com/hikirsch/htd-home-assistant/issues/31

To me, the ability to load the names directly from the HTD hardware settings is more important because that would eliminate a point of confusion and indirection which HA has way too many as it is. There are plenty of UI facilities to label things as desired downstream of the hardware integration. So, the closer an integration is following its hardware’s state, the cleaner.

My “vote” is freedom to name sources. I don’t use the HTD app, except for initial zone setup, and my sources are pretty static, so adding the source naming in the configuration.yaml or where would be all I need. Loading names from HTD hardware would be best of course, but config is enough for me.

Sorry been busy, finally got around to submitting a pull request to python-htd which adds 100% HTD lync feature support

This sounds great! How can I install your updates?

I wonder if Home Assistant's new ability to have serial ports over the network with ESPHome will eventually change the way HTD can interact with Home Assistant?

Hey guys,

With the new found tools in AI, I wanted to try my hand at giving something back to the community, even though I am not a developer by trade.

I have forked hikirsch's repo and implemented all of the features that were requested there. Or at least they are all working great for me. :slight_smile:

I have also released a really basic dashboard card to control a zone from a single card.

If anyone is willing to test for me, I would appreciate it. It is working well in my system.

A huge thank you to kingfetty, for his amazing contribution that made this really easy. I believe he wrote the HomeSeer plugin also, which was really fantastic for HTD control.

Anyway, here are the repos if you want to give them a shot:

Installation is completely manual at this point. I figured I'd wait and see if hikirsch wanted to merge this back into his code line. If he doesn't, I have already started the process to have these published into the mainline HACS repo so they will be directly searchable and installable.

I fully expect to have a few bugs here and there since I only have a Lync 12 to test with. Please report any you might find with as much detail as you can and I will work on fixes as my time allows.

Take care!

@harshl Is there a plan for the eventual integration of your updates into the original repo? I really appreciate everyone’s work on this. I have a Lync 12 and will be testing this in the next few weeks. Thanks so much!

Curious about HTD Lync 12 functionality I used in HomeSeer if this latest version of the Home Assistant integration will allow for:

I used to setup a trigger in HomeSeer if any HTD Zone Keypad hit the DND button HomeSeer would have an event trigger that would take action based on it that would fire off immediately. Can this Home Assistant integration for HTD also immediately detect that a zone has been put into DND and take action?

I do not actually want a zone in DND mode, I only use it as an input button to fire off an automation. I then reset the zone back to not being in DND. It is a way of using a button on the keypads as an input to trigger on the controller.

I just wanted to see if this would still be able to work this way in Home Assistant.

oh my… I feel so ashamed I missed this so long ago. thank you so much for doing this. I will take a look at this within the next few days and test this on my unit and just make sure it works. if all is good, i will happily merge this in!!

I’m very sorry everyone for the delay. it’s been a crazy past few months for me.

–Adam

My repo has been approved and it is up on HACS now. Not sure what that means for the future, but it should be easily and directly installable now.
Installs from HACS seem to be working well. I also updated the README with some instructions on migrating from a manual install to a HACS installation and preserving settings. Pretty straight forward.

While I haven’t tested this specifically myself, I would expect this to work, yes.

I can test it easily this weekend or next week when I have a few cycles. Been working on the road for a while so I am not near my panels to test at the moment.

@Jean-Marie I had a chance to test this today. I just did it remotely. Setup an automation that triggered on DND from a particular panel and sent a notification to my phone. Within 2 seconds of turning on DND, I had a notification on my phone. Should work well for you I think.

@harshl Perfect!! Thank you!!! I will migrate this from HomeSeer! Yay!! That is one less item I need to worry about in this migration. I really appreciate you testing this for me! I use it all the time. I wish the HTD Lync Keypads had other buttons that could be used trigger automations. What I use the DND button for is to tell the home automation controller to pause the music it then also undoes DND mode on the zone that it was pressed on. The benefit is local control (to a very limited extent) of the source that is playing from the keypad. That brings up another question to find out if this is possible.

The keypad has 4 other buttons that don’t do anything unless you are playing an MP3. Does anything get generated by the HTD Lync 12 when any of these are pressed that HA could maybe trigger off of? That would allow people to control their media from the keypad in a basic way like I do with the DND button. Thanks for all your help and thanks to all that have supported this effort!!! You are awesome as is Ultrajones (@kingfetty) for the HomeSeer UltraHTDAudio3 plugin that I used for years! Thank you all!!! :smiley:

@Jean-Marie here is what I have found so far. The buttons are not actionable unless the pad is set to the MP3 source. The play and stop buttons seems to signal commands to the network controller reliably, but the fast forward and backward buttons are spotty. I am suspicious of this being because there are no MP3s on my controller. I am going to load up some MP3s onto the controller as soon as I have a little time and test again to see if those buttons repeat commands back to the network controller reliably at that point.
Regardless, it doesn’t seem ideal to use these as triggers since it must be on the MP3 source to do so.

If, under those restrictions, you still have interest, let me know and I’ll see about getting it implemented.

@Jean-Marie
I have done a ton of testing and it seems that using these buttons would require that the source of the panel be set to the MP3 source, and even after that, only the first press of a button is reliably reported, unless another button is pressed first. For instance, if you press the play button, it will be reported and picked up, but if you try to use the play button again before pressing the stop button, it would not be seen.

I think it would be very unreliable and not worth the effort to implement. If anyone else finds differently and disagrees, I am happy to put in the effort with additional information provided to me.

This also only accounts for these older gen panels. I have no access to the newer panels/controller revisions to see if they behave differently.

I’m going to close the issue out for now. It would have been awesome if it had worked better!