My two-way integration project to a RTI processor and remote. It’s quite custom to my own system, but hopefully people can take the foundation and examples here and apply it to their own projects.
1 Like
This is awesome. Thanks for sharing!
1 Like
Have Got a RTI XP6 have got the RS232 port 2 attached the GATEMAN DDL N Protocol 2 Way RF Link which works fine for Opening the YALE 4109A Lock using RF but want to have it integrated with Home Assistant so that i can use the RS232 Port of the RTI to trigger for Opening and Closing the Locks via Home Assistant Only kindly guide
Hi, anyone here who can help me to integrate the integration in HASS? I tried it, but no accceptance of the system.
I put this in the configuration.yaml:
#=======RTI Remote=======
remote:
- platform: rtiremote
name: Wohnzimmer_RTI # Name der Fernbedienung
host: 192.168.8.160
port: 5000 # Standardmäßig 5000Weitere Optionen:
device_code: <Gerätecode> # Falls erforderlich
activities: # Definition von Aktivitäten
- name: <Name der Aktivität>
commands:
- <Befehl 1>
- <Befehl 2>
All files from the download are here:
custom_components/rtiremote
I didnt get no entry under “integrations”
Thanks for help…
regards, ingo
That’s doable.
- Setup a Rx driver in Integration Designer using the RTI two-way-strings driver and make two listeners.
RX String 2 Name | door lock
RX String 2 | door
RX String Variable Type | Boolean (enter string to make the boolean true)
RX String 2 Prefix | door:
RX String 2 Suffix | :cmd
Rx String 2 True Result | lock
RX String 2 Name | door unlock
RX String 2 | door
RX String Variable Type | Boolean (enter string to make the boolean true)
RX String 2 Prefix | door:
RX String 2 Suffix | :cmd
Rx String 2 True Result | open
-
Send strings from Home Assistant to the TCP port you setup on the RTI two-way-strings driver using the method of your choice (YAML, NondeRed, Pyscript, etc) The string for lock would be “door:lock:cmd” and the string for unlock would be “door”:open:cmd".
-
In Integration Designer Two-Way Strings “Driver Events”, just make event macros using your existing RTI driver that listen for these two events.
This project does not use the ‘custom components’ feature of HA. The programming on the HA side and the RTI processor need to be very tightly coupled in a very specific way, so a generic custom component just didn’t make sense to me at the time.
As stated in the Readme, there’s no way to make the two systems automatically talk to eachother out of the box, at least without access to the RTI SDK, which is only avaialbe to approaved developers in the RTI ecosystem.
I’d love to collaborate with someone who is RTI Driver Development Program certified and has access to the SDK to discuss making this dream a reality.
Hi,
I am doing something simliar to control virgin media and apple tv using RTI and works well but i cant for the life of me get data sent from node red to the RTI processor
may i asked how you have managed to get a TCP out node connected to the processor
chas
I just have the “two-way strings” driver in RTI listening on the same port. The RTI processors’ webserver is pretty helpful for debugging as it will show you the raw data that the driver last received. Any step in particular you’re having trouble with?
Wow, this is golden! Thanks @mefranklin6!
I have an aging RTI system and have been anticipating making a shift to something new and after much research I settled on Home Assistant. As @mefranklin6 indicated, RTI makes some great hardware. I have an XP-6 controller, several handheld zigbee remotes, several in-wall controllers and 12 zones of multiroom audio (one AD-8 and one AD-4), all RTI equipment. While setting up my HA Green system I started seeking out compatibility options for my core systems which also include Lutron lighting and DSC security both of which I found integration solutions for. When I came across this RTI integration I was ecstatic that someone had put what appears to be an enormous effort into a great solution and shared it!
Being new in the world of HA, python and yaml it took me some time to get up to speed enough to be able to implement this integration but I have achieved success with the connection and am sending some basic data/commands back and forth.
Because both HA and RTI are now talking with Lutron and DSC my main objective is to create a smooth audio integration with seamless control from either system. The RTI amplifiers have driver commands for:
- Input sources (x8 but I’m only using 4)
- Power on / off
- Volume + / -
- Treble + / -
- Bass + / -
- Balance l / r
- Mute on / off
-Multiplied by 12 zones this quickly exceeds the 100 string limit that the RTI Two Way Strings driver can support.
I expect it should be possible to multiplex commands and parse them within RTI. For example send a ‘vol_up:bdrm’ with the room being the variable. This could greatly reduce the number of Strings required by the driver.
I’m just not sure how to approach this and am hoping one of you experts out there might be able to shed some light on this for me?
BTW it wouldn’t be necessary to implement bass, treble and balance due to the fact they are rarely adjusted and could therefore be tweaked directly as required within RTI .
Thanks in advance, I’m looking forward to the next steps with this project.
@FrontierFred I’m happy to hear that! Thank you for your kind words!
I can think of four options that might solve your problem:
- Programming over 100 entries in Two-Way-Strings sounds like a nightmare, but it’s technically possible since you can load multiple Two Way Strings drivers in a project. The only catch is that they would be listening and sending on different ports. If your strings are all unique, you can simply have HA multicast to all the ports listening without having to keep track of which port can receive what command, and back in NodeRed you can set up multiple TCP listeners that flow into one event fire node. Of course there’s multiple ways of doing this, but for simplicity, I would set up something like this, presuming you would use 4x Tx drivers and 4x Rx drivers:
Alternatively the optimized approach here would involve one driver per zone, one NodeRed Tx per driver, one NodeRed Rx per driver with its’ own “Fire Event” node, and one Pyscript event subscription per NodeRed listener. That’s if you want to do it ‘properly’, but the above simple example will be more than sufficient at this scale.
-
Your system could possibly be greatly simplified by using a different RTI driver. Others have used a third party driver called HTTP Commander here: Remote Technologies RTI XP3 with several PCM-4 - #19 by dskudrin I don’t have any experience with third party drivers so I can’t tell you if it works or not. Maybe dskurdin on here could help you out?
-
Let’s think about this a different way. Why do we need to go through the RTI controller at all? Those devices use RS232, so if you can find the API maybe you can use something like a GlobalCache IP to Serial adapter. Someone figured out the AD-8X over IP here: My Solution for RTI AD-8x Control in Home Assistant In my experience, actual command strings for traditional AV devices like this one are the same between RS232 and IP, so you can try reverse engineering the above project. It seems pretty simple, like muting zone 2 is “*ZN02MUT01”. I bet AI could get you all the strings you need from the above project.
-
Let’s get even further out of the box, literally. Are your amps being fed by RCA? Maybe control the source through HA and use the AD units as dumb amplifiers. All the commands you described (except power on/off) can be done ‘upstream’ before the signal hits the AD boxes if you have the right source device. Just leave the amps on at unity gain with no processing and handle the processing in whatever source device you’re using upstream. If you really want to add power on/off, devices like this can typically be safely controlled through a relay controlled switched outlet, which there are plenty of HA compatible options.
Hope this helps! Let me know if you have any other questions.