Skip to content

Unjoin stops working after 'wrong' join usage #3

@Patrick1610

Description

@Patrick1610

So I have 2 receivers. This means I have two scenario's:

  1. I am playing on the living room and want to add the lounge
  2. I am playing on the lounge and want to add the living room

This is fine and seems to work correctly. I get issues when the following occurs.

  1. I am playing on the living room
  2. I run an automation 'add lounge to living room'
  3. I (accidentally) run an automation 'add living room to lounge'
  4. I try to unjoin, this failes.
  5. I manually unjoin (using the app)
  6. I join using one of either automations
  7. I still cannot unjoin using the automation
  8. After rebooting the whole lot I managed to get it to work, but trying the same it failed once more.

I also have the following:

  • When I add the lounge to the living room, I cannot unjoin the living room and keep the lounge active, or vice versa.
    Is it possible to add that functionality, or the option to 'change' master?
    That is the reason I tried the second join command, but as you can see without success.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions