Proper config in Xlights for FPP with eth and wifi

[BrianA]

I am wondering what the 'proper' way to configure a FPP on a Rasberry Pi 3 with wifi should be.
The FPP is the player and connects to the isolated show network via eth0. The wifi connects to my local network, where my desktop running Xlights is.

I have tried setting the IP as the show network (10.1.1.2) and the proxy to its wifi connection (192.168.1.201), and just setting the ip to the wifi connection.
Either way I get a notification:
Abnormal Conditions - May Cause Poor Performance
UDP Output set to send data to myself. Disabling 10.1.1.2
(or it disables 192.168.1.201, depending on the setting in Xlights)

Is this something that I can ignore, or is there something I can set that makes things happier? I am running the lastest FPP (7.3.1)

[JonD]

Is this something that I can ignore, or is there something I can set that makes things happier?

Not something you can ignore.  Did you FPP Connect select "UDP Out = All" and upload channel data to the FPP?

[Poporacer]

Is this something that I can ignore, or is there something I can set that makes things happier?

There could be a couple issues. Is your FPP an actual controller? By controller, that means that pixels are wired directly to the FPP. If not, you probably have the FPP listed as a controller in xLights. If it is NOT a controller, I would suggest removing it from xLights. If it IS a controller, then set the Active status to xLights Only.

[BrianA]

There is a Pi Hat on the FPP, so it is a controller and a player.

UDP Out was set to None, I changed it to all with no difference.

When I do FPP Connect, it sees the controller twice. Once for each IP address.

When I run discover in XLights, I get:
The discovered controller matches and existing controllers IP address but has a different description.
Do you want to update the description in xLights?

If I say yes, it ends up adding both IP addresses as controllers.

[Poporacer]

There is a Pi Hat on the FPP, so it is a controller and a player.

Thanks, how about a screenshot of your controller's page in xLights so that we see when you have going on? (A screenshot and not a picture please, pictures are hard to see.)

UDP Out was set to None, I changed it to all with no difference.

The correct setting for that will depend on what we see in the screenshot.

When I do FPP Connect, it sees the controller twice. Once for each IP address.

That is normal.

When I run discover in XLights, I get:
The discovered controller matches and existing controllers IP address but has a different description.
Do you want to update the description in xLights?

You have to be VERY careful using the Discover button, if you are not 100% certain what it does or is functionality, DON'T use it.

If I say yes, it ends up adding both IP addresses as controllers.

LOL, exactly what I just mentioned above....It can create havoc on your show!

[BrianA]

One thing I am still not clear on is if it should be set in XLights to the show network and its own wifi address as the proxy, or just use the wifi  address.

Screenshot of current settings attached.

[BrianA]

I think I figured it out.
I have the Pi configured using it's wifi address in XLights
When I upload I do not select the show network IP of the Pi
and I select 'proxied' for UDP out on the Pi with 'None' for the other controllers.

Now I am not getting any warnings/errors.

Thanks for the input. It helped me look in the right direction.

[Poporacer]

One thing I am still not clear on is if it should be set in XLights to the show network and its own wifi address as the proxy, or just use the wifi  address.

Without knowing what your network configuration is, we can just speculate. It looks like your FPP-Globes is your main player that you are connecting to your home computer via Wi-Fi and then you are using that as a "bridge" to get to your other controllers? If so, in xLights, the IP address for your FPP-Globes will be the Wi-Fi address. No Proxy
A Proxy is only used when you need to connect from one subnet to another. If you are connecting like I assumed AND using a proxy then your other controllers would need the proxy configured. (a proxy is just one of at least 3 methods to route network traffic)

[james-s]

If you look in the FPP Manual there is a section toward the end about exactly what you are doing with eth() and wan().   I just spend an hour or so trying to move from using DHCP for both eth() and wan() where my main show player would drop of my network.  I am using multisync across one show player and two remotes and I found a section in the manual how to set the eth() to DHCP and static to wan().   So far I am not seeing any drop out for the show player/controller combo.   xLights controller shows all using the static controller addresses and I just uploaded models to each with no issue.  Also able to use the DNS name to get to each with a browserl

Show player - RPi 4+, Falcon PICap
Remotes - 2 x RPi 4+, Kulp K8-Pi