TRO.Y 2 Programming Guide: Section 3 - Miscellaneous & Troubleshooting

Guide Overview

This guide is divided into three main sections to help you get the most out of TRO.Y 2:

Section 1: Getting Started
Covers discovering your TRO.Y on the network, adjusting basic settings, and adding shades and devices to the system.

Section 2: Programming and Integration
Covers creating groups, programming keypads and remotes, and integrating with third-party control systems.

Section 3: Advanced Programming and Troubleshooting
Covers miscellaneous programming tasks, advanced features, and troubleshooting guides.

TRO.Y Programming Guide

Complete Setup, Configuration & Troubleshooting Guide

Section 1 – Finding the TRO.Y GUI & Setup ▼

Discovery & Initial Setup

• Discovering With a Local Network
• Using a Windows Computer
• Using a Mac Computer
• Discovering Without a Local Network
• Using a Windows Computer
• Using a Mac Computer
• Troubleshooting

Basic Setup & Configuration

• Updating Firmwares
• Network Settings
• User Interface Password
• Time/Date Settings

Adding Shades to TRO.Y

• Discovering RS485 Shades
• RS485 Motor Config
• Discovering Zigbee Devices
• Helen Coordinator
• Adding Zigbee Routers
• Adding Zigbee Shades
• Zigbee Motor Config
• Zigbee Network Configuration
• Adding RTS Shades with Pegasus
• Adding the Pegasus
• Adding RTS Shades

Section 2 – Groups, Remotes/Keypads & 3rd Party Integration ▼

Groups & Scenes

• Creating a RS485 Group
• Creating a Zigbee Group
• Creating a RTS Group
• Creating a Supergroup
• Creating a Scene
• Creating an Event

Remote & Keypad Programming

• Pairing a Remote to Pegasus
• Somfy Remote
• SI KAOS Remote
• Alpha Remote
• Lutron Pico
• Adding a DecoFlex Keypad
• Programming DecoFlex
• Using the GPIO on Pegasus
• Adding a Sensor to Pegasus

3rd Party Integration

• Telnet/JSON Server Settings
• Integrating a Bond Bridge
• Integrating Lutron Systems
• Integrating Control 4
• Integrating Crestron Home
• Integrating Crestron SIMPL
• Integrating Savant
• Integrating URC

Section 3 – Miscellaneous & Troubleshooting ▼

System Management

• Reports & Backups
• Creating a Site File
• Loading a Site File
• TaHoma/Link ProZ Integration

Advanced Features

• 1 Way Serial Commands
• System Integration ID
• Advanced Programming
• Protocols
• HTTP Commands

Troubleshooting

• Zigbee Troubleshooting & Design
• Knowing your Zigbee Environment
• Using Helen Diagnostics
• Changing Zigbee Channels
• Helen Coordinator Won't Initialize
• RS-485 Troubleshooting
• RS-485 General Troubleshooting
• RS-485 Diagnostics
• RTS Troubleshooting
• RTS General Troubleshooting
• Troubleshooting Ghost Signals

Additional Resources ▼

Installation & Setup Resources

• Installing the TRO.Y
• Video Vault
• Firmwares: TRO.Y Helen

Zigbee Design & Troubleshooting Guides

• Zigbee Mesh Design Guide
• Advanced Zigbee Troubleshooting

Section 3

---

Reports & Back-ups

 

---

Creating a Site File

⚠️ Important: Site File will only Backup 485 Devices, Wireless Devices will not be backed up.

1. Click the "Report" button to open the Integration Report menu.
2. From here, you can create, delete, save, and load site files and reports.
3. Reports are saved as .csv files, which work with most spreadsheet programs.
4. These reports include all system settings, devices, and group lists for easy documentation.
5. Click "Create Report / Site Backup" to start the process. It may take 1-2 minutes, depending on your system size.
6. A progress bar will show the status of the file creation/backup.

---

Loading Site Files

🔴 Important: Loading a Site File into TRO.Y / 2 will overwrite all settings.

