Open ccristal opened 3 weeks ago
Hey there @velleman, mind taking a look at this issue as it has been labeled with an integration (linkplay
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
linkplay documentation linkplay source (message by IssueLinks)
I have already rolled back to nagyrobi's custom integration because of this issue, but I can restore the configuration with the new integration if it helps reproducing the problem and getting it fixed more quickly.
I've tested this case specifically when adding multiroom, but it appears that there are still some bugs here in gathering the leader of the multiroom. I haven't seen this bug specifically in the same way you mentioned, but I'll fix the other bugs and try to add it the next release and see if it fixes it along the way.
I've tested this case specifically when adding multiroom, but it appears that there are still some bugs here in gathering the leader of the multiroom. I haven't seen this bug specifically in the same way you mentioned, but I'll fix the other bugs and try to add it the next release and see if it fixes it along the way.
Again, happy to do some testing for you if it helps...
If you don't mind, I would appreciate it if you could test since I don't think I have found the issue thus far. You can wait if you want until 2024.11.2 is released, since some multiroom fixes are planned to be fixed there.
The command "ConnectMasterAp:JoinGroupMaster:eth0.0.0.0:wifi0.0.0.0" should list the real ethernet address in there, that's also not happening and should be fixed in 2024.11.2.
Just like in the other issue: The integration is capable of detecting the correct protocol (either 80 and 443) and will even attempt to accept the LinkPlay certificate. On the latest home assistant version (2024.11.0+ or 2024.11.2), you can enable debug logging to get more information.
Hi! I have now installed 2024.11.2, and the issue still exists. I have added the relevant log messages (or at least what I think is relevant) to the main issue description.
177 is my main device (Wiim Pro), 47 and 173 are the satellites (Audio Pro Addon C3) (we don't use "master" and "slave" anymore here... ;-) ).
So, the action completes but nothing is actually linked.
Hope this helps. Thanks for looking into this...
The problem
I have an Audio Pro C3. Its API can be invoked via http (not https). The Linkplay integration is able to discover and configure it, but it can't join it to a group with a master device with an API accessible via https (like a Wiim Pro). This is the error message I get when I try to add my Audio Pro C3 as a satellite speaker to a Wiim Pro master:
The device on 192.168.1.47 is the Audio Pro device, so the protocol should be http.
What version of Home Assistant Core has the issue?
core-2024.11.0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Linkplay
Link to integration documentation on our website
https://www.home-assistant.io/integrations/linkplay/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response