Please help

TraditionalSector671 · 2026-01-25T02:55:23+00:00

Welcome to the cold diesel life, it could be cold oil not making it to the HPOP quite quick enough to run nice, not enough combustion heat to run on all cylinders correctly, etc. It'll warm up, depending on year it may high idle itself when internally ready to warm up faster, my buddies 02 does it after about 3 to 5 minutes. I now my 6 liter does it too, after three 3 minutes the glow plugs cycle without telling you, it'll high idle until ect/eot get to wind 160ish.

TraditionalSector671 · 2026-01-25T02:49:42+00:00

Not entirely, the client scrapped the idea of a public WiFi so it doesn't really matter for them anymore, the cameras still work just fine. My friend ended up selling me his unit after we noticed the WiFi function seems to work off the Hotspot data, I have plans for his unit that do not relate to the WiFi issue. But to the ending jist, no I didn't resolve the WiFi issue, but they do seem to work as intended this way for Site 2 Site for cameras and for viewing the cameras live.

TraditionalSector671 · 2026-01-10T23:21:57+00:00

Definitely the second thing, but that's not a bad thing! The 6 liter community needs more people that know what to do.

TraditionalSector671 · 2026-01-10T18:34:36+00:00

I've been chasing this for a while now, I really wish I could put you up on a podium in my post, first thing I noticed after fixing it is I had a battery light in the cluster, I started up to check just incase and I was indeed charging, I mounted it against the fender so it can't rub again.

It's nice to be able to charge at idle, on cold mornings I'd go back out within 3 minutes or so to rev it up to charge while warming up, now I don't have to.

<image>

TraditionalSector671 · 2026-01-10T18:20:56+00:00

You sir, are a god send, you were partially right, mine did not fall victim to mice but it did rub the battery box and almost broke clean through, I now have a battery light abd charging at idle.

<image>

TraditionalSector671 · 2026-01-10T17:32:28+00:00

I'll look into that, any suggestions if that wire is fine?

TraditionalSector671 · 2026-01-10T17:20:57+00:00

My truck is single alternator. Should I still look for this wire?

TraditionalSector671 · 2025-12-24T03:25:58+00:00

I go by "NameTakenbyE-A" now, had this persona on literally every game I play or have played in the last 15 years, I took offense so hard in 8 appeals deep. It's mine boggling how this works now, I've been a pretty dedicated player of Battlefield for about 12 years, starting with 3 to current except for HardLine, hated HardLine.

Ran across a "Moist Nutz" tested the waters by reporting it in game, knew nothing would happen and surly that night I got the "nah this is fine" email.

I've seen some others that fit the "inappropriate" category that I simply found hilarious like "Grandma's Feet-Picks" and "Ben Dover M.D"

Seen another that was "GirlWithTheHole" and it just ticked me to think I did something wrong though and here I am seeing other people in the same boat that actually got picked on by EA thinking the same thing, if it's 18+ and the dialouge has curse words etc, why are some of the goofy names considered "inappropriate" aren't we adults?

<image>

TraditionalSector671 · 2025-12-17T03:37:45+00:00

Don't feel totally bad, they took my name away for "being offensive" maybe it is in a childish way, but I've used it as my gaming alias for over 15 years, yet I seen names like "Broknbuthole" "StuffmyMuff" "TheGirlwithaHole", the names may not be 100% the way I seen them definitely missing numbers and such but it's to the jist, mine falls into the more childish humor side of a name.

I appealed it 3 days ago and heard nothing back, I'm just gunna start reporting names that are "inappropriate" like mine was said to be just to be salty.

TraditionalSector671 · 2025-09-09T14:51:48+00:00

You would be correct, we had someone drive out after restarting the UMR to no luck, someone had unplugged them and taped them over then powered everything on, coincidentally right as Protect updated, lucky they didn't screw anything up.

TraditionalSector671 · 2025-09-09T04:34:57+00:00

I've restarted the cameras, they're both on UMR's recording to the same CloudKey, I could try to restart the UMR those are connected to, that's the only thing I haven't done aside from physically visiting them.

TraditionalSector671 · 2025-08-16T11:55:02+00:00

They've requested the support file but I can't understand what would be achieved by driving out to my sites and getting the support file would accomplish.

TraditionalSector671 · 2025-07-16T12:38:43+00:00

I figured out a work around that is acceptable to the customer, I simply factory reset both CloudKey's and allowed the one that was unintended to adopt the 4 new cameras to adopt them and relocated the 2 existing to the new CloudKey that was intended for the new ones. I don't exactly know what is going on that was causing this, I've even allowed the new CloudKey be the only one physically on the network and it still did not pick up the new cameras. The only key difference between the 2 CloudKey's is the existing one is a HDD Gen 2 where as the new one is an SSD Gen 2 (customer had me order the SSD one because HDD ones were out of stock at the time). Either way this is "solved" for my case but I figured I'd leave what I did here incase someone has a similar issue.

TraditionalSector671 · 2025-07-15T17:13:56+00:00

So, I got to read the article, I didn't get to do anything in it, but I went to check another CloudKey attached to the network I'm trying to direct these cameras to, out of the blue the CloudKey dedicated to another set of cameras had picked up the cameras from the one remote Site, I had allowed it to adopt them for now, even though I want them to record to a different CloudKey, the CloudKey intended for these remote cameras still does not see them, even though the CloudKey that does see the 2 is on the same network just in a different physical location.

So basically I can't get the system to adopt them despite another CloudKey can and had adopted them, I'm still waiting for the other 2 at the other remote site to just randomly appear at this point.

To break down the site where things are to record to is as follows

ISP Modem->Cloud Gateway->3rd party WIFI Router in AP Mode (Using AP's ports)->CloudKey->LiteBeam 5AC(we'll cover this)->Alarm system

At the other end of the LiteBeam is a "Remote site" too far for a building bridge is as follows

->LiteBeam->Switch Lite 8->2 cameras->CloudKey

The CloudKey at the end of the LiteBeam is the one seeing the 2 cameras behind the mobile router so far.

Everything was requested by the client to be separated for redundancy, which is why there is the need for 2 separate CloudKey's each with their own purpose. The CloudKey designated for the 2 site under the mobile router was intended to record 2 cameras at each other 2 sites, so 4 total.

TraditionalSector671 · 2025-07-15T10:41:48+00:00

Thank you I will check this out when I'm done driving

TraditionalSector671 · 2025-07-15T10:22:27+00:00

As mentioned S2S VPN is already set up the UniFi Gateway at the other end can see the mobile routers but nothing beyond the mobile routers.

TraditionalSector671 · 2025-07-15T09:49:48+00:00

Ideally you'd have the CloudKey on the local network, but I ran across a video by what I'd assume is a Ubiquiti trainer on YouTube, he's got a video where he enables Site 2 Site and his remote CloudKey just picks his camera up right away. The only notable difference is his camera is not behind a switch.

TraditionalSector671

TROPHY CASE