1. Wireless bridges may take up to 2 minutes to load—be patient.
2. Do not close the browser until the process is complete.
3. After loading, commit the integration table to save changes.
4. TRO.Y / 2 may need to reboot during this process.

Steps to Load a Site File:

1. Click "Choose File" and select your site backup file.
2. (Optional) Check "Apply to RS485 devices only" if you're updating a single RS485 motor.
3. Click "Open" to start the process.
4. A pop-up will ask you to restart TRO.Y / 2—click OK to continue.
5. TRO.Y / 2 will begin loading the site file.
6. If the number of wireless devices in the site file doesn’t match the wireless bridge, a warning will appear—click OK to proceed.

Matching Devices and Groups:

1. Match live devices and groups with those in the site file using the dropdown menu.
2. Click "Commit Matches" when done.
3. Continue until the status bar confirms the site load is complete.
4. Go to the Aggregate Table to verify all devices and settings are loaded correctly.

---

TaHoma or Link ProZ Integration

Wireless Bridge Settings - Link ProZ / TaHoma / TaHoma Switch

1. Open the Integration Settings
   
2. Click “Show” to start the Telnet Server.
3. Select "Link Pro / TaHoma Bridge"
4. Click “Submit” to save your settings.
5. Restart TRO.Y
6. Enter the IP address for the Link ProZ, TaHoma, TaHoma Switch
7. Default Port: 44100

---

1-way Serial (RS-232) Control

How to Set Up Telnet for Serial Control: 

1. Click “Show” to start the Telnet Server.
2. Select "Serial Port"
3. Enter "Baud Rate", "Parity", and "Stop Bits"

Default TRO.Y / 2 Serial Settings:

• Baud Rate - 4800-56K
• Control bit – 8
• Parity –None
• Stop Bits - 1 

💡 Tip: Serial port data output (WHT/BLUE) is the transmit (TX) from (TRO.Y / 2 DCE) on pin 5
Serial port data input (GRN) is the receive (RX) to (TRO.Y / 2 DCE) on pin 6

---

System Integration ID

---

Advanced Programming

Click Here for HTTP Commands

Protocols

General Notes:

• Adding the key "seq" to a command requests position updates for as long as the position continues to change.
• The "seq" number is arbitrary and can be used to reference a specific motor or group. For example, the controller could assign a seq value of 1 to motor 123456, and any position report with seq=1 can be assumed to correspond to motor 123456.
• The seq value must be less than 0x1000.
• Position reports are sent every 5 seconds and continue until the motor position stops changing. The final report will include the key/value pair "eot": true.
• From the controller’s perspective, "Groups" and "Super Groups" function the same way.
• Data is exchanged over a simple TCP connection. The port number is configurable but defaults to the Telnet port (23).
• Heartbeat: If more than 70 seconds pass without Troy receiving any data, the connection times out, and Troy will drop the TCP connection.
• The "id" number should be unique for every message sent. An incrementing value that rolls over at 0xffff is a good choice.

---

Troy Device Communication Guide

ID Request: System

Requests the unique integration ID of the Troy device.

Send:

json

CopyEdit

{"method":"status.intid","id":12037}

Response:

json

CopyEdit

{"result":{"integrationID":"ABCDEF123456"}, "id":12037}

---

Motor "Ping" Requests

Returns a list of registered motors.

General Motor Ping

Note: This does not indicate whether devices are online.

Send:

json

CopyEdit

{"method":"sdn.status.ping","params":{"targetID":"*"},"id":12037}

Response:

json

CopyEdit

{"result":["066666","0628C5","0628C6","0628C7","0628C8","0628C9","0628CA","0628CB","0628CC","0628CD"],"id":12037}

Motor Ping (Using Wildcard Domain)

Note: SDN Domain replaced with *.

Send:

json

CopyEdit

{"method":"*.status.ping","params":{"targetID":"*"},"id":11657}

Response:

json

CopyEdit

{"result":["000001","000002","000003","000004","000005","000006","000007","000008","0628CD"],"id":11657}

Single Motor Ping

Note: This is generally not useful.

Send:

json

CopyEdit

{"method":"sdn.status.ping","params":{"targetID":"000001"},"id":58}

Response:

json

CopyEdit

{"result":["000001"],"id":58}

---

Group "Ping" Requests

Returns a list of registered groups.

General Group Ping

Note: SDN Domain replaced with *.

Send:

json

CopyEdit

{"method":"*.status.ping","params":{"groupID":"*"},"id":11657}

Response:

json

CopyEdit

{"result":["000501","000502","000553","000504","000505","000506","000007","FFFFF0","FFFFF2"],"id":11657}

---

INFO Requests

Motor INFO Request

Send:

json

CopyEdit

{"method":"sdn.status.info","params":{"targetID":"066666"},"id":12037}

Response:

json

CopyEdit

{"result":{"type":"motor","nativeID":"0628C4","label":"MY Label Here3","assignedID":"066666","statusAvailable":false}, "id":12037}

Group INFO Request

Send:

json

CopyEdit

{"method":"sdn.status.info","params":{"targetID":"FFFFF2"},"id":120}

Response:

json

CopyEdit

{"result":{"type":"group","nativeID":"rts.*","label":"All RTS Devices","assignedID":"FFFFF2","statusAvailable":false}, "id":120}

Super Group INFO Request

Send:

json

CopyEdit

{"method":"sdn.status.info","params":{"targetID":"FFFFF0"},"id":120}

Response:

json

CopyEdit

{"result":{"type":"superGroup","targetList":["FFFFF1","FFFFF3","FFFFF2"],"label":"All Devices","assignedID":"FFFFF0","statusAvailable":false}, "id":120}

---

Motor Movement Commands

Move Motor Down

Note: Position reports are spaced 5 seconds apart.

Send:

json

CopyEdit

{"method":"sdn.move.down","params":{"targetID":"000001","seq":3},"id":815}

Response:

json

CopyEdit

{"result":true, "id":815} {"method":"sdn.status.position","params":{"seq":3,"position":0}} {"method":"sdn.status.position","params":{"seq":3,"position":81}} {"method":"sdn.status.position","params":{"seq":3,"position":100}} {"method":"sdn.status.position","params":{"seq":3,"position":100,"eot":true}}

Note: The "seq" number is arbitrary and can be used to track specific motors or groups.

Move Group Up (No Position Updates)

Send:

json

CopyEdit

{"method":"sdn.move.up","params":{"groupID":"000502","seq":12},"id":889}

Response:

json

CopyEdit

{"result":true, "id":889}

Move Group Down (No Position Updates)

Send:

json

CopyEdit

{"method":"sdn.move.down","params":{"groupID":"000502","seq":12},"id":889}

Response:

json

CopyEdit

{"result":true, "id":889}

Stop Group Movement

Send:

json

CopyEdit

{"method":"sdn.move.stop","params":{"groupID":"000502","seq":12},"id":890}

Response:

json

CopyEdit

{"result":true, "id":890}

---

Preset (IP) Commands

Move to Next Preset (Lower Number IP)

Send:

json

CopyEdit

{"method":"sdn.move.ip.next","params":{"targetID":"000001","seq":3},"id":1722}

Response:

json

CopyEdit

{"result":true, "id":1722} {"method":"sdn.status.position","params":{"seq":3,"position":49}} {"method":"sdn.status.position","params":{"seq":3,"position":25}} {"method":"sdn.status.position","params":{"seq":3,"position":25,"eot":true}}

Move to Previous Preset (Higher Number IP)

Send:

json

CopyEdit

{"method":"sdn.move.ip.prev","params":{"targetID":"000001","seq":3},"id":1729}

Response:

json

CopyEdit

{"result":true, "id":1729} {"method":"sdn.status.position","params":{"seq":3,"position":4}} {"method":"sdn.status.position","params":{"seq":3,"position":25}} {"method":"sdn.status.position","params":{"seq":3,"position":25,"eot":true}}

