Recent content by JasonL

Id recommend not forwarding to port 80. That could be blocked by your cable provider. I have optimum and they definitely block it so I use port 8000 which is not

Got my desktop back working and had the ping going and it went without stopping for 12 hours or so so guessing this is now resolved! Thanks for the help! The weird thing is that when I got this originally a few years ago I never had any issues with dropping, and then it started last year which...

Thanks for the info will hopefully remember for next time. What is the LEDE thing at the top? It now says LEDE Reboot SNAPSHOT r5264-94491a1571 Whereas previously it was r4558

Installed the latest snapshot and will check over the next few days. Unfortunately my desktop is having issues so don’t have anything on the same network that I can just continuously ping the heatermeter to see if the connection ever drops. Edit: looking pretty good so far. Has worked...

Thanks, so just take out the sd card and reimage it using https://heatermeter.com/dl/ to create the right image with the WiFi info configured? Edit: actually how do I tell what version of linkmeter I’m on? I see this at the very top when I go into configuration. LEDE | LEDE Reboot SNAPSHOT...

Great thanks!!

I think I may just try to replace the raspberry pi B with a raspberry zero WH. I confirmed the pi is not pingable at all when i am unable to connect to the web interface. I already replaced the WiFi adapter last year and that didn’t solve the issue. None of my other devices seem to have any...

Probably a dumb question, but how do I know which pins on the pi WH do I clip? Was having issues with the WiFi on the pi for my HM 4.2, so thinking about replacing the pi. Seems like the zero WH might be the easiest and cheapest option

Just saw this, not sure what to make of it. Tried connecting and couldn’t around this time but a minute later was able to 19 01:42:20 2019 daemon.err uhttpd[348]: sysctl: error: 'net.nf_conntrack_max' is an unknown key Thu Dec 19 01:42:24 2019 kern.err kernel: [82511.270722] rtlwifi: AP...

Its been a while and figured I’d try and tackle this issue again. I had been just unplugging and replugging it back in whenever it happened to resolve and it’s gotten old. I had it running all of last night and today. It worked fine every time I tried connecting up through this morning...

Around the 1st hashmark for anywhere from 225 to 350 (When using the joetisserie).

thanks. I'm finally back in town and getting to try this out. I went ahead and purchased a new wifi adapter and letting that run, though I guess the smart thing would have been to use the old one and check the logs. Thanks for the help, really appreciate it. Will report back my findings...

What should I read into it if it wouldn’t connect a couple hours ago and when I tried again just now it showed up fine? Previous attempts would show the luci link and eventually get a timeout/no response error. Will the web server auto restart after some time period? The uptime in the Status...

Spoke too soon, will check out the other possibilities when I’m home.

I got a new SD card and loaded on a new image and things have been running smoothly. It’s just running inside but the probes are all plugged in / similar to how it was running when I had a lot of issues last week. Hopefully no more issues but only time will tell. Thanks again!