Hi
I think saga is probably slightly strongly worded...
Hopefully you ran the terminal command - it the 2 minutes before the voice announcement. Good to see that the message regarding it is there.
16.4 on Homepods has some major issues, and is likely leading to this
I've upgraded and had to reset 2 and still can't play anything (using the Home app)
I've reset one with no change.
Following 16.4 update - HomePods spend ages doing something. Within the Home app - would say configuring...
During this time wouldn't be able to access.
After an hour and 2 resets and reconnection - seems to be now accessible. Who knows what they have been doing....
The error you are seeing is library based. Without rebasing and editing library not to much I can do about it currently.
& rapid quick fire requests to the same device will cause a async lock issue.
- Code: Select all
Running through the Debug log: (which isn't the same timing as attached - seems only one failure)
First: CM-Homepod Powerstate update Old PowerState.On and new PowerState.Off
(almost looks like Homepod restarting, or potentially sleeping?? If 16.4 has introduced some new sleep behaviour that will be issue)
11:52:17 - Connection to appleTV - CM-Homepod lost. Nothing plugin based, something either device restarting or network.
Then:
11:52:28 - send Remote Command which fails.
11:52:31 BlockstateError - is because the device is disconnected when attempt command.
20 seconda later (thats the async loop which can shorten)
Plugin sees disconnection and restart this appleTV/Homepod handler
11:52:32
11:52:33 Scans IP with unicast - finds and reconnects here
I'll have a look and see. Can drop the loop timing so that disconnects are recognised sooner and reconnected (its async loop so won't matter)
If sleep handling has changed, may even need to make before command..
Clearly relates to 16.4 UpgradeSeems to have updated the Device_Info message, causing a Power off/Power On to be toggled.
Winding back to 16.3.2 - fixes - no idea how to do that - but is possible.
Sending message twice works - because of toggle above oddly.
Library has reported this (some beta users apparently), and I have re-reported.