homie-esp8266: Can't configure homie
Before submitting your issue, make sure:
- You’re using a stable release, not the Git development version which is, by definition, unstable
- You’ve read the documentation for your release, which is in the
docs/
folder of the.zip
of the release you’re using, especially the Getting started and Troubleshooting pages, which contain respectively the minimum required version of the dependencies, and some answsers to the most common problems - You’re using the examples bundled in your release, which are in the
examples/
folder of the.zip
of the release you’re using. Examples in the latest git revision might not be backward-compatible with your release
Thanks!
I am trying to get my first Homie board set up.
I have tried a number of sketches using both master and delevop branches, cloned and installed from zip.
Homie installs on both NodeMCU and on Wemos D1 mini and there my luck runs out…
I cannot get a heartbeat using either of the configuration web pages. I can see ‘heartbeat request received’ multiple times on the serial console but the web page never gets beyond waiting for device.
I can connect to device and get device info using the app but once I get to the settings tab I get stuck. The ‘next’ button is never enabled so I can’t progress to Launch.
If I try using curl to PUT a config I get an ‘invalid or too big JSON’ error.
I’m obviously missing something but I can’t figure out what!
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 40 (12 by maintainers)
Sometimes I delete rows from my default config and there’s always a dangling comma that bites me …
https://jsonlint.com/ and similar are nice tools to test the config
Remove the , at the end of the first line containing the password.
@amayii0, i’m working on a standalone app: discover homie networks, connect, and upload a saved configuration. Than you can also see the mqtt messages from the device. it’s still beta though: https://play.google.com/store/apps/details?id=com.plugdio.homiedash)
You should use DNS if possible to avoid this issue. You can easily have a DNS entry that points to an IP within your own LAN mqtt.mydomain.com -> 192.168.1.2
Once configured, you can update the config using MQTT.
I yesterday ran into a catch22 where the MQTT broker changed IP and the device couldn’t be reconfigured since that is done by MQTT (and the JSON API is disabled once in normal mode).
The device was stuck in the “connecting to broker” loop.
Anyway, it is mentioned in the documentation that the JSON API is available in config mode. But I also read over it and assumed it was available all the time. (but since it’s not protected by any means, it would be a security issue)