Check it works
Quick checks
The client is up. With Docker,
docker psshows(healthy). Without Docker, run this on the client's computer:curl -sk https://localhost:20846/health # {"status":"ok"}It found your TVs. Its log has a
discovery: device addedline for each Chromecast.The internet can reach it. From outside your network, for example a phone off Wi-Fi (details):
curl -s https://home.example.net:20846/healthWith Let's Encrypt this must work without
-k. With your own CA, add--cacert ca.crt.Alexa reaches it. Say "Alexa, pause the Living Room TV" and watch the client's log: a
requestline, then aresponseline, means the whole chain works.
When Alexa says the device isn't responding
First look at the client's log at the moment you spoke.
Nothing in the log at all: the command never reached the client.
| Check | How |
|---|---|
| The endpoint URL | On the settings site: https://, your name, your external port, and /askhomeskill. |
| The port forward | Quick check 3 from outside your network. Your public IP may have changed: is your dynamic DNS updating? |
| The certificate | Not expired, names the host in your endpoint URL, and is the full chain. With your own CA, ca.crt must be pinned on the settings site. |
| Client certificates (mTLS) | With requireClientCert, the log shows client_cert_rejected instead: upload client.crt and client.key on the settings site. |
auth_error in the log: the command arrived but its signature didn't match.
- The shared secret differs between the settings site and
config.json. The settings site shows the last four characters of its secret: compare them with the end ofsharedSecret. If they differ, paste the same secret in both places (or generate a new one and paste it intoconfig.json) and restart the client. - Your entry in
accountshas its ownsharedSecretthat differs: an account's own secret overrides the top-level one.
A request line, then an error or a reject: the client got the command but couldn't carry it out. The line
says why, for example a TV that is off the network, or an app on the TV that doesn't support that command.
Other problems
- No devices after "Alexa, discover devices": the client must see the Chromecasts (quick check 2). With Docker,
it needs
--network hoston a Linux host. The computer must be on the same network (and VLAN) as the TVs. - A TV is missing or has an old name: rename it in the Google Home app if you like, then discover devices again.
- "Alexa, pause the TV" fails but naming a TV works: set a default TV.
- Voice search says it isn't supported: the account has no working Plex settings. The client's startup log names the problem.
- The Alexa app says the skill needs linking again: link it again. The skill never unlinks you on its own.
More detail
Start the client with LOG_LEVEL=debug for every Cast and Plex step. Logs never contain your secret, tokens or
household identifiers.