-
Notifications
You must be signed in to change notification settings - Fork 12
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
setup MQTT server #5
Comments
Unfortunately, it depends heavily on the exact details of how your home network is set up. I used linux and hostapd, but I never went down this path fully. I ended up discovering how to modify the flash image so that it'd use my wifi network, which made doing so pointless. I'd recommend following the instructions at https://gist.github.com/flaviut/93a1212c7b165c7674693a45ad52c512 to run ESPHome. |
Great work, Congratulations ! |
Source code for the framework they use can be found here: https://github.com/aws/aws-iot-device-sdk-embedded-C. OTA would be really nice, but Amazon generally knows what they're doing security-wise (tuya… maybe not so much. but even they caught on eventually).
By the way, if change the firmware to espHome, is it possible to put the original firmware back ?
Absolutely. That's why the first step in my guide is to back up the existing firmware. You can just keep that file around, and just flash it on if you want to switch back.
Also if you are interested, i can write about the other method to putting the esp32 in download mode, without using the VCC pin at all, it involves grounding the enable and io1 like you mention in your blog.
Yup, but I'd rather keep it simple. I don't want to confuse anyone by giving more choices than they need.
Very cool idea bringing the serial wires out through there. Definitely seems nice for testing.
…On Mon, Jan 17, 2022 at 10:20 PM Joe ***@***.***> wrote:
Great work, Congratulations !
I'll do the espHome route!, and keep looking the non soldering way too, if
lucky find the ota magic byte or something else.
By the way, if change the firmware to espHome, is it possible to put the
original firmware back ?
Also if you are interested, i can write about the other method to putting
the esp32 in download mode, without using the VCC pin at all, it involves
grounding the enable and io1 like you mention in your blog.
[image: emporiavueserial]
<https://user-images.githubusercontent.com/67212264/149864081-adbd8376-a803-4a49-ada7-6a2900ca5b52.jpg>
—
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHY2HPXBG3E2KQP7YZ5KKDUWTL6DANCNFSM5MDVMUSQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
Yes. The original revision of the guide suggested that you hold the pins in the hole without soldering a header. In that situation, I think it's a little easier to do things with the VCC pin. However, I discovered that 90%+ of boards these days are coming with the holes filled with solder. So I removed that part of the guide, since it's no longer useful. But I didn't change to EN/IO0 because it doesn't really matter. |
aww, AWS seems like a long shot... |
I know this has a long time, but worth the shot: Did you have any issue with connecting the 2 grounds together? The USB/FTDI and the emporia (mains supplied)? |
Hello!
Could you please explain how did you setup the local network and bridge MQTT server with 192.168.1.101 address for getting the prod/minions/emporia/ct/v1/AAAABBBBCCCCDDDDEEEEFF/debug/v2 topic ?
Thank you!
The text was updated successfully, but these errors were encountered: