[BUG] Snapclient service does not start with whitespace in "Host ID" field

[curiousercreative]

Describe the bug

Snapclient service does not start when a value entered in "Host ID" field contains whitespace.

How to reproduce

Steps to reproduce the behavior:

1. Install Snapclient service add-on
2. Configure Snapclient to connect to a snapcast server (perhaps using the Snapcast service add-on on the same Kodi instance)
3. Configure Snapclient with no Host ID and save configuration
4. From LibreELEC shell (ssh), observe service status and command run
   Expected/Actual Result: service is active (running) with command similar to
   snapclient --latency 0 --host 127.0.0.1 --port 1704
5. Configure Snapclient with Host ID "libreelec" and save configuration
6. From LibreELEC shell (ssh), observe service status and command run
   ER/AR: service is active (running) with command similar to
   snapclient --hostID libreelec --latency 0 --host 127.0.0.1 --port 1704
7. Configure Snapclient with Host ID "libre elec" and save configuration
8. From LibreELEC shell (ssh), observe service status and command run
   ER: service is active (running) with command similar to:
   snapclient --hostID 'libre elec' --latency 0 --host 127.0.0.1 --port 1704
   AR:service is failed (Result: exit-code)

System details

• LibreELEC Version: 12.2.1
• Hardware Platform: RPi4.aarch64
• Forum Thread: https://forum.libreelec.tv/thread/29928-snapclient-no-longer-working-in-12-2/

[curiousercreative]

I ended up forgoing the host ID field entirely. If this is picked up, probably makes sense to update the command more thoroughly since hostname and port params are deprecated in favor of unnamed param for server url. So my examples above would become

snapclient --hostID 'libre elec' --latency 0 tcp://127.0.0.1:1704

[curiousercreative]

It's also not clear why output is being redirected.