App seems to stop responding after running for several hours

[patrickeasters]

With the latest firmware, the NodeMCU app seems to stop responding or behaving correctly after 6-12 hours or so. I haven't gotten to the bottom of this yet or been able to reproduce it consistently, but I have this hooked up to a computer now and am watching console logs to see if anything comes up.

[wavesailor]

Why not install MicroPython on you ESP8266 board (http://micropython.org/download#esp32) seeing as you using Home Assistant which is written in Python?

[patrickeasters]

@wavesailor Per my comment on Medium, there wasn't a real driving force to use any particular firmware/framework since MQTT is pretty platform-agnostic. I may try it out for a future project.

[patrickeasters]

I'm trying out a new firmware build from the dev branch of nodemcu-firmware to see if that helps any, since this was only a problem since upgrading to 2.1.

[lbrasi]

I flashed the latest master build and also facing issues after approx 6 hours, any fix for this?

[JoooostB]

I'm trying out a new firmware build from the dev branch of nodemcu-firmware to see if that helps any, since this was only a problem since upgrading to 2.1.

Are you able to follow up on this matter? I'm experiencing the same issue with the most recent version of nodemcu

[patrickeasters]

I'm trying out a new firmware build from the dev branch of nodemcu-firmware to see if that helps any, since this was only a problem since upgrading to 2.1.

Are you able to follow up on this matter? I'm experiencing the same issue with the most recent version of nodemcu

I flashed a build from the dev branch as of April 1 and it's been solid since then. Are you using a build from dev or master right now? And what version number?

[JoooostB]

I've used the most recent stable version as of writing the previous comment. However, as a challenge for myself I rewrote it in MicroPython which seems to be stable :)

Op zo 11 nov. 2018 21:01 schreef Patrick Easters <[email protected]mailto:[email protected]:

I'm trying out a new firmware build from the dev branch of nodemcu-firmware to see if that helps any, since this was only a problem since upgrading to 2.1.

Are you able to follow up on this matter? I'm experiencing the same issue with the most recent version of nodemcu

I flashed a build from the dev branch as of April 1 and it's been solid since then. Are you using a build from dev or master right now? And what version number?

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/patrickeasters/nodemcu-sensor-mqtt/issues/2#issuecomment-437699917, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIPa1EVU2Yyjp6D4C4ebmnOsneIoKi6Fks5uuIIdgaJpZM4S8GjF.