Snowbirding 2022: The Power Problem

I finally track down and solve an annoying battery power issue.

The problem first reared its ugly head at Pahranagat National Wildlife Refuge on Saturday night — the day after I’d left home. (I’d spent that first night at a campground in Idaho with a power hookup.) Nighttime temperatures were forecasted to be at 20°F or lower so, like anyone who values comfort, I stacked some extra blankets on my bed at nighttime and turned the heater on.

How It All Works

My RV’s heater is forced air propane. That means there’s a propane burner that heats the air and a battery powered fan that blows the air into the living space. So in order to have heat, you need propane and battery power.


My rig’s batteries in their compartment. The space is so limited that only a few different battery models will fit — so please don’t lecture me about 6v systems because I’ve already explored that option.

My RV has two 12v deep cycle marine/RV batteries on board. They are connected to the rig’s internal converter (which converts AC to DC power when I’m plugged into an external AC power source), a power connector to my truck (when the camper is on the truck and plugged into it), and my solar panel controller (which is attached to two 100-watt solar panels on the rig’s roof). That gives me three ways to keep those batteries charged: external power (if I’m plugged in), power from my truck (as I’m driving down the road), and solar power (during the day, which varies depending on how sunny it is).

My batteries showed fully charged — per the voltage reading on the solar controller — when solar power eased off late in the day. That was fine; that’s the way it’s supposed to be. The system is set up so that if I’m parked in a sunny place during the day, the batteries will fully charge before nightfall. I’m extremely conservative with my power use because, although I have a generator, I don’t like to run it.

Between sunset and the time I went to bed, power seemed to drain out of the batteries a bit more than I remembered it doing. Keep in mind, however, that I hadn’t been “dry camping” since the previous winter, so I really didn’t remember what kind of power drain I’d been experiencing. (The batteries were new; replaced in January.) I went to bed with the heat set low to just take the big chill out of the air.

The Problem Rears Its Head

I woke early and noticed that my refrigerator was showing an error code that meant it wasn’t getting enough power. My refrigerator runs on propane (when I’m not plugged into external power) but, like my heater, it requires a certain amount of DC power to operate its thermostat and interior light and who knows what else. When power drops below a certain level, the refrigerator shuts down and the error message appears.

I checked the solar charge controller. It read 10v. That was very bad.

I got up and turned everything off. And then I got back under the covers, which was pretty much the only way I’d stay warm until it was light enough for the solar panels to go to work or late enough for me to run my generator in a campground where other people might like to sleep past 5 AM.

I had a hell of a time getting the generator started later that morning in 18°F temperatures. I thought it was a problem with the generator itself but I think it was more the fact that the previous user — who was not me; when will I learn not to lend out my stuff? — ran it dry of fuel. Later, I managed to get fuel and get it running and everything was back to normal.

Or at least I thought it was. I figured that I’d just expected too much from the fully charged batteries the night before. Instead of running the heater all night, I’d leave it turned off the next night and turn it on in the morning to warm the place before I got out of bed. In the meantime, the batteries were charging fine in the bright sun of my campsite.


Here’s my usual generator setup. There’s an adapter that makes it possible to plug in my 30 amp RV cord to a standard 20 or 15 amp outlet.

But the next morning, when it was only slightly warmer than the morning before, the batteries were already dead — without me running the heat at all!

I waited as long as I could and then said, “F*ck this, I’m running the generator before I freeze my ass off.” And I started the generator at 6 AM. Fortunately, my closest neighbor had left the day before and my 2KW Honda is pretty quiet. Plugging the camper into the generator is pretty much the same as plugging it into any AC power source; I had power and the batteries would charge.

Plugging In, Then Trying Again

Meanwhile, winter weather — rain and wind in that part of Nevada — was moving in. I decided that what I needed was either a campsite with a power hookup or a campsite in a remote area where I could run my generator anytime I had to.


At Valley of Fire State Park. I’m not totally opposed to campground living; I just don’t really like it when I don’t need it.

I went to Valley of Fire State Park and enjoyed two nights plugged in at one of their campgrounds. Surely being plugged for more than 40 hours straight would fix the battery issues. But I had my doubts. I’d dry boondocking — that’s camping with no hookups — one more night before I tried to get the batteries replaced.

So I spent the night at Stewart Point on Lake Mead. I had a great campsite and I would have loved to spend more than one night there. But it was the same story in the morning — freezing cold with no battery power. I didn’t even bother running the generator. I made my coffee in a travel mug, loaded up my pups, and left the campground right around dawn.


Boondocking at Stewart Point. I could have stayed here a week if it weren’t for the power problems.

Tracking Down the Problem

That was Thursday.

I already had reservations at Willow Beach campground on the Colorado River for Sunday and Monday night. I changed them to that night. If I couldn’t fix the power problem, I’d need a power hookup again. I was tired of freezing my ass off in bed and very tired of seeing my pups shivering, even with their coats on, as they tried to sleep. I was starting to wonder whether I should just give up and go home. I was seriously sick and tired of dealing with the problem.

I headed in to Henderson, NV where there was a Camping World. Camping World is a chain of RV sales and service places that are usually quite large and well-stocked. I had already called them the day before to see if they could replace my batteries while I waited. I was not going to deal with a place that made an appointment two weeks from Tuesday.

Long story short: because the Interstate brand batteries were less than a year old, they were covered under warranty. But because Camping World didn’t sell that exact model, they wouldn’t swap them. I wound up going to the Interstate location in Las Vegas. All this time, I’m trying to get the folks who sold me the battery to email me a copy of the receipt as proof of purchase.

One of the Interstate techs came out and tested the batteries. By this time, the drive plus the sun had fully charged them. The first battery tested good. I started thinking about how I’d track down the power issue if the problem wasn’t the batteries. But the second battery tested bad. And the guy found the date code on the battery that proved its age so I didn’t need a receipt after all.

There was some trouble with how I was going to swap them. They didn’t do installations on RV batteries — just car batteries. And they wouldn’t give me the new battery unless I left the old one. And then they also were trying to sell me the replacement or even a replacement for the one that wasn’t bad. They gave me the number of a mobile installer — likely someone they get kickback from — but I also called Camping World. Camping World wanted $149 plus tax to swap the batteries.

Once again, I found myself saying, “F*ck that. I’ll do it myself.”


It’s the battery on the left that needed replacement. One terminal had just one fat cable while the other had two fat cables and three skinny cables. It was difficult getting them all back in place, but I managed.

I dug out my junky $49 Harbor Freight toolkit, which lives at the bottom of one of my outside storage compartments. I took a photo of the mass of wires I’d have to disconnect and then reconnect on the battery terminals. I disconnected the wires on the bad battery. And then I got the Interstate tech to take the bad battery out of the cabinet and lift the replacement battery up into its place. (I don’t think I could have lifted them myself; I tipped him $5.)

I got to work with a couple of wrenches and fastened all the wires where they needed to be. No sparks, no flames. I went inside my camper to look at various things that would indicate success or failure. The solar charge controller was registering properly, the fridge was on, the stereo’s clock was lit up. It all looked good.

I put everything away and left.

The Test

I had a celebratory lunch in Boulder City. It was more of a reward for dealing with everything I’d dealt with. Then my pups and I took a bike ride on the Historic Railroad Trail that starts at the Lake Mead Visitor Center and goes all the way to Hoover Dam. I put the bike and my pups’ trailer away and we headed down to Willow Beach.


Here I am, parked at a nice level site with a full hookup at Willow Beach. It’s a nice enough campground, but I think the price is outrageous. It’s half price for 65+ with the right paperwork so I have something to look forward to — in five years.

I considered not plugging in so I could test the system right then and there. But I was paying $57 for that campsite for one night and I’d be damned if I wasn’t going to use every single one of its features. So I enjoyed 30 amp power and “city” water and dumped the RVs tanks. I also had a good shower and did a load of laundry before leaving on Friday morning.

I’d decided that I’d test the system at Kingman Wash, a camping area about 3 miles from pavement on Lake Mead. I didn’t want to get any farther away from the Las Vegas area; if the problem wasn’t resolved, I’d need it troubleshooted and I stood a much better chance at finding an experienced RV repair person in a metro area than 100 miles south in some podunk town.

I drove down there, found an excellent camping area with just one other camper, parked on a high point overlooking the beach, pulled out my generator, and set it up. If I was going to need it, I wanted it all ready for me. I discovered that because the site was down in a canyon, I’d only have direct sunlight for about 6-1/2 hours a day — I was in shadows by 3 PM. But the batteries were charged when I went to bed.


I’m parked nearly dead center in this photo. Most of the vehicles by the water were for a SCUBA certification class that showed up during the day on Saturday and Sunday. You can see the afternoon shadow creeping toward my rig.

I left the heat off. It was warmer there than it had been at previous sites. In the morning, I still had 12.5v on the solar controller. I fired up the heat. And some lights. Everything worked fine.

The second night was the same.

For the third night, I got a little daring. I put the heat on before I went to bed. Again, set low to keep the chill out. It cycled on and off as needed all night. In the morning, I still had more than 12v of power.

I didn’t need to run my generator at all.

The problem was resolved.

Current Status

It’s Tuesday morning and I’m boondocking at Six Mile Cove on Lake Mohave. I set my generator up again before going to bed last night and left the heat on overnight. Power levels were fine in the morning, but it’s overcast today and I wanted to charge my laptop and a few other things so I ran the generator for about two hours. Now I’m just finishing up this blog post before a lunch break. This afternoon I’ll edit more video.


It’s a crappy day at Lake Mohave but it’s quiet and private, especially since my neighbors just “went into town” for a tire for their RV. (The closest town that might have a tire is Boulder City, which is about 90 minutes from here.)

The camping area is large, right on the lake, has garbage receptacles and pit toilets. It’s just me and a couple in a big fifth wheel toy hauler. Yesterday, I helped them get their rig out of the sand where it was stuck. They invited me to join them at their campfire and I did. My cell signal is weak, but I seem able to get online enough. I’ll spend another night here and then head over to the campground at Cottonwood Cove where I can get a full hookup while some more weather moves through. By that time, I’ll need to dump my tanks, top off my fresh water tank, and maybe buy some propane.

After that, back to boondocking. It’s the kind of RVing I like most — and you really can’t beat the price.

Blog Problems Resolved

It looks like I’ve finally fixed the Home page issues here.

Back in March, my blog started acting weird. I’d post something new and it wouldn’t show up on the Home page for everyone. It showed up for me, though. At least sometimes.

Permalink Settings
Permalink settings for my WordPress blog.

Then I started having issues with the permalinks. You see, WordPress (the blogging platform I use) stores all of its content in a database. Blog pages don’t exist as regular HTML pages like a regular Website. They’re generated on the fly as needed. The permalink is a formulated URL that brings up a specific blog post or other content. For some reason, my permalinks insisted on including a double slash (//) after the domain name. When I tried to restore them to my preferred format (www.aneclecticmind.com/year/month/day/post-name), my blog would cease working.

This was driving me nuts because I couldn’t figure it out for myself and because I was traveling extensively and simply couldn’t take the time to troubleshoot it with my hosting company. When I got home from traveling, I tried once or twice to get it resolved and failed.

I tried again when I was in Ketchikan last week with my laptop and a few hours to spare. My ISP, Bluehost, escalated it up to Tier 3d. Someone did something and they fixed the permalink issue — although they did set it incorrectly. I corrected it today and it “stuck” without causing the whole blog to come crashing down.

But the Home page refresh issue continued to rear its ugly head. I posted two blog posts earlier today — one as a test and the other to get some half-finished content online. Two individual people contacted me to tell me that the post appeared at the link provided on Twitter but not the Home page. I checked and found the same thing.

I logged in to make sure the posts hadn’t been somehow deleted. They were there. I went to the Home page and they appeared. As they should.

I logged out and checked again. They were gone. The most recent post that appeared was the one I’d written back on March 8.

What the hell?

I called Bluehost to set up another ticket. It took a few tries for the support guy to duplicate the problem. He was certain it was related to caching.

I used to use a caching app to speed up the site. The tech support folks had told me that it might be causing the Permalink issue so I deleted it.

The Bluehost guy couldn’t fix this issue, but he promised to open a ticket and move it up to Tier 2. I thanked him and hung up.

I was unhappy. I like to blog. I’ve been blogging here since 2003 — 16 years in October. There were a lot of things I wanted to say, a lot of stories I wanted to share about my recent travels. I can’t add new content to my blog if my blog isn’t working right.

So I rolled up my sleeve and started poking around in the WordPress files that aren’t in the database. I found a cache folder. Inside the cache folder was a folder named all. That folder was full of numbered folders, including some that corresponded to years and, within them, months. Just like WordPress organizes my post permalinks. There was also an index.html file. I opened it up and guess what I found? The home page that kept appearing for people who weren’t logged in.

I called Bluehost tech support again. Of course, I couldn’t talk to the same guy. The guy I got wasn’t quite as knowledgeable. I told him about the problem and what I’d found. I asked him if he thought I could delete the all folder. He didn’t think that would be a good idea. How about renaming it? Sure. I could always restore the name.

So I renamed all to _all. And I went back to the Home page of my blog. And it properly displayed my most recent post at the top of the Home page.

I asked him to look at it. It showed him the same thing.

I got on Twitter and asked my followers to try it and report back. A handful of them did. It was working right for them, too.

Problem solved.

I deleted the _all folder and everything still works fine. Then I reinstalled a highly recommended cache plugin and turned it on. Still fine.

So at this point, my blog seems to be mostly fixed.

I say mostly because I need to update WordPress to the most recent version and I can’t because the whole blog is running on an old version of PHP and I can’t seem to update it. That already has a Bluehost ticket in Tier 2 going.

Why can’t things be simple?

Lesson Learned: Don’t Update an iOS Device on the Day the Update is Released

I learned it the hard way — and won’t forget.

Yesterday, I spent about 3 hours in an Apple Store. It was not pleasant.

It all started when, in preparation to update my iPhone and iPad 2 to iOS 5, I synced my two iOS devices. I got an error message. Thinking that was probably not a good thing before doing an OS update, I made an appointment at the local Apple Store — which is walking distance from our Phoenix place — with an iOS Genius. An hour later, I walked over with my iPhone, iPad, and syncing computer, a MacBook Pro.

The “genius” (and this guy definitely deserves his title put in quotes) looked at the situation and told me that because the error message appeared on my Mac and not on my iOS device, he couldn’t help me. But he could make an appointment for me later that day.

If there’s every a way to piss me off, it’s to tell me I’ve wasted my time and need to come back later in the day to waste more time. I gave him a lot of grief, which he deserved. It gave me a really good idea about the quality of management at the Biltmore Apple Store: it sucks. It was the first time I’d ever left the store angry, without my problem resolved.

I went back to my office and started troubleshooting on my own. That’d when the iOS 5 update was released. Since the problem had been resolved on my iPhone, I figured I’d update that. Things went smoothly — on our fast Internet connection, I was able to get the download in less than 15 minutes. But the upgrade kept failing.

So I showed up at the Apple Store again for my second appointment of the day. This time, they put me with a Mac expert. He listened to my problems, looked at his watch, and told me he had to go to lunch in 8 minutes.

What was I saying about Biltmore Apple Store management? Oh yeah. It sucks.

He started out by using Software Update to look for updates. I’d done that first thing in the morning and there weren’t any. But now there was — Mac OS X 10.7.2 — making me look like an idiot. He began the install and while it was working, left for lunch.

Another genius stepped up to fill his spot. I told her that since the process would take some time, she should help someone else. I’d try to resolve it on my own and let her know how I did.

I got the Mac OS update done and then tried again to update my iPhone. No joy. By this point, everyone was tweeting about server problems. I didn’t think this was server related, but when I realized that some kind of verification was going on and that’s where it was failing, I agreed that was the issue. I kept trying.

Connect to iTunesMy phone became “bricked” — completely unusable — with a “Connect to iTunes” image after the fifth try.

Now a small seed of panic began growing inside me. My iPhone is my only phone. It’s for personal and business use. It’s the only way I can be contacted by voice communication.

After trying a few more times, I talked to the new genius they’d assigned to me. (I hadn’t moved from my stool at the Genius Bar.) He tried updating from another computer. When that failed twice, he took it in the back of the store somewhere.

I sat with my laptop and iPad, researching possible solutions on the Web and Twitter.

After 20 minutes, he returned with my phone and some bad news: he wanted to replace my phone.

Now if he was offering to replace it with a factory new iPhone 4, never touched by human hands since leaving China, I would have gone for it. But he was offering a reconditioned phone. And I have terrible luck with previously owned devices. The idea of using a phone that once belonged to someone else — who may have dropped it in the toilet for all I knew — really wigged me out. I told him I’d keep trying.

He set me up with an Ethernet connection to the Internet and a power cord.

And I did. I kept trying updates and failing. While that was going on, I kept searching for troubleshooting tips. @singhpanther on Twitter suggested Lifehacker. I found “How Do I Fix My Bricked iPhone, iPad, or iPod touch?” and worked my way through the instructions, including the DFU mode stuff. I kept trying updates…and failing.

All the while, people kept coming in with iPhone 4s showing the same “Connect to iTunes” icon I had. I counted about a dozen of these people, all looking lost and bewildered.

Finally, after spending a total of about two hours on that damn Genius Bar stool, it worked. My phone was recovered and working properly with iOS 5.

I don’t think it’s anything special that I did. I think I just managed to squeeze into the server queue at the right time for success.

By that time, the lunching genius was back at his place. I showed him my phone. “Got it working, ” I said.

“Of course,” he said smugly. “What do you think we were doing back there?”

You were doing nothing that worked, I felt like snapping back to him. After all, they hadn’t fixed it. They wanted to replace it and put it back on iOS 4.2. It was my perseverance and refusal to let them take the phone away that had resulted in success.

But as I age, I’m realizing that it just isn’t worth arguing with smug assholes like him. So I just got up off the stool and left.

What was I saying about the management of the Biltmore Apple Store? Oh, yeah. It sucks.

The lesson I learned from all this is this:

With millions of iPhones and iPads out in the world and a rabid user base that’s willing to wait overnight in long lines for new devices, it’s not a good idea to update iOS on the first day of its release. Wait a day or two — it’ll all go more smoothly.

And yes, iOS 5 is worth the wait.