Search results

Just to tie some partial ribbons on this thread, I am at our lake home and find that the Cisco router does not have a guest mode. Worse, for the Cisco routers that do have that mode: "The Guest Network Name will always follow the main network’s SSID followed by a “-guest” suffix. If you want...

Yup. Conservation of difficulty still applies. :-) Agreed, lower case. Actually had I thought of that I might have tried it. I don't have/don't need guest networks but the home WAP has the capability. Not sure about the lake, but probably it has the capability too. Just giving the lake...

We could. What you suggest is do-able. It's one of those common things where you can move the difficulty around but you can't really eliminate it. At home I would have to reconfigure at least a half-dozen devices to a new SSID. At the lake, fewer, but well above zero. But to have the HM tail wag...

You cook inside your house next to a RJ45/Cat5 connection point? I don't. My use is to have the HM connected to my home network so I can check it from my desktop or, rarely, from a tablet. No need to access it from the internet. Using its WAP capability would be a pain because the desktop and...

OK, let, me make sure I understand; *The config.txt on the microSD is a don't care. *I make two USB sticks, one with the "city" parameters and one with the "lake" parameters. In both cases the parameter lines are not commented out. *The software boots and copies the config.txt to the microSD...

Thanks very much. The USB config.txt is a good solution, much less hassle than pulling the internal microSD. Should I remove the config.txt from the internal microSD to force the software to check the USB or is the USB checked first/default? Probably there are very few of us who cook with two...

We have a lake home and a city home, each with wifi but with separate SSIDs of course. After a lot of experimentation last month I figured out how to edit the config.txt file that was working in the city to work a the lake. I will now be making a second microSD with a config.txt file to suit...

OK. Problem fixed. RP board wifi had failed, as I speculated/suspected/post 6 and post 10. New board from Amazon solved the problem. The blank "wireless overview" screen was probably diagnostic but since I am not familiar with the box at that level I didn't realize that. Gary V's help was...

And ... <drum roll > ... what is an ATMega?

Oh, one more thing: On boot, unless the Cat5 cable is connected, the x.x.200.1 address never displayed (no address is displayed) and the HM does not advertise a network SSID.

Thanks very much. Exactly the kind of thing I was looking for. Comments below: That's the IP the DHCP server gave it via the Cat5 connection. Today it got 192.168.1.106 The x.x.200.x address did display briefly before it displayed the DHCP-derived address. I was actually a little surprised to...

Well I guess we'll see. Maybe papering over the problem with a new software copy will do it. I'll try I guess. Re Rover I never had any product on that one, but on lots of others including Mars Observer, Cassini, and many Geo and Leo birds. You do not paper over problems when you're in that...

I'm glad you are amused. The implication of your post is that you have some unrevealed technical expertise. All you have offered so far is first level tech support type stuff. But lets see ... The failure symptoms are consistent with a failed WiFi radio. This is a Raspberry Pi 3 B or B+, I...

Thanks, but I'm hoping someone with a little more technical expertise will weigh in here. I don't like sledghammer solutions, especially when the problem has arisen after the current software has been running successfully. Something has changed here but it was not the software. I may try the...

I did misread, but DNS has no idea what to do with http://heatermeter.local/ and, as is always the case even when the HM is active on my local network, http://heatermeter.com/devices/ gives me nothing. RasPi is self contained, no dongles. News: Medium breakthrough though: I just plugged it...

As I said in the OP that has never worked for me. As I said in the OP, I do not see the HM on the list of devices having DHCP addresses and I do not see it advertising its network.

When my HM boots it takes an excruciatingly long time to display the IP address that it has gotten via DHCP. So long that I sometimes give up waiting or, worse, look away at the critical moment. When I do get the address, the web interface runs like a dream. http://heatermeter.com/devices/...

When mine was in Access Point mode, it did show the default IP address after bootup but it took a long time. The display would show normal scanning and then get interrupted by the default IP address display. 10-20 seconds, maybe? I never timed it. To check for AP mode, just look at the list...

Thanks. I wasn't sure if I had to do something else to make the DHCP mode persistent. I'll probably never know why the HM refused to connect on T-day. I just turned it on the way I always do. No messing with setup. But apparently it was in AP mode for some reason. Yes. I assumed that, but...

You guys have been sniffing at the right thing. When I first fired the HM up on T-day, everything was normal except for it not connecting. In the course of fiddling with it, using the right button to look for its IP address (no joy) it did offer to reset but I left the "no" default. One time...