OutBack Power Technologies User Forum Forum

ah, no, i see, i have it on combo soc&v -- there's no color on the ordinate axis for the combo. on solo soc or v there are colors. my bad. apologies.

Check your PMs

The colors on the lines (not the bars) reverted to a single color (orange) some time ago with an Optics 'update' and was reported, and was going to be fixed in a future release

That remote camera crossed my mind today. I have an extra camera I could add. 350 days a year, my system works good, not perfect, good in AZ. The 15 days it doesn’t work good it’s rainy and I need to manually change things. Today was one of those rainy days where batteries needed more power, so I needed to swap to UPS mode to keep them from Dying. So of course Optics goes down. Debating to go home to check, but comes back up. My backup WiFi access is a Fortress power battery app, which has quit working two weeks ago. No response after three days from Fortress Power. I have another backup I could do by adding a camera like Shasta Todd did. I can watch that remotely. I may do that.

We call that a high security air gap.

yes, that's what i'm referring to. they no longer display on my graphs. settings haven't changed. do they display for you?

People have suggested WAN to LAN firewall devices so I can access my Mate3s if OBs server is down. Those devices are ~$200. Here is my $40 webcam hack.

I will also point out that my graph no longer has the temperature and voltage and soc thresholds from settings reflected in green, yellow, red sections on the graphs, which is a big loss. i quite liked that feature and hope it comes back. thx I might be mistaken, I believe the voltage green/yellow color changes are determined by your low battery voltage setting in the device registration page.

I will also point out that my graph no longer has the temperature and voltage and soc thresholds from settings reflected in green, yellow, red sections on the graphs, which is a big loss. i quite liked that feature and hope it comes back. thx

In iteration 2 the Mate's web service (and Kimono) kept working without problems I let the running without internet access for over 30 minutes; in comparison, in the first iteration they failed within the first few minutes. The first iteration ran until the Optics update window, I'd imagine. Then the data export routine "spins" trying to connect, and in failing, monopolizes the port. Shutting off Optics (and sometimes cold booting) removes the source of the port contention, allowing the other apps to communicate.

In iteration 2 the Mate's web service (and Kimono) kept working without problems I let the running without internet access for over 30 minutes; in comparison, in the first iteration they failed within the first few minutes.

Now try iteration 2. • Disable OpticsRE on the Mate. • Disconnect the LAN from the broadband. • Test local Web App and Kimono.