check these first:
- aws endpoint is correct in
.env - cert file paths are correct and files exist
- policy is attached to the certificate
- mosquitto is started with the generated bridge config
- mosquitto logs show bridge connected to aws
- use your pc local ip, not
localhost - check firewall rules for port
1883 - verify username/password match
mosquitto_passwdfile - make sure mosquitto is actually running
- update path in
.env - use full absolute paths
- on windows, forward slashes are easiest:
C:/path/to/file.pem
that can happen if the payload is not json.
- verify topic is
espresense/devices/# - send a test json with
npm run send:sample - if sample json prints fine, watcher is okay
likely tls or cert issue:
- wrong root ca file
- wrong device cert/private key pair
- policy missing action(s)
- system clock is very wrong
check mosquitto logs in verbose mode (-v) and fix the first tls error.
you need to regenerate config:
npm run build:mosquittothen restart mosquitto with that file.