Sonos Playsers have disappeared

[ape404]

Hi Folks
I am running AirConnect in Docker since many moons. Now all of the sudden all my SonosPlaysers have disappeared. The Docker container is running properly, als a restart with pulling the latest image has not helped. The log is not very helpful either:

2023-08-30T16:56:53.194961462Z [16:56:53.194584] main:912 Starting aircast version: v1.1.5 (May 7 2023 @ 13:42:18)
2023-08-30T16:56:53.218044938Z [16:56:53.217720] main:1367 Starting airupnp version: v1.1.5 (May 7 2023 @ 13:42:38)
2023-08-30T16:56:53.271722759Z [16:56:53.271436] Start:1086 Binding to iface [email protected]:0
2023-08-30T16:56:53.272708220Z [16:56:53.272466] Start:1125 Starting pico HTTP server on port 40455
2023-08-30T17:42:56.800885850Z [17:42:56.798335] main:912 Starting aircast version: v1.1.5 (May 7 2023 @ 13:42:18)
2023-08-30T17:42:57.180461566Z [17:42:57.179911] main:1367 Starting airupnp version: v1.1.5 (May 7 2023 @ 13:42:38)
2023-08-30T17:42:57.264658982Z [17:42:57.264204] Start:1086 Binding to iface [email protected]:0
2023-08-30T17:42:57.265422734Z [17:42:57.265100] Start:1125 Starting pico HTTP server on port 42757

has anyone an idea what I could do or check in order to get the thing fixed?
Thanks for all help
Albert

[philippe44]

You have launched aircast instead of airupnp

[ape404]

I dont unterstand fully. from the log I can see that there are both aircast and airupmp started. How can I influence this and first of all why has it changed without any altering at the Docker image?

[ape404]

Dear Philippe Still have the same situation – no airplay at all. Do you have an idea what could be done? Here again the logs of the container after 3 restarts: [18:03:34.960074] main:912 Starting aircast version: v1.1.5 (May 7 2023 @ 13:42:18) [18:03:34.973559] main:1367 Starting airupnp version: v1.1.5 (May 7 2023 @ 13:42:38) [18:03:35.026334] Start:1086 Binding to iface ***@***.***:0 [18:03:35.027161] Start:1125 Starting pico HTTP server on port 33965 [11:55:19.272583] Stop:1155 terminate update thread ... [11:55:19.272838] Stop:1160 flush renderers ... [11:55:19.272900] Stop:1163 terminate libupnp [11:55:19.775710] Stop:1182 terminate main thread ... [11:55:22.032468] main:912 Starting aircast version: v1.1.5 (May 7 2023 @ 13:42:18) [11:55:22.048997] main:1367 Starting airupnp version: v1.1.5 (May 7 2023 @ 13:42:38) [11:55:22.101889] Start:1086 Binding to iface ***@***.***:0 [11:55:22.102760] Start:1125 Starting pico HTTP server on port 33501 [11:14:05.339739] Stop:1155 terminate update thread ... [11:14:05.340120] Stop:1160 flush renderers ... [11:14:05.340211] Stop:1163 terminate libupnp [11:14:05.843046] Stop:1182 terminate main thread ... [11:14:07.485426] main:912 Starting aircast version: v1.1.5 (May 7 2023 @ 13:42:18) [11:14:07.633065] main:1367 Starting airupnp version: v1.1.5 (May 7 2023 @ 13:42:38) [11:14:07.686077] Start:1086 Binding to iface ***@***.***:0 [11:14:07.686967] Start:1125 Starting pico HTTP server on port 36315 Von: philippe44 ***@***.***> Gesendet: Donnerstag, 31. August 2023 14:19 An: philippe44/AirConnect ***@***.***> Cc: ape404 ***@***.***>; Author ***@***.***> Betreff: Re: [philippe44/AirConnect] Sonos Playsers have disappeared (Discussion #485) You have launched aircast instead of airupnp — Reply to this email directly, view it on GitHub <#485 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF7YXBANUGJQJTCYI2RTIATXYB6NDANCNFSM6AAAAAA4F63LUM> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AF7YXBDSCDX5273YS4GIKBLXYB6NDA5CNFSM6AAAAAA4F63LUOWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQANDT4C.gif> Message ID: ***@***.*** ***@***.***> >

[philippe44]

It's an "old" version you are running. I've updated it since. Where do you take that docker image from? It probably has something to do with the network interface being used or the docker mode (host)

[ape404]

Hi Philippe
I have relaunched all my SONOS players after I have set them into original status. Now airconnect works again. It seems to me that they have joined a different network (?), but how could this have happened? Anyway now everything is fine again and you can close this issue.
Thanks and by