Closed inexxu closed 1 year ago
The latest release v2022.10 should fix this. Please give it a try
@giachello thank you for all your effort you put in. Just installed it. It work first. It was updating when changing from Radio to Deezer for example but when I skipped tracks on Deezer it did not update and went to a freeze completly (even when I was switching back to Radio)
@giachello thank you for all your effort you put in. Just installed it. It work first. It was updating when changing from Radio to Deezer for example but when I skipped tracks on Deezer it did not update and went to a freeze completly (even when I was switching back to Radio)
just did a little more testing and it seems to get stuck on deezer all the the time / not following back when switching back to a radio source for example (I have tested with Beosound Essence MK2 and Beoplay M3)
I would be great if you could turn on debugging and send me the logs
In configuration.yaml ... add these lines:
logger:
default: warning
logs:
custom_components.beoplay: debug
Will do in the morning! Where do I find the log files to send them to you?24.10.2022 kl. 19:53 skrev Giovanni Iachello @.***>: I would be great if you could turn on debugging and send me the logs
In configuration.yaml ... add these lines:
logger:
default: warning
logs:
custom_components.beoplay: debug
On Mon, Oct 24, 2022 at 1:34 AM Michael @.***> wrote:
@giachello https://github.com/giachello thank you for all your effort you put in. Just installed it. It work first. It was updating when changing from Radio to Deezer for example but when I skipped tracks on Deezer it did not update and went to a freeze completly (even when I was switching back to Radio)
just did a little more testing and it seems to get stuck on deezer all the the time / not following back when switching back to a radio source for example (I have tested with Beosound Essence MK2 and Beoplay M3)
— Reply to this email directly, view it on GitHub https://github.com/giachello/beoplay/issues/18#issuecomment-1288639006, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOOHKDJMIRXLQJCA6DWPBQ3WEZCXPANCNFSM5SCL643Q . You are receiving this because you were mentioned.Message ID: @.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
homeassistant.log from "File Editor" on the left hand side navigation bar.
[image: image.png]
[Uploading home-assistant.log…]()
@giachello let me know if you need anything else
@giachello can you access the file now. I hope
So this should be fixed now. Please check out v2023.1.1
Works perfectly!! Thanks so much for your efforts!03.01.2023 kl. 08:10 skrev Giovanni Iachello @.***>: So this should be fixed now. Please check out v2023.1.1
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Since the update to 2022.3 the integration seems not to update the status of the devices. Everytime the device is playing from a source the state is ‚unknown‘. Actually there isn‘t any possibility to read out the source of the device. Are there any solutions for that problem?