Cannot find device

[JackCaster]

Hi, I have the computer and the Neon app connected to the same network but the device does not appear in the device selection:

$ lsl_relay
[12/20/23 10:40:16] INFO     Saving logs to lsl_relay.log                                 cli.py:189

Available Pupil Companion 
         Devices          
┏━━━━━━━┳━━━━━━━━━┳━━━━━━┓
┃ Index ┃ Address ┃ Name ┃
┡━━━━━━━╇━━━━━━━━━╇━━━━━━┩
└───────┴─────────┴──────┘
 Select  Enter index and hit enter
 Reload  Hit enter without input
  Abort  Use ctrl+c and hit enter

I can ping the device IP and I can connect to the stream web interface. I am using Pupil Companion app is at v. 2.7.8-prod and the Neon eye tracker has been updated to the latest firmware.

Do you have any suggestions on how to get it connected?

[mikelgg93]

Hi @JackCaster! Could you confirm you are not in an institutional network?

Can you try connecting to the Monitor App or the Realtime API and letting us know if you can successfully connect?

[JackCaster]

Hi @JackCaster! Could you confirm you are not in an institutional network?

Can you try connecting to the Monitor App or the Realtime API and letting us know if you can successfully connect?

Hi, I am not in an institutional network. I am running the software within a Docker container (Linux Ubuntu), but I can connect to the Monitor app from within it

The video does not load, but this has happened from time to time even when running locally on Windows.

EDIT: I tried to connect to the phone hotspot but still cannot find the connected device.

[domstoppable]

If you can ping the companion device, you should be able connect the LSL Relay to the device directly without relying on mDNS search/discovery. E.g.,

lsl-relay --device_address 192.168.0.123:8080

[JackCaster]

I tried at home, where I am sure the network does not block anything strange. Autodiscovery does not work, but I can connect to the device using its IP. However, I get the error that the RTP is not receiving any data. I remember I had a similar problem with the Python real-time API. The problem disappeared after an update but now I am facing it again (pupil-labs/realtime-python-api#44). So, I think the problem is with the underlying network API. Is there anything I can try to get it working?