Snapclient repeatedly restarting

1st Official Post

    I've got the new LE 9.0 image on my rpi zero w. I can't use it to stream audio because it's turning on and off repeatedly. I can see this when using snapdroid to control it. I think it's something to do with snapclient.start. When I run from terminal ./snapclient-start the restarts occur. However, when I run ./snapclient -d. It works fine.

    Feb 07 10:54:44 zeroELEC sh[612]: metadata:{"STREAM":"Kodi"}

    Feb 07 10:54:46 zeroELEC snapclient[623]: Exception in Controller::worker(): Can't fill params: Invalid argument

    Feb 07 10:54:48 zeroELEC snapclient[623]: Connected to 192.168.222.251

    Feb 07 10:54:48 zeroELEC sh[612]: metadata:{"STREAM":"Kodi"}

    Feb 07 10:54:50 zeroELEC snapclient[623]: Exception in Controller::worker(): Can't fill params: Invalid argument

    Feb 07 10:54:51 zeroELEC snapclient[623]: Connected to 192.168.222.251

    Feb 07 10:54:51 zeroELEC sh[612]: metadata:{"STREAM":"Kodi"}

    Feb 07 10:54:53 zeroELEC snapclient[623]: Exception in Controller::worker(): Can't fill params: Invalid argument

    Feb 07 10:54:54 zeroELEC snapclient[623]: Connected to 192.168.222.251

    Feb 07 10:54:54 zeroELEC sh[612]: metadata:{"STREAM":"Kodi"}

    Feb 07 10:54:56 zeroELEC snapclient[623]: Exception in Controller::worker(): Can't fill params: Invalid argument

    Feb 07 10:54:58 zeroELEC snapclient[623]: Connected to 192.168.222.251

    Feb 07 10:54:58 zeroELEC sh[612]: metadata:{"STREAM":"Kodi"}

    Feb 07 10:55:00 zeroELEC snapclient[623]: Exception in Controller::worker(): Can't fill params: Invalid argument

    Feb 07 10:55:01 zeroELEC snapclient[623]: Connected to 192.168.222.251

    Feb 07 10:55:01 zeroELEC sh[612]: metadata:{"STREAM":"Kodi"}

    Feb 07 10:55:03 zeroELEC snapclient[623]: Exception in Controller::worker(): Can't fill params: Invalid argument

    Feb 07 10:55:05 zeroELEC snapclient[623]: Connected to 192.168.222.251

    Feb 07 10:55:05 zeroELEC sh[612]: metadata:{"STREAM":"Kodi"}

    I was starting it manually because it was doing the above through Kodi's interface. It works find when I start it manually, but it's a hassle.