You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I use sayit in connection with the chromecast adapter since many years. I use it every morning for an announcement of weather + appointments. I use Amazon AWS as cloud-voice provider.
Sometime within this years, this stopped working. I restarted the adapter incl. chromecast and then it worked again.
Unfortunately this happens now every couple of days which is annoying.
I tried many things but nothing was successful. Also setting "Type" to "Google Home" did not fix the issue.
The biggest problem is, that no debugging is possible as there is no warning/error in the log, even in the "silly" mode.
To Reproduce
Not reproduceable as it is a sproradic error.
When the problem is present, there is nothing in the logs but the "test" button in the adapter simply ends in a waiting loop.
Expected behavior
On one hand, the adapter should work permanently without restart, on the other hand I would expect any level of error / warning when there is a connection issue.
Screenshots & Logfiles
N/A
Versions:
Adapter version: 3.0.5
Chromecast adapter version: 3.0.3
JS-Controller version: 5.0.16
Node version: 18.17.1
Operating system: Debian, running in a VM on a Proxmox server
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Describe the bug
I use sayit in connection with the chromecast adapter since many years. I use it every morning for an announcement of weather + appointments. I use Amazon AWS as cloud-voice provider.
Sometime within this years, this stopped working. I restarted the adapter incl. chromecast and then it worked again.
Unfortunately this happens now every couple of days which is annoying.
I tried many things but nothing was successful. Also setting "Type" to "Google Home" did not fix the issue.
The biggest problem is, that no debugging is possible as there is no warning/error in the log, even in the "silly" mode.
To Reproduce
Not reproduceable as it is a sproradic error.
When the problem is present, there is nothing in the logs but the "test" button in the adapter simply ends in a waiting loop.
Expected behavior
On one hand, the adapter should work permanently without restart, on the other hand I would expect any level of error / warning when there is a connection issue.
Screenshots & Logfiles
N/A
Versions:
Additional context
N/A
The text was updated successfully, but these errors were encountered: