I have an all UniFi network, except I use a Synology RT1900ac as an access point for my Pronto’s. By using a dedicated AP for Pronto’s, I can customize settings for the Pronto’s that work better for my them. The only devices that use it are my Pronto remotes. I setup MAC filtering to only allow the Pronto’s to use the Synology AP. I also hide the SSID so others don’t try to connect to it. My Synology AP is connects to a UniFi Port which assigned to a Pronto specific VLAN. My RFX9600 is on the same Pronto VLAN. For additional security, I have firewall rules so that devices in the Pronto VLAN can only talk to a very specific list of IPs. These are the IPs that my Pronto can talk to directly but aren’t in the Pronto VLAN, like my madVR Envy, Kaleidescape, Plex server, etc. This provides additional security. I used to get a lot of “Command Failed” errors until I moved my Pronto’s to its own Pronto VLAN. Once I moved my Pronto’s to their own VLAN, no more Command Failed! I was thrilled to get the good old reliable Pronto behavior that I had in the past. I think one thing that made a big difference is turning off IGMP snooping in my Pronto VLAN.

When I use WPA, it always takes time for the Pronto to connect to Wi-Fi whenever its screen was off, and I press a hard button. the very first press doesn’t work, and then I have to press the hard button a second time for the command to work. Does anyone using WPA get this behavior still (needing to wait for Pronto to connect to via WPA before a remote command can be sent)? I use DHCP reservations for my Pronto’s (using static IPs didn’t make a difference). But with WEP, there is no delay.

EDIT: another thing I did recently is to simplify the work done by my Pronto’s. I had code that had to communicate with multiple RS232, IR, and IP devices simultaneously (like half a dozen or more devices), such as part of shutdown or startup, and the processing got slower and less reliable. I started using Home Asssistant to integrate with all my Home Theater components, and wrote HA automations to do heavy lifting like watch activities and shutdown tasks. Now, the Pronto only needs to send one command to HA, and HA does the heavy lifting. My Pronti works more reliably and overall performance is much faster. This saves me from having to do as much custom use as before. For example, instead of writing my own ProntoScript to control Lutron Caseta devices and Nvidia Shield via IP, I instead have HA control those devices via IP and my Pronto just sends commands to HA (but for some commands like Apple TV, I still use the IR commands from Lyndel).

Randman, thanks for your comment!
The way it looks now, my Raspberry will take the role of your Synology access point, so it's a quite similar setup.
I am also planning to deploy separate VLANs for IoT devices, entertainment, services and end-user devices - the Pronto will be in a very restrictive environment.
It still needs some planning, I'm not quite there yet.

I'm also a long-time Home-Assistant user - it's the same for me: I have offloaded nearly all automations to HA and I'm usually using the Pronto to trigger HA functions (eg. controlling Hue lights).

That said, I do mostly use the Pronto for IR stuff and only have a couple of network-related functions implemented. I don't have any RFXs though...

Regarding the slower connection establishment when using WPA, it's the same for me - I'm also using DHCP, so it takes about 1-2 seconds when the Pronto is picked up.
It's not an issue for me since I mostly run IR commands, so, for example, I do not have any network-based play/pause commands where responsiveness would be a key requirement for me.

On the other hand, WEP is basically an open network and especially in a residential area an invitation to take a look. MAC filtering is equally useless from a security standpoint. So there's no alternative to WPA2 for me, but it's different for everyone.

Last time I tested WPA, using static iP versus DHCP reservation didn't make a difference when the Pronto wakes up. The first hard button pressed when the screen is off fails and the button needs to be pressed a second for the command to work (my hard buttons are either iP or RS232/IR that go through the RFX9600. I'm curious if other folks have experienced faster WPA2 Wi-Fi connection time if using static IP versus DHCP reservation.

The one thing I wish the Pronto supported is faster Wi-Fi. Oh well, considering this remote came out circa iPhone 1 is pretty amazing.

My AP is set to the lowest transmit power, and my Wi-Fi isn't useable outside my property, fortunately. I also have firewall rules to limit the blast radius in case of a security issue (my Home Assistant is focused only for Home Theater gear, and not doors, for example).

For your Pronto WiFi. Do you also want to configure a vlan on the wireless adapter? Would this force any thing that connects to a single vlan?

[Link: networkmanager.dev]

Hi Lyndel,
I'm assuming you are referring to the Raspberry Pi setup.
I did not configure a VLAN on the wireless adapter - I'm not sure this is even possible or feasible (to separate wireless clients, you would probably rather create multiple virtual APs).
You could probably set up the VLAN on the Ethernet connection of the Pi and then have the Pi join that specific VLAN (and all the wireless clients with it - the network beyond the LAN side of the Pi only sees traffic from the Pi and is unaware of the wireless clients).

In my UniFi network, I have created several VLANs, one of which is used for all the AV stuff (AppleTV, Denon AVR, Kodi box, etc. - and also the Pi access point for the pronto).
I configured the VLAN on the switch port where the Pi is plugged in, the Pi then automatically is assigned an IP address from the AV VLAN range via DHCP.
If you use unmanaged switches or connect the Pi to a trunk port carrying multiple VLANs simultaneously, you would probably need to set up VLAN tagging on the Pi's ethernet port.

My Synology AP, which my Pronto’s connect to, has no knowledge of VLANs (it’s configured as an access point and not a router). The UniFi switch port that my Synology AP is connected to is assigned to my Pronto-specific VLAN. Likewise, the UniFi switch port that my Pronto RFX9600 is connected to is also configured with the same Pronto VLAN. My original intention of setting up the Pronto VLAN was for security purposes, but I was pleasantly surprised that my Pronto TSU9400 became much, much more reliable after moving them to their own dedicated VLAN. I stopped getting “Command Failed” errors (due to no reply from the RFX9600). I turned off IGMP snooping on my Pronto VLAN, which I suspect was causing the Command Failed problems. Some devices that my Pronto talks to via IP are in another VLAN, but I have firewall rules to only allow the Pronto’s to talk to specific IPs, mitigating potential security problems.

Also note that UniFi doesn’t support WEP anymore.