TPSR app does not work over a routed network
Issue
Cannot find dimmers using the TPSR app to configure Sensor modules, either by scanning a QR code or by entering Space and Circuit numbers manually.
Other ETC apps (Paradigm Touchscreen Remote, Eos iRFR...) work normally, and it is possible to ping the CEM3 from the wireless device
Explanation of Issue
TPSR uses multicast to discover the requested circuit number. This is because the app doesn't know which rack (and therefore IP address) a given circuit is in. If your wireless device is on a different subnet from the Sensor processors, a router will be used to pass data between these two subnets. The router will normally not pass these multicast requests between network segments.
This is most commonly seen in situations where the wireless access to the lighting network is provided via a wider building network, e.g. a "technical" Wi-Fi SSID, which lives on a different subnet from the lighting devices themselves. It can also occur when using a basic wireless router to create a wireless network for an Eos remote or similar.
Because iRFR/aRFR and the Paradigm remote apps look for a specific IP address (e.g. P-ACP or Eos console), they are not affected by this limitation.
How to tell if you're on different subnets
- Check the IP address of your CEM3 processor(s) (Setup > Network)
- Check the IP address of your wireless device in the WiFi settings page
If these are totally different (e.g. 10.101.101.101 vs 192.168.1.55) or different in the digits where the subnet mask is 255 (e.g. 10.101.101.101 vs 10.7.0.55), then the devices are on different subnets.
Solution
A basic test and/or solution to get up and running quickly would be to add a WAP (wireless access point, NOT a router) to the lighting network itself. For testing, this could even plug into the front network port on a CEM3. This should allow your wireless device to have an IP address in the same subnet as the CEM3s, and the TPSR app should work normally. (NOTE: when connecting through a WAP you'll need to assign a static IP to your device, or start a DHCP server on the network serving IP addresses in the same subnet as the CEM3)
This may not be a suitable idea for permanent installations, due to concerns about range, or wireless interference with the existing building network. In this case, please consult your network designer so they can help resolve this situation using your existing network infrastructure. They can contact ETC technical services for advice.