Move to Specific IP

Send:

json

CopyEdit

{"method":"sdn.move.ip","params":{"targetID":"000001","num":3,"seq":33},"id":1729}

Response:

json

CopyEdit

{"result":true, "id":1729} {"method":"sdn.status.position","params":{"seq":33,"position":25}} {"method":"sdn.status.position","params":{"seq":33,"position":75}} {"method":"sdn.status.position","params":{"seq":33,"position":75,"eot":true}}

Motor Position Queries

---

Query Motor Position (With seq)

Send:

json

CopyEdit

{"method":"sdn.status.position","params":{"targetID":"000001","seq":3}, "id":73}

Response:

json

CopyEdit

{"result":25, "id":73} {"method":"sdn.status.position","params":{"seq":3,"position":25}} {"method":"sdn.status.position","params":{"seq":3,"position":25,"eot":true}}

Query Motor Position (Without seq)

Send:

json

CopyEdit

{"method":"sdn.status.position","params":{"targetID":"0628CC"}, "id":73}

Response:

---

HTTP Commands

Important Notice on Sending HTTP Get Commands to TRO.Y / 2

🔴 Important: Be careful when sending any HTTP Get commands to TRO.Y / 2, as incorrect characters can damage your system's site file or disrupt operations. Always backup your site file before sending any commands to avoid potential issues.

Supported Motor Commands:

• UP
• DOWN
• STOP

Command Format:

http://###.###.###.###/troy.cgi?cmd=70&str1=XXXXXX&str2=$$$$

Where:

• ###.###.###.### is a valid IPv4 address (e.g., "192.168.0.100" or "10.10.0.100").
• XXXXXX is a 16-bit node ID on one of TRO.Y / 2's RS485-bus lines, in a 6-character alphanumeric format (e.g., "1001003" or "1A0113").
• $$$$ is the valid ASCII command (e.g., "up", "down", "stop") for the motor.

🔴 Important: Before sending commands, ensure that your network is set up correctly, and your site file is backed up.

---

Here are some simple examples of commands you can use:

• UP Command: http://192.168.1.149/troy.cgi?cmd=70&str1=001003&str2=up
• STOP Command: http://192.168.1.149/troy.cgi?cmd=70&str1=001003&str2=stop
• DOWN Command: http://192.168.1.149/troy.cgi?cmd=70&str1=001003&str2=down

Just replace the IP and node ID with your own, and use the command you need (up, stop, or down).

---

Troubleshooting

Quick Navigation Table

Zigbee Troubleshooting	RS485 Troubleshooting	RTS Troubleshooting
Knowing your environment	General Troubleshooting	General Troubleshooting
Helen Diagnostics	RS-485 Diagnostics	Troubleshooting Ghost Signals
Zigbee Channels
Helen Coordinator Won't Initialize

---

Zigbee Troubleshooting & Design

Additional Resources:

• Zigbee Mesh Network & Troubleshooting Guide
• Zigbee Mesh Design Guide

Knowing your Zigbee Network, and the Environment it's in:

Zigbee 3.0 operates on the 2.4 GHz frequency, which is also used by Wi-Fi, Bluetooth, and other wireless devices. This overlap can lead to interference. Here are the most common causes:

1. Wi-Fi Interference

• Overlapping Channels: Wi-Fi channels 1, 6, and 11 (commonly used) overlap with Zigbee channels 11-22.
• High Wi-Fi Traffic: A busy Wi-Fi network can crowd the 2.4 GHz band, making it harder for Zigbee signals to get through.

2. Bluetooth Devices

• Bluetooth operates in the same 2.4 GHz range and uses frequency hopping, which can disrupt Zigbee communications.

3. Microwave Ovens and TV's

• Microwaves and TV's generate electromagnetic noise around 2.45 GHz, which can interfere with Zigbee signals.

4. Cordless Phones & Baby Monitors

• Some older models use 2.4 GHz and can create interference similar to Wi-Fi.

5. Metal Objects & Thick Walls

• Metal surfaces (like refrigerators, filing cabinets, or mirrors) can reflect or absorb Zigbee signals.
• Concrete, brick, or dense walls weaken Zigbee signals as they try to pass through.

6. Fluorescent & LED Lights

• Some poorly shielded fluorescent lights and LED power supplies can emit radio frequency noise that disrupts Zigbee.

7. Overcrowded Zigbee Network

• Too many Zigbee devices on a single channel without proper spacing can cause network congestion.

How to Reduce Zigbee Interference

✔ Change Zigbee Channel – Use a channel that doesn't overlap with busy Wi-Fi networks (Zigbee 15, 20, or 25 are often good choices). 

✔ Optimize Wi-Fi Settings – Use Wi-Fi on 5 GHz instead of 2.4 GHz when possible. 

✔ Increase Distance – Keep Zigbee hubs and devices away from Wi-Fi routers, Bluetooth devices, and microwaves. 

✔ Use More Zigbee Routers – Zigbee is a mesh network, so adding powered Zigbee devices (like smart plugs or bulbs) helps strengthen the network.

---

Understanding Wi-Fi and Zigbee Channel Overlap

This graph illustrates the relationship between Zigbee channels and Wi-Fi channels in the 2.4 GHz frequency range. Here's how they interact:

1. Wi-Fi Overlaps with Zigbee:
   • Wi-Fi uses channels 1, 6, and 11, each covering a wide range of frequencies (shown in red).
   • These Wi-Fi signals overlap with many Zigbee channels, which can cause interference.
2. Best Zigbee Channels to Avoid Wi-Fi Interference:
   • Zigbee channels 15, 20, and 25 are positioned between major Wi-Fi channels, reducing interference.
   • These are the best choices for a reliable Zigbee network.
3. Why Avoid Overlapping Channels:
   • If Zigbee operates on channels like 11, 12, 13, 17, 18, or 19, it overlaps significantly with Wi-Fi and may suffer performance issues.
4. Higher Zigbee Channels (25 & 26):
   • These channels have the least interference but may have lower power due to regulatory restrictions.

1. Check Your Wi-Fi Channels

• Log into your Wi-Fi router and check which channel it's using (usually under wireless settings).
• Most routers use Wi-Fi Channels 1, 6, or 11, which overlap with Zigbee.
• You can also use a Wi-Fi analyzer app (like "WiFi Analyzer" for Android or "NetSpot" for PC/Mac) to see which Wi-Fi channels are most crowded.

2. Select a Low-Interference Zigbee Channel

• Zigbee channels 15, 20, and 25 are usually the best because they have less overlap with Wi-Fi.
• Here's how Zigbee channels align with Wi-Fi:
  • Zigbee 11-14 = Overlap with Wi-Fi Channel 1 (Bad choice)
  • Zigbee 15, 16 = Mostly clear, slight overlap with Wi-Fi Channel 1
  • Zigbee 20, 21 = Mostly clear, slight overlap with Wi-Fi Channel 6
  • Zigbee 25 = Minimal interference (best if your devices support them)

3. Change Your Zigbee Channel

• Change Network Channel – Select a channel from the dropdown menu and click "Change Existing Network Channel" to apply (this takes about 10–15 seconds).

• 

4. Test & Monitor Performance

• After changing the channel, check if your Zigbee devices respond faster and more reliably.
• If you still experience issues, try moving devices away from Wi-Fi routers and metal objects.

---

TRO.Y Tools to help diagnose Zigbee Issues

Troubleshooting Zigbee Networks Using Screen Innovations Helen Diagnostics & Routing Table

To effectively diagnose and resolve Zigbee network issues in Screen Innovations TRO.Y 2, you can combine insights from both the Helen Diagnostics Table and the Routing Table. Here's how:

Step 1: Identify Offline or Unresponsive Devices

• Use the Helen Diagnostics Table to check if a device is offline ("X" in On/Offline column).
• If offline, cross-check the Routing Table to see if the device is still listed.
  • If it's missing: The device may have been removed or lost connection.
  • If it's listed but has a weak link: The connection may be unstable.

✅ Solution:

• Power cycle the device and refresh the tables.
• Ensure the device is within range of a router or the coordinator.
• If still offline, re-pair the device with TRO.Y 2.

Step 2: Check Signal Strength & Connectivity Issues

• Look at the SILQ (SI Link Quality) column in Helen Diagnostics
  • A low SILQ value means weak connectivity.
• In the Routing Table, check if the device is connected to a weak or distant parent router.

✅ Solution:

• Move the device closer to a stronger router.
• Add a Zigbee router (e.g., powered motor or repeater) between the device and its parent.
• Change Zigbee channels if there's interference from Wi-Fi or other 2.4GHz devices.

Step 3: Verify Parent-Child Relationships

• In Helen Diagnostics, check the Parent column to see which router the device is connected to.
• In the Routing Table, confirm that the parent device is active and has a strong signal.
  • If a device is connected to a weak or overloaded router, communication may be slow or unreliable.

✅ Solution:

• Power cycle the child device to force it to reconnect to a stronger router.
• If a router has too many devices, add an additional router to balance the load.

Step 4: Confirm Power & Battery Status

• In Helen Diagnostics, check the Power column:
  • If a device is running on low battery, it may disconnect randomly.
  • If an AC/DC device shows the wrong power status, it may have wiring issues.

✅ Solution:

• Replace low batteries or check power connections.
• Ensure devices are properly wired to AC/DC power.

Step 5: Look for Routing Bottlenecks or Broken Paths

• The Routing Table can show if devices are overloading a single router or using a weak path to the coordinator.
• If multiple devices rely on one weak router, they may experience delayed or dropped commands.

✅ Solution:

• Add routers to distribute the load.
• Re-pair devices to create better routing paths.
• Move key routers to a centralized location for better coverage.

Step 6: Test Communication & Fix Unresponsive Devices

• In Helen Diagnostics, use the Test RF Group button to check if the device responds.
• If the device doesn't respond, check if its route in the Routing Table is stable.

✅ Solution:

• If the route is broken, remove and re-pair the device.
• Use Zigbee "heal" (power cycle routers to allow devices to find better connections).
• Refresh both tables after changes to verify improvements.

Step 7: Reduce Zigbee Interference

• If multiple devices show low SILQ values, it could be Wi-Fi or Bluetooth interference.
• Check if Zigbee channels overlap with Wi-Fi (especially Wi-Fi channels 1, 6, 11).

✅ Solution:

• Change the Zigbee channel in TRO.Y 2 settings.
• Keep Zigbee devices away from Wi-Fi routers and large metal objects.

By using both Helen Diagnostics & the Routing Table together, you can: ✅ Find offline devices ✅ Identify weak signals ✅ Balance device connections ✅ Resolve power issues ✅ Improve overall Zigbee performance

This method ensures stronger connectivity, faster communication, and a more reliable Zigbee mesh network in TRO.Y 2.

---

When your Helen Coordinator won't Initialize

🔴 Important: Connect the Helen Coordination directly to the Helen port on the TRO.Y 2

🔴 Important: DO NOT use the supplied POE Injector.

• The supplied POE Injector is only used to power Helen's being used as a Router

Check the PAN ID

• Navigate to Wireless Bridge Settings in the TRO.Y2 web interface.
• Look at the PAN ID value:

If it displays "0000", the Zigbee network has not been created. Click the Create Zigbee Network button. The PAN ID should change to a random 4-digit combination (letters/numbers).

🔴 If the PAN ID does not update, try power cycling TRO.Y2 and repeating the steps.

---

RS-485 Troubleshooting

General Troubleshooting Steps for RS-485 Devices:

RS485 is a robust communication protocol, but physical and configuration issues can disrupt communication. Here are general practices for troubleshooting:

Check Wiring & Connections:

Verify Proper Termination: RS485 networks need proper termination at both ends of the bus to avoid reflections and data corruption.

