Skip to content
This repository has been archived by the owner on May 7, 2020. It is now read-only.

Sonos notification broken in snapshot 988 #3877

Closed
lolodomo opened this issue Jul 24, 2017 · 12 comments
Closed

Sonos notification broken in snapshot 988 #3877

lolodomo opened this issue Jul 24, 2017 · 12 comments

Comments

@lolodomo
Copy link
Contributor

lolodomo commented Jul 24, 2017

Sonos TTS seems to be broken in snapshot 988.
There was this recent PR #3808. I see something strange in this PR, the old value was in milliseconds (20000) while the new default thing setting is in seconds (40), so I think 40 ms is used by default !
@ivivanov-bg : can you check please ?

@lolodomo
Copy link
Contributor Author

lolodomo commented Jul 24, 2017

Later I will set the thing setting to 20000 as a workaround to see if it solves the problem.
But the real fix would be to apply a conversion from second to millisecond.

@lolodomo
Copy link
Contributor Author

And I see no valid reason to set this new thing setting as required.

@maggu2810
Copy link
Contributor

But the real fix would be to apply a conversion from second to mullisecond.

I had a short look at #3808 and it seems you are right.

@lolodomo
Copy link
Contributor Author

I submitted PR #3883 that fixes the bug introduced by PR #3808. I restored a default timeout of 20 seconds which is already very long. If someone needs a longer timeout, it will use the new setting.

Unfortunately, TTS with Sonos is still not working after my fix, probably due to other changes relative to audio. @cweitkamp, maybe your PR #3837 could be one of the source of the problem ? Did you test TTS with Sonos after your change ?

I am back now to snapshot 951 with working audio and TTS.

@lolodomo
Copy link
Contributor Author

Another candidate could be PR #3764.

@cweitkamp
Copy link
Contributor

Sry, I did not test TTS with Sonos. Any log files?

#3837 was merged after you created this issue. I suggest that PR to be not the reason.

#3764 seems more likely. I am going to review my changes.

@lolodomo
Copy link
Contributor Author

My fix (PR #3883) has been applied to the last sources that includes your PR #3837.
To test in my production environment (snapshot 988), I installed the fixed Sonos binding + the new version of the core.audio bundle.

@lolodomo
Copy link
Contributor Author

lolodomo commented Jul 25, 2017

Cool, a new ESH build was done this morning with all the recent ESH fixes so the next OH snapshot (990l) should include them tomorrow and I will test again TTS with Sonos.

@lolodomo
Copy link
Contributor Author

lolodomo commented Jul 25, 2017

@kaikreuzer: that is not clear for me, does the OH snapshot 989 already include the ESH build from today ?

@kaikreuzer
Copy link
Contributor

This morning? It depends on where on the world you are - I did the build just a few minutes ago ;-)
openHAB distro 990 will include it.

Looking forward to get positive feedback from your testing!

@lolodomo
Copy link
Contributor Author

lolodomo commented Jul 25, 2017

Bingo, the problem is solved in OH distribution 990. So the problem was only the bug with the timeout handling I fixed yesterday.
@cweitkamp : I hope you have not lost too much time to search.

@cweitkamp
Copy link
Contributor

@lolodomo Glad to hear that it could be solved so fast. I haven't lost time. I only won a new bullet point on my TODO list. Since there is no unit test for VoiceConsoleCommandExtension I put it onto mine. Maybe we should put a unit test for the Sonos binding on any TODO list as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants