-
Notifications
You must be signed in to change notification settings - Fork 308
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
Reboot loop with current version #373
Comments
I am getting something similar, but the |
I had the same, I downgraded Homie to commit d9a2760 and it's working fine now. I suspect this was the upgrade to asyncmqtt but haven't bothered to confirm yet. |
I'm struggling to get any combination to work now :( . Always the same reboot loop after attempting to connect to WiFi. Will try a stock example to see if that works... And it does. However, there is a slightly suspicious chain of events when connecting to WiFi, there seems to be some extra disconnected messages after connecting.
|
If using Arduino IDE, try selecting the "Generic ESP8266" board... I have
had reboot loop issues with Sonoff's and standalone ESP-12 modules when I
selected NodeMCU "board". Not certain how things work with PlatformIO
…On Thu, Jul 27, 2017 at 5:30 AM, Philip Barclay ***@***.***> wrote:
I'm struggling to get any combination to work now :( . Always the same
reboot loop after attempting to connect to WiFi.
Will try a stock example to see if that works.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#373 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEyM8Y3Z9VI_l-yFL2qc1xcRMGYiZC22ks5sSFjRgaJpZM4Ogg99>
.
|
I'm currently on vacation but I'm pretty sure I had to use generic boards for D1 mini clones. |
@claybar: I think that's a separate concern. That's the same kind of behavior I seen when accessing my Wifi when the signal isn't great (your log shows 42-46%). |
Some more information: I decoded the stack trace with https://github.com/littleyoda/EspStackTraceDecoder. here's the result:
Unfortunately no line numbers, but maybe it helps in finding out, what is going wrong |
Very strange. I uninstalled/reinstalled Homie in Platformio (Homie version cd2fa9f), recompiled, uploaded again and now everything is stable. |
Same exception for me. Even reinstalling Homie (bb7fbc9) does not help. Decoded stack trace:
|
Same thing here.
Mosquitto/DHCP server log:
Stack Trace:
|
Problem found: Homie crashes on startup when not a single node is defined (as in the "bare minimum" sketch). Pull request #379 fixes the problem. |
Merged! Guys, can you test with @jbliesener's fix? |
Ouch, nice find. I'll test this evening when I'm back home. |
Sorry for the late feedback. @jbliesener fixed it for me. My basic ota script has no nodes. If nobody objects, we can close this issue. |
using platformio and homie minimum example, the device goes through an endless reboot loop after uploading. The crash always happens directly after the "Sending initial information..." message is shown.
The initial information ($homie,$mac, ... $implementation/config) is sent, my mosquitto receives it and a separate client (mqttfx) that has subscribed to homie/a020a6117237/# receives it.
The program:
Platformio libraries in global storage, no lib_deps in plaformio.ini:
The first two repititions of the serial output:
💡 Firmware homie-minimal (1.0.0)
🔌 Booting into normal mode 🔌
{} Stored configuration
• Hardware device ID: a020a6117237
• Device ID: a020a6117237
• Name: Developer
• Wi-Fi:
◦ SSID: onklan
◦ Password not shown
• MQTT:
◦ Host: 192.168.0.10
◦ Port: 1883
◦ Base topic: homie/
◦ Auth? no
• OTA:
◦ Enabled? no
↕ Attempting to connect to Wi-Fi...
✔ Wi-Fi connected, IP: 192.168.0.207
Triggering WIFI_CONNECTED event...
↕ Attempting to connect to MQTT...
Sending initial information...
Exception (28):
epc1=0x4020761c epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000
ctx: cont
sp: 3fff04d0 end: 3fff0760 offset: 01a0
ets Jan 8 2013,rst cause:2, boot mode:(3,7)
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v3ffe8550
~ld
▒💡 Firmware homie-minimal (1.0.0)
🔌 Booting into normal mode 🔌
{} Stored configuration
• Hardware device ID: a020a6117237
• Device ID: a020a6117237
• Name: Developer
• Wi-Fi:
◦ SSID: onklan
◦ Password not shown
• MQTT:
◦ Host: 192.168.0.10
◦ Port: 1883
◦ Base topic: homie/
◦ Auth? no
• OTA:
◦ Enabled? no
↕ Attempting to connect to Wi-Fi...
✔ Wi-Fi connected, IP: 192.168.0.207
Triggering WIFI_CONNECTED event...
↕ Attempting to connect to MQTT...
Sending initial information...
Exception (28):
epc1=0x4020761c epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000
ctx: cont
sp: 3fff04d0 end: 3fff0760 offset: 01a0
ets Jan 8 2013,rst cause:2, boot mode:(3,7)
load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v3ffe8550
~ld
The text was updated successfully, but these errors were encountered: