With mine, it seems to mess up when it gets several commands in quick succession.
I've Kinda noticed that too. But did some testing and couldn't get it to happen. So thinking it might still be related to waking up.
It seems that when the unit doesn't play a message is when I get that 'Internal Error Occurred'. So what does that mean? Is it referring to the device, the driver, the app????? Could help the troubleshooting if I knew where that was coming from.. @gopher.ny
Here is a screen shot of the events on one of the pods. The speak command at 1:46 worked fine. The one at 4:29 didn't and the log shows the internal error at that time.
So yesterday evening I did a update on my router. Then of course all the devices had to reconnect, which took awhile. The bedtime announcement didn't take place, but I attributed that to not totally being connected yet.
This morning again, no announcement. Tried several units and nothing. Went into the Airplay Integration app, devices all showed up and were checked. So I did the re-install of the dependencies. STill nothing. Then I realized I had to restart the integration. Still nothing. Then I noticed that all of my pods had zero volume. Apparently when you re-install dependices or restart the integration it sets the volume to zero. PITA. So now they work again, at least for now.
I never had any issues with this until the update that required dependices be installed. Don't remember which one that was. I think it also related to the ability to play music thru the system.
I don't know what is going on, but something is broke in the HE integration.
Checking that (and the rest of it)... I don't believe there's anything that explicitly sets the volume, just need to get to the bottom of it.
Thank you for looking into this. Anything I can do to help testing let me know.
1 Like
When I have a few spare minutes I play around with this to see if I learn anything, sadly no.
In the integration one of my devices, Apple TV 4K, shows up in a list down lower in the settings that says
" These devices must be paired to the hub in order for the AirPlay TTS to function."
What exactly does that mean? I tried unselecting it and it really made no difference on any of the others.
I have a total of 7 homepod Minis plus the unit mentioned above. Could that be too many. I tried unselecting all but one and not sure that made any difference either.
Just some things I am wondering about.
Some interesting test results.
I have a simple app set up where I toggle a virtual switch and it sends a message to the pod(s).
In Airplay Integration I have only one pod selected. When I trigger the switch there is about a 15 second delay before the pod speaks. The 15 seconds is pretty consistent. The very first time it was a truncated message, but after that it was fine. Gonna see what happens after it sits for awhile.
I also have a google mini. If I only select that to send the message to it is pretty much instantaneous. And consistent. If I select both the Homepod and the Google they are both delayed about 15 seconds. It appears the message is getting sent to the Homepod and then somewhere in the app (not my app, no delay there) logic it waits to send it to the Google.
Don't know if that is of any help or not.
I also wonder, am I the only one having this issue? If so then it must be something in my setup that I have no idea what.
Yesterday morning I dug out my Google Mini's and set them up. Can't rely on the Homepod integration. Then I deleted the Airplay App along with all the devices. 12 hours later I still get 'Initialize Called' log entry from that app that is no longer installed.
2.4.2.143 build may solve this issue. It's just gone public.
4 Likes
Installed .143. Re-installed Airplay Integration. Selected only one of my pods. Still doesn't work right. Sometimes no speak. Sometimes only partial speak. When it does speak it's about 12-15 sec delay. Still get 'internal error occured' in logs.
Any updates on if or when these issues will get resolved?
1 Like
1 Like
Already updated. Still not working.
Darn. Back to the drawing board.
1 Like
Something I just tried that looks promising. In my Home app I changed the settings from ‘Anyone On The Same Network’ to ‘Everyone’. Preliminary testing is showing much better results. I will keep testing and see what happens.
3 Likes
I have "Anyone", but there's only me. Maybe it can get more complex with more users (?).
Changing it to Anyone has helped, but it's still not 100%. Still occasionally get a truncated speech. This morning I see a different error in the logs. "Timeout While Trying To Connect". Can't say exactly what was going on when the error occurred. This is on the one unit I have re-enabled for my announcements.
EDIT: Something that still puzzles me. If it appears I am the only one having this issue, or no one else is talking, then it must be something in my setup. Which I can accept but how do I figure out what it is???
You meant "Everyone", right?
