[Bug Report] OpenRGB command line client can't request device listing

Description of Bug

OpenRGB (built today from master) in client mode will not be able to receive the device listing from the server.

Server command line and log:

$ openrgb --server --startminimized
Attempting to connect to local OpenRGB server.
Connection attempt failed
Local OpenRGB server unavailable, running standalone.
Network connection thread started on port 6742
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Network server started
Server connection closed
Network server started
Server connection closed
Network server started
Server connection closed

Client command lines and logs

$ openrgb -l
Attempting to connect to local OpenRGB server.
Connected to server
Network client listener started
Local OpenRGB server connected, running in client mode

$ openrgb -d 0 -z 1 -c 00ff00   # It works as intended in standalone mode, though it takes 5 seconds
Attempting to connect to local OpenRGB server.
Connected to server
Network client listener started
Local OpenRGB server connected, running in client mode
Error: Invalid device ID: 0
OpenRGB 0.51, for controlling RGB lighting.
Usage: OpenRGB (--device [--mode] [--color])...

[...]

Here's a pcap of the loopback interface as well: openrgb-bug.pcapng

OpenRGB has been built from master with the experimental Mystic Light controller enabled (I uncommented the define in Controllers/MSIMysticLightController/MSIMysticLightControllerDetect.cpp).

The issue is present on v0.5 as well.

The issue does not occur if I launch a second instance of the graphical interface and connect it to the server, it works fine.

Also, the server will also start the UI. I don't know if this is intended.

Hardware Configuration

I doubt the issue is hardware related but...

Bus 003 Device 004: ID 1462:7c37 Micro Star International MYSTIC LIGHT

image

I'm running Arch Linux.