Chromecast Audio device driver beta has issues

🛎️ Get Help Devices
1

I've been chasing this for a year or 2. I thought it was a WebCore issue but the last 2 days of intense Wait commands, Logs and direct device commands seems to have narrowed the issue down to the device driver.

  1. If I send an integer to change the volume from the current (45) to volume (70) the number received is 50% correct.

app:18842024-12-19 15:14:26.187info ║ 70
app:18842024-12-19 15:14:25.582info ║ Called by Doorbell
app:18842024-12-19 15:13:26.863info ║ 72
app:18842024-12-19 15:13:26.522info ║ Called by Doorbell
app:18842024-12-19 15:12:02.654info ║ 70
app:18842024-12-19 15:12:02.218info ║ Called by Doorbell
app:18842024-12-19 15:09:36.535info ║ 72
app:18842024-12-19 15:09:35.058info ║ Old volume ,45

  1. The SetLevel command stops working for some reason. Both sent from WC and directly from the Devices tab. I don't know what disables it but I found the only way to bring it back is to command a speak(). This brings Set Level back to life.

I now send a speak() with no chars to wake up my speaker group device and then successfully change the volume and send my message.

Hope this helps in proving me I'm crazy or fixing this issue. I'm good either way. :slight_smile:

image
image1253×915 42.7 KB

2

Set a rule to run initialize every 5 mins. It will prevent the chromecast device from going to sleep (at least 95% of the time)

3

I did try that earlier but it didn't seem to do anything.
WebCore had a 'bug' during that test where you couldn't retrieve the volume level in the same With block as other commands.
Once I figured out the problem I moved the Set Variable command to it's own With and I stopped getting 0 all the time.
I was assuming the Init was going to solve that issue but it was a different problem.
I have solved my issue but I can try the init again as it's a bit cleaner?

1 Like