-
Notifications
You must be signed in to change notification settings - Fork 792
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
Watchdog reset when using nodemcuv2-pilight and receiving rf codes. #1971
Comments
Hi all, I can confirm the issue. I get exactly the same crash report for the following config:
There are no crashes with the same config and OpenMQTTGateway 1.6.0. |
Do you reproduce with the development branch ? |
Try adding It'll dump a lot more info out to the console which might help narrow down the issue. |
Thank you for your suggestions. I just tested again, but with the following config as I don't have my nodemcuv2 board with me. I used v1.7.0 and v175, both work fine. I'll test again when I'm back.
|
I have tested now again with the nodemcuv2 board. I have to add to the last test that I was not aware anymore that the problem only occurs when a signal is received - so that test was completely useless. I've now put v1.7.0 with the config:
The output is:
However, compilation of the development branch fails with:
I have not yet figured out how to change that version. Log also says some old version is used (in case this is the version related to the error) although platformio.ini lists a much newer version.
|
ESP8266 crashes hard when using pilight build, and receiver is getting input (eg, by pressing kaku/nexa RF remote)
Serial console output:
Issue is present with OpenMQTTGateway 1.7.0, and also with current development version.
Environment used:
The text was updated successfully, but these errors were encountered: