Closed dmunson424 closed 6 years ago
This is a duplicate of #45
I've seen this issue before a handful of times. We don't know the exact cause but it's almost always related to a leased cable modem from your cable company. Upgrading the firmware or replacing the cable modem is the only workaround right now.
Nate,Just wanted to let you know that your diagnosis is right. We changed out the cable company's modem/router, and now everything is working like a champ.Thanks a bunch.Dan
On Monday, December 18, 2017 11:03:42 AM, Nate Clark <notifications@github.com> wrote:
This is a duplicate of #45
I've seen this issue before a handful of times. We don't know the exact cause but it's almost always related to a leased cable modem from your cable company. Upgrading the firmware or replacing the cable modem is the only workaround right now.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
You have a great product and code Nate. As I am attempting to get my first NodeMCU online, the unit connects to Wifi, loads the server, initializes the six sensor pins, loads the application, and then disconnects with a HTTP client error. The printout is shown below. Any advice?
NodeMCU 1.5.4.1 Konnected Security 2.0.5 build 20170825 powered by Lua 5.1.4 on SDK 1.5.4.1(39cb9a32) Heap: 41264 Initializing Konnected Heap: 36776 Version: 2.1.0 Heap: 35024 Connecting to Wifi..
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
load 0x40100000, len 24580, room 16 tail 4 chksum 0xa2 load 0x3ffe8000, len 2268, room 4 tail 8 chksum 0x7d load 0x3ffe88dc, len 136, room 0 tail 8 chksum 0x89 csum 0x89 „âì2‚nì’sƒòN|ì$l$l`Œãr’lŒ$Œþ