Windows 11 PC won't connect to MissYou MS4 hologram fan wifi hotspot

I’m working to get my Missyou MS4 hologram fan (42 cm) to work as a topper for my virtual pinball cabinet. There is an existing GitHub project that would change the image on the fan for each table, and also for individual events while a table is running. I’m initially just trying to get a video to show up for each table. (link below) The project seems to work for older fans. It requires the PC to connect to the fan’s built-in WIFI.

The issue seems to be that Windows 11 won’t connect to the hologram fan’s wifi, so communication can’t happen. The SSID for the fan has a black X and says it can’t connect after asking for the password.

The fan will connect to my iPhone, iPad, or Google Pixel 6a phone, but doesn’t connect to Windows 11 PCs, which is what powers the pinball cabinet.

I’ve tried both the PC’s motherboard wifi, and a USB Wi-Fi dongle with the IP set to 196.168.4.2, the fan has the address 192.168.4.1. Both return “cannot connect to this network”

You want your pinball cabinet to show a different video for each table, and eventually react to game events. An API-capable MISSYOU S-series device covered by the protocol below is a possible route to that goal. We cannot yet confirm that your current 42cm/MS4 supports it, or why Windows 11 cannot join its hotspot.

Your current fan and the Windows connection problem

There are two separate checks: joining the fan’s Wi-Fi network, and having a playback-control interface that the plugin supports. Successful Wi-Fi connection alone would not establish that the plugin can select videos. We want to check your existing equipment first rather than ask you to replace it unnecessarily.

Please share the complete model from the label, the firmware version if available, and a screenshot of the Windows connection error. Hide serial numbers, passwords and personal information. Your report that phones can connect is useful, but it does not establish the cause of the Windows failure.

S-series alternative for table/event-driven playback

The MSXXS4 manual documents an API that selects a stored file to play, with pause, resume, loop-current-file and previous/next-file commands. Videos can stay on the fan’s TF card while the PC sends selection commands; this route does not require live video streaming.

The appendix lists F45, F52, F56, F65, F80 and F100. Those codes must be matched to the actual device and firmware; they are not a guarantee for every S-series model. The FanPlugin.Wrapper code we reviewed uses different protocols, so a developer would need to add an adapter and verify the file-index mapping. Changing only the IP or port is insufficient. We have not completed a hardware compatibility test with this plugin; please do not purchase a replacement solely on the assumption that it will work.

Smallest useful test on a confirmed applicable S-series device

For you or the plugin developer, the original English protocol page is attached below:

  • Enable third-party control in the MISSYOU PC software or app, then power off and restart the device.
  • Connect through a shared LAN or directly to the device hotspot. The documented TCP port is 50200; the hotspot IP is 10.10.10.1. On a shared LAN, use the device’s actual IP.
  • With two files already stored on the device, test file selection using 0x5B 0x06 N. The first file is indexed as 0; verify which actual video each index selects.
  • The manual specifies one instruction per TCP packet.

The first checkpoint is whether the command displays the intended stored video. Only after that works should the developer connect table-change events, then test faster game events and measure switching delay and reliability. If the connection fails or the wrong file plays, stop at that stage and report the result; do not apply these commands to an unconfirmed model.

Next step: please send the model details and Windows error screenshot. If you already have an applicable S-series device available, also tell us the file-selection test result. We will use that information to determine the next step for your existing fan or the API alternative.

API protocol appendix - click the image to enlarge: