Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing step in directions? #2

Open
ahollyer opened this issue Mar 11, 2018 · 0 comments
Open

Missing step in directions? #2

ahollyer opened this issue Mar 11, 2018 · 0 comments

Comments

@ahollyer
Copy link

After following the instructions in the readme, the AWS IoT business rule is misconfigured. Resolved it with the following steps:

  1. Log into your AWS console at https://aws.amazon.com
  2. Go to the AWS IoT service
  3. Click "Act" in the lefthand menu. Rules dashboard comes up
  4. Click the card for the rule that matches your device
  5. Next to the "Rule Query Statement" heading, click edit
  6. Look at the topic filter. It says /button_pressed. This is incorrect. Change it to the actual topic name your device is publishing to: YOUR_DEVICE_NAME/button_pressed

If you don't know your device name, you can connect your esp32, run the terminal command 'mos console' and, if you've set up correctly, you can press the button and see the full topic name, e.g.

[Mar 10 13:48:58.508] Published: yes topic: esp32_12345/button_pressed message: {"free_ram":150572,"total_ram":229788}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant