Please setup one speaker on ethernet and see if integration discovery and mp3 play works.
I forgot to mention, if you revert to 2.2.8 does everything work?
OK,
I will try this tomorrow.
But please keep in mind, rules like this are still working fine:
But rules like this (basically all based on MP3 files) stopped after upgrading to 2.2.9.137
Why suddenly it could be a network related problem?
If discovery doesn't work then something isn't right.
I'm just going the process of elimination
The Discovery actually works (I guess).
Both my speakers are discovered and selected:
But when I am clicking on the Done button nothing happens.
Speakers are not added to the Device list.
The Discovery did not work when I initially added speakers about
5-6 month ago. So I added them manually.
And they are still partially working (please see my messages above).
I can try cable connection tomorrow but I am sure this is not a problem.
OK,
I figured out what I was doing wrong (i did not remove existing device).
Now I added successfully just one speaker via Sonos Integration built-in app.
Speaker is added but it still does not play URI:
http://192.168.20.91/local/Beethovens_5th_Chime.mp3
But Speak Button works just fine - I can hear "Speaker Test" play back:
If you revert to 2.2.8 does everything work as expected?
If revert back to 2.2.8 I am sure it will work but I will not be able to test 2.2.9
I have C-5 idling but still online.
I will try to update C-5 to the latest 2.2.9 and see what happens.
OK,
- Updated my idle C-5 to the 2.2.9.137
- Uploaded one MP3 file
- Attempted to play this file from the Device page with Play Track button
File did not play. - Attempted to use Speak button
SUCCESSFUL
Here is a related log:
Ok so revert that spare hub to 2.2.8 and verify everything works.
My preference will be to revert back to 2.2.8 my main C-7
and play with 2.2.9 on spare C-5.
Will it be OK for the debugging?
The reason is: my wife wants all announcements back.
Sure. Just trying to verify that its an issue with 2.2.9. Doesn't matter which hub
I'm guessing someone would have mentioned this already it it did matter (and it doesn't seem to matter for Bruce, so probably not), but does using port 8080 instead of the default (80) in your Play Track URL happen to do anything different? It can't hurt, in any case--alternate port in Hubitat for the same thing.
Reverted C-7 back to 2.2.8.156
Speakers are back to normal and working fine.
So, the problem is clearly pointed to 2.2.9137 HE SW, no doubts.
Attempt to update spare C-5 to the latest 2.2.9.138 resulted
in never ending "reboot in progress" and blue LED on a hub.
Recycling power brought C-5 hub back to live.
Tested Speaker and it did not work. But this was expected.
Ok thanks, we will get to the bottom of this.
1 Like
Thank you very much.
I can test fixes/updates with my spare C-5 hub.
How about this old problem described here:
I understand, the priority for this problem is very low.
But I am hopping, it will be fixed sometime.
I really want to use native TTS vs. MP3 files.
OK, we're unable to replicate the local mp3 file play issue so far, but I found a solution for the Russian language issue (at lease it appears to work for me)
Create your text messages as such:
<lang xml:lang="ru-RU">Мой текст здесь</lang>
2 Likes
Thank you,
I will try this solution.
2 Likes
OK,
Created very simple rule for testing:
Rule worked as expected.
Does this mean I can dynamically (right from RM) select language to speak?
If "yes" what is abbreviation for English?
"en-EN" ?
And thank you very much for this work around.
1 Like
Probably the traditional "language-region" format, which for United States English would be en-US. Guessing the supported list for Hubitat's serivce, reported to use Amazon Polly, would be this:
1 Like
Very BIG Thank you for the info!
