[GH-ISSUE #139] Adding a 2nd Stereo Extension uses same Serial as first? #78

Closed
opened 2026-02-27 19:28:16 +03:00 by kerem · 7 comments
Owner

Originally created by @tobsch on GitHub (Jan 25, 2026).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/139

Check the screenshot. I wanted to add more channels and thus needed another extension, but it uses the same serial as the first and disappears on reload.

Image
Originally created by @tobsch on GitHub (Jan 25, 2026). Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/139 Check the screenshot. I wanted to add more channels and thus needed another extension, but it uses the same serial as the first and disappears on reload. <img width="1232" height="1482" alt="Image" src="https://github.com/user-attachments/assets/6cf49cbd-7901-452f-8831-f5ee78be03e4" />
kerem 2026-02-27 19:28:16 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@rudyberends commented on GitHub (Jan 25, 2026):

ok, that is a bug. this beta release introduces dynamic Mac addresses, but apparently this goes wrong for extensions. I will fix this in the next beta.

It's not really an issue though. just add it with 69 in loxone config and after saving and reboot it will show up in the audioserver

<!-- gh-comment-id:3797128171 --> @rudyberends commented on GitHub (Jan 25, 2026): ok, that is a bug. this beta release introduces dynamic Mac addresses, but apparently this goes wrong for extensions. I will fix this in the next beta. It's not really an issue though. just add it with 69 in loxone config and after saving and reboot it will show up in the audioserver
Author
Owner

@tobsch commented on GitHub (Jan 25, 2026):

Cool, thanks!

<!-- gh-comment-id:3797140314 --> @tobsch commented on GitHub (Jan 25, 2026): Cool, thanks!
Author
Owner

@tobsch commented on GitHub (Jan 25, 2026):

BTW: If I add 3 zones at once, it does it correctly. It just always starts again with :68. If I hit reload, zones are gone and it restarts with :68, even though 68 is already "persisted and being used".

I did as you told me and added them to loxone - they do not show up in lox-audioserver now anymore after reloading.
Just the first stereo extension is there and stays there.

<!-- gh-comment-id:3797159574 --> @tobsch commented on GitHub (Jan 25, 2026): BTW: If I add 3 zones at once, it does it correctly. It just always starts again with :68. If I hit reload, zones are gone and it restarts with :68, even though 68 is already "persisted and being used". I did as you told me and added them to loxone - they do not show up in lox-audioserver now anymore after reloading. Just the first stereo extension is there and stays there.
Author
Owner

@rudyberends commented on GitHub (Jan 25, 2026):

They are just placeholders to guide the user through the process. They are in memory only, until they are pushed by the miniserver. They do not mean anything other than to provide the user with a serial to use. If you just add 5 extensions with unique serials and save it in the miniserver, they will show up in the audio server. but like before, you need to drag their outputs to create player blocks

<!-- gh-comment-id:3797173408 --> @rudyberends commented on GitHub (Jan 25, 2026): They are just placeholders to guide the user through the process. They are in memory only, until they are pushed by the miniserver. They do not mean anything other than to provide the user with a serial to use. If you just add 5 extensions with unique serials and save it in the miniserver, they will show up in the audio server. but like before, you need to drag their outputs to create player blocks
Author
Owner

@tobsch commented on GitHub (Jan 25, 2026):

Ahh, interesting. Okay, after adding audio players to the room it actually works. sorry for bothering.

<!-- gh-comment-id:3797232779 --> @tobsch commented on GitHub (Jan 25, 2026): Ahh, interesting. Okay, after adding audio players to the room it actually works. sorry for bothering.
Author
Owner

@rudyberends commented on GitHub (Jan 25, 2026):

Yes that is not something I invented. It's just how loxone works. Those player blocks are the building blocks of the audioserver. That is what you see in the loxone app. We manipulate the state of that player by using those inputs

<!-- gh-comment-id:3797271816 --> @rudyberends commented on GitHub (Jan 25, 2026): Yes that is not something I invented. It's just how loxone works. Those player blocks are the building blocks of the audioserver. That is what you see in the loxone app. We manipulate the state of that player by using those inputs
Author
Owner

@rudyberends commented on GitHub (Jan 26, 2026):

This is fixed in 67da249

It will be in the next beta

<!-- gh-comment-id:3801252832 --> @rudyberends commented on GitHub (Jan 26, 2026): This is fixed in 67da249 It will be in the next beta
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/lox-audioserver#78
No description provided.