"Channel data is not in expected format" errors

[wjwaldron]

I have been having issues recently with the plugin. Attempting to browse channels, I often get a login failed message. Looking at the plugin log, I see:

[04.10.2025 10:11:51.129] ERROR <siriusxm.proxy>: Channel data is not in expected format - received: undef
[04.10.2025 10:11:52.392] ERROR <siriusxm.proxy>: Channel data is not in expected format - received: undef
[04.10.2025 10:11:54.685] ERROR <siriusxm.proxy>: Channel data is not in expected format - received: undef
[04.10.2025 10:11:58.976] ERROR <siriusxm.proxy>: Channel data is not in expected format - received: undef
[04.10.2025 10:11:58.976] ERROR <siriusxm.proxy>: Channel data format invalid after 3 retries

Restarting the proxy from within the plugin settings doesn't fix the issue, but stopping and restarting LMS does.

In case it matters, I'm running my server on Windows 11.

[paul-1]

Sorry I did not have notifications turned on for this repo. Are you still seeing this?

[wjwaldron]

Actually, I am not -- and I was remiss in not following up here.

What resolved the problem was a re-installation of the plugin. Since it didn't seem to be a common issue, I assumed it was something related to my system. I had been using a manual download/install into the server plugins folder (C:\Program Files\Lyrion\server\Plugins on my Windows box). I decided to remove that and just install via "manage plugins" (i.e., into C:\ProgramData\Lyrion\Cache\InstalledPlugins\Plugins), as most people would do.

In the almost two months since I did that, the problem hasn't reappeared since. I haven't felt the need to examine the code to see if I could determine a possible reason for this...and since I'm sure very few people ever install the plugin manually, it's probably not worth your time, either. :)

[wjwaldron]

Actually, I am not. I just left a comment over at GitHub with more details. Thanks again for this plugin! Bill

…

On Thu, Jan 8, 2026 at 3:16 PM paul-1 ***@***.***> wrote: *paul-1* left a comment (paul-1/plugin-SiriusXM#54) <#54 (comment)> Sorry I did not have notifications turned on for this repo. Are you still seeing this? — Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABD3PRCROCTLLWJKH4UV4UD4F23LPAVCNFSM6AAAAACIJAYOX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMRVGU4TOMJZG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[paul-1]

as long as the Bin/sxm.pl is in the same folder as the plugin.pm, then it should find it. I'll do some some checking.

[paul-1]

I've installed manually and through plugin manager, and it always finds the proxy. So not sure, if you want to play, you can increase logging levels. But if the plugin manager works, then there isnt much of a reason to not use it.

[wjwaldron]

When I have some time, I may try the manual install again, just for kicks -- and to see if the intermittent issue returns and the log would indicate something. But for now, I'm happy to stick with the install I have -- the plugin has been working very reliably. Thanks again for developing this -- while the python proxy worked fine, your solution with the integrated metadata from xmplaylist (and not having to manually keep up with occasional channel changes) is much nicer.

…

On Tue, Jan 13, 2026 at 5:01 PM paul-1 ***@***.***> wrote: *paul-1* left a comment (paul-1/plugin-SiriusXM#54) <#54 (comment)> I've installed manually and through plugin manager, and it always finds the proxy. So not sure, if you want to play, you can increase logging levels. But if the plugin manager works, then there isnt much of a reason to not use it. — Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABD3PRHTRBL4QXKHNLNNEZ34GVTKNAVCNFSM6AAAAACIJAYOX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONBWG42TKOBQGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>