I have an RTI system that I need to troubleshoot and unfortunately the original installer is MIA.

I consists of an XP6 controller and AD-8X.

Everything else (lights, alarm, IR, thermostat, etc) is still working, but audio distribution isn't working.

The problem seems to have arrived after replacing a bunch of network equipment after a storm surge but I can't say 100% that it's related as I hadn't tested it immediately before or after the replacements.

Normally I would be able to open the RTI iphone app, select a room and tell it to stream Sonos and it would play.

Now when I select a room and hit play, it's silence...

BUT if I log into the AD-8X web GUI using it's IP address, I can toggle the zone on manually from there and the music plays. So the AD-8X, music source, wiring, and speakers seem to be fine.

It just seems like the XP6 and AD-8X may not be communicating correctly. Again, I can still control the lights and other things from the iphone app, so I would say the connection from the app to the XP6 is ok too.

Can anyone offer guidance? Or possibly (paid) remote support?

Is the ad8 being controlled via the network or RS232.

If it is network controlled I have seen ad8’s take a couple hard reboots to get them to sync up with the processor.

Also if you’ve changed network components around and the IP address has changed you will need it to match what is in the program file.

Thanks for the reply.

It's controlled over the network.

I have rebooted before but I will try it a few more times.

Is the only way to view the program file to download it with Integration Designer software? If I am not mistaken, the AD8 was on DHCP before it stopped working.

The AD8 would have been on a static IP address. Otherwise the controller wouldn't know where to find it and it wouldn't work (just like what is happening now).
This could have been set in the AD8 or a DHCP reservation in the router. Sounds like it was set in the router that got erased when equipment was replaced.

If there was no documentation that was left for you from the original installer (BS hack) and you have no idea what the original IP address on the network was; then yes you are going to need the Integration Designer software and make the changes to the XP6 to get it to communicate again. And set a static IP in the AD8!

From the AD-8X installation manual:

"Setting a static IP address is NOT necessary and is discouraged. The RTI two-way driver uses the UPNP name of the AD-8x to find it on the network so a static IP is unnecessary."

Is this not accurate?

I am 99% sure the AD8 itself was set to DHCP (it's static right now just from me trying to troubleshoot) but you may be right about a DHCP reservation in the router. Unfortunately it's smoked so I can't look it up.

In theory, if I had a copy of Integration Designer, would I just connect to the XP6 via USB and download the program file? Then somewhere inside the file it would show what IP it expects the AD8 to have?

I haven't done RTI in a very long time. I can't remember if the XP6 could be set with a password or not. That would be the only thing that could get you, is if the previous installer set a password on the XP6 (if that was possible). Then you would have to reset the XP6 and program from scratch. That is not something a normal consumer can do without a lot of instruction and experience (especially since you said you have lighting & HVAC controlled as well).
But if it has no password, then yes you can connect to it with the ID software and see how everything is configured.

Since the AD-8x uses UPnP with the XP6, then technically it shouldn't matter the IP address. And maybe Diskreet's advice of just keep rebooting it until it connects again, will eventually work. But it seems to me, if it hadn't done it after 2-3 times then something's wrong.
Might also check and make sure UPnP is turned on in the router. A lot of routers these days are coming with UPnP turned off by default. That would make this not work.
As far as static IP goes.... You should still set up static IPs for ANY equipment that is a permanent part of the network and on 24/7. Bonus points for doing VLANs with a managed switch and separating out streams, IoT, control, etc. for a more efficient & secure network. And document everything! That's just good practice regardless of the stupid $hit manufactures sometimes say.
Sometimes when dealing with crappy manufacture that their product just barely works on a network, you might have to follow advice to not set a static IP in the device itself - but you should still set a DHCP reservation to make it static on the network.

[edit] If you don't already know - a LOT of AV manufacture (even the really good ones) struggle sometimes with network stuff. They just don't have the talent in-house to have great networking results. A lot rely on 3rd party design for their network interfaces with firmware/software. Many examples thru the years of great products with crappy & troublesome network issues.

You can try to check diagnostic page and view the logs , also check if the router have Ad8x as DHCP or static , if the device itself set to be DHCP you will need to map that in the DHCP server so it wont change , if you still need help with it give me call or text 7148609866 .