Inspect Cables:

• Make sure the cables used are designed for RS485 communication (twisted pair cables, CrestNet, Lutron or Somfy wires are preferred).
• Inspect for any physical damage, sharp bends, or loose connections in the wiring that could lead to communication failures.

Proper Grounding:

• Ensure that the RS485 devices are properly grounded to avoid ground loop issues.
• Grounding issues can cause communication problems and data noise.

Cable Length:

• RS485 has a maximum recommended cable length, typically up to 300 feet, depending on baud rate and system configuration. If the cable is too long, the signal may degrade, leading to communication failures.

Verify RS485 Settings:

Device Address Conflicts:

• Check that no two devices on the bus have the same address. Conflicting addresses will prevent proper communication.

Test with Known Working Devices:

• If you have spare devices or a simple setup, swap out devices to see if the issue persists, helping isolate the faulty device or wiring.

---

Using the RS-485 Diagnostics Table in TRO.Y

The Diagnostics Table helps troubleshoot communication and device status issues. Here's how to use each field for troubleshooting:

• Native ID – The unique node ID assigned to the motor. If missing, the motor may not be properly discovered.
• Integration ID – The ID that TRO.Y assigns for third-party integration. A mismatch here could cause integration failures.
• Label – The device name. Ensure this is correctly assigned to identify devices easily.
• Type – The type of device (e.g., motor, sensor). If incorrect, there may be a configuration issue.
• Discovery – Shows the status of device discovery. If a device isn't discovered, check wiring, power, and RS485 termination.
• Status – Indicates whether the device is online. If offline, verify power, wiring, and communication settings.
• Port – Displays which BUS port on the TRO.Y the device is connected to. If the wrong port is assigned, communication may fail.
• Test Button – Jogging the shade helps confirm communication. If the test fails, check power, addressing, and wiring.

Use this table to quickly diagnose connection, discovery, and communication problems on your TRO.Y RS485 network.

Systematic Troubleshooting Process:

Identify Problem Motors or Wiring – Use the diagnostics table along with the number of devices and their assigned ports to pinpoint issues. If a motor is not responding, compare its status with other devices on the same bus.

Isolate Issues in Multi-Janus Setups – Instead of daisy-chaining multiple Janus controllers, connect each one individually to the Troy's bus outputs. This allows you to test each Janus separately, making it easier to locate the problem.

Narrow Down the Faulty Motor – Once you've identified a problematic Janus, disconnect all motors and reconnect one at a time, checking the diagnostics table after each addition. This method isolates the exact motor or connection causing the issue.

Inspect Wiring, Connections, and Terminations – Once the faulty motor or connection is found, check all wiring points, terminations, and physical connections. Loose or incorrect terminations can cause RS485 communication failures.

Perform a Continuity Test – To rule out wiring issues, perform a continuity test on the RS485 wiring. This helps detect any shorts, broken connections, or interference that could be disrupting communication.

By systematically isolating devices and verifying wiring integrity, you can quickly diagnose and resolve RS485 communication issues in the Troy & Janus setup.

---

RTS / RF Troubleshooting

RTS (Radio Technology Somfy) operates on a 433.42 MHz frequency, and range issues can be caused by interference, obstacles, weak signal strength, or antenna positioning. Follow these steps to diagnose and resolve range problems:

General Troubleshooting

1. Check Basic Range Limitations

• The typical RTS range is:
  • 30 feet indoors (varies depending on walls and interference).
  • Up to 60 feet outdoors in ideal conditions.
• If your range is significantly shorter, continue troubleshooting.

2. Test Direct Line of Sight

• Stand closer to the motor and try controlling it.
• Move directly in front of the receiver to test if obstacles are reducing the range.
• If the motor works fine at short distances but fails further away, signal interference or obstructions may be an issue.

3. Check for Interference

Common sources of interference include:

• Metal objects (large appliances, HVAC ducts, metal cabinets).
• Thick walls (especially concrete, brick, or metal-reinforced walls).
• Other RF devices (Wi-Fi routers, baby monitors, cordless phones, wireless security cameras).

Solution:

• Move RTS remotes away from interfering devices.
• If the motor or receiver is near metal objects, try repositioning it.
• Turn off nearby RF devices temporarily and retest the range.

4. Check Remote Control Batteries

• A weak battery can cause range issues. If the remote only works at close range:
  • Replace the battery (most RTS remotes use a CR2430 or CR2032 coin cell battery).
  • Ensure the battery contacts are clean and secure.

5. Reposition the Antenna on the RTS Receiver

• Somfy motors have built-in antennas, but external RTS receivers may have an exposed wire as an antenna.
• Tips for better reception:
  • Ensure the antenna is fully extended (not bent or coiled).
  • Position the antenna vertically for optimal signal reception.
  • If the receiver is in an enclosure, move the antenna outside if possible.

6. Try a Different Remote

• If available, test with another RTS remote to see if the issue is with the remote or the receiver.
• If the second remote works better, your original remote may be faulty.

7. Use a Repeater (RF Signal Booster)

• If range is still an issue, a RF Repeater can extend the signal range by retransmitting the RTS signal.
• Install the repeater halfway between the remote and the motor for best results.

8. Reset and Reprogram the RTS System

• If signal issues persist despite troubleshooting, resetting and reprogramming the remote may help.
• Refer to the RTS Wire Free, RTS Low Voltage 50 Series, RTS AC for your specific motor or receiver.

9. Check for Nearby RTS Devices on the Same Channel

• If multiple RTS motors are installed, ensure they are not interfering with each other.
• Try pairing the remote again to ensure a proper link between the remote and motor.

10. Test in a Different Location

• If the motor is near a known RF interference source (e.g., a router or security system), try moving the receiver or testing in a different location.

---

Ghost Signal Troubleshooting

Symptom: Motor Moves Without User Command ("Ghost Signals")

Possible Causes

• Interference from nearby devices operating on 433 MHz frequency (e.g., car remotes, baby monitors, other wireless systems).
• Nearby RTS motors sharing the same address or programmed channel.
• Noise or voltage spikes on the power line triggering the receiver.
• A nearby remote or controller stuck or malfunctioning.
• Third-party automation systems (e.g., home automation hubs, smart control panels) triggering unintended schedules or events.

Step-by-Step Resolution

1. Power Cycle the Motor

• Disconnect power to the motor for 30 seconds.
• Reconnect and observe if ghost signals persist.

2. Clear Programming

• Perform a full reset:
  • See specific motors reset procedure

3. Reprogram with Secure Channels

• Reprogram using a single trusted remote.
• Avoid using old or damaged remotes.

4. Isolate External Interference

• Identify and relocate devices operating near 433 MHz.
• Temporarily disable other RF devices nearby to check if interference stops.

5. Use an RF Scanner for Diagnosis

• Utilize an RF scanner to detect unknown or suspicious RF activity around 433 MHz.
• Monitor spikes or abnormal traffic that could trigger ghost signals.
• Identify and isolate sources such as unauthorized transmitters, faulty remotes, or nearby RF-heavy equipment.

6. Check Third-Party Systems and Automations

• Audit connected home automation systems (e.g., smart hubs, timers, cloud services).
• Review and disable any schedules, scenes, or automation events related to window coverings.
• Confirm that no overlapping events or random triggers are affecting RTS motors.

7. Strengthen Signal Control

• Use official Somfy RTS repeaters if necessary to filter and strengthen desired signals.
• Avoid physical obstacles or reflective surfaces around the motor.

8. Inspect Remote and System

• Ensure no buttons are stuck.
• Remove battery from remotes not in active use.
• Check for corrosion or water damage in remote transmitters.

Additional Tips

• Keep a minimal number of active remotes programmed per motor.
• Record the programming sequence for future reference.
• Regularly audit third-party automation schedules.
• Consult a Somfy-certified technician if ghost signals continue after troubleshooting.

---