My highlights include:

• The power supplies add roughly 33% to the physical size of the unit, sticking out of the sides like giant plastic thorns. Apparently integrating the power supplies—or at least designing them so they don't dramatically increase the installation footprint—was asking too much.
• Cable entry is at both the top and bottom. So the already enormous mounting footprint isn't actually the mounting footprint, because now you also need clearance above and below it. They could have made the thing twice as thick, half as wide, and put the cable entry in one location, and it would be dramatically easier to mount and adapt to different installations.
• It isn't weather-rated. So despite being infrastructure equipment intended for outdoor/network deployments, it has to go inside another enclosure. And because of the dimensions, protruding power supplies, and cable-clearance requirements, the smallest practical enclosure is something like 24x12—and that's assuming you don't need the outrageous luxuries of a switch, fiber enclosure, outlet, surge protection, or anything else in the cabinet.

Which gets to the part that really blows my mind: who was this physical design actually intended for?

This isn't a piece of desktop equipment. It's UISP equipment. Presumably someone, somewhere, during the design process understood that these things were going to end up mounted in telecom cabinets, huts, shelters, pedestals, and outdoor enclosures where physical space matters.

Yet nearly every design decision seems engineered to maximize the amount of otherwise unusable space around the device.

It's like someone designed the PCB first, wrapped the smallest possible plastic rectangle around it, declared victory, and nobody involved in the project ever tried to actually install one.

Hi everyone,

I would like to report a possible firmware/software issue with EdgePower 54V 72W, running firmware 1.14.0.

Originally, the unit was connected to a 20 Ah lead-acid battery, with the battery charging function managed directly by the EdgePower. Everything worked correctly for a long time. Later, due to autonomy requirements, I increased the battery capacity to 45 Ah. After performing the battery reset procedure, everything seemed to work fine at first. However, after a few months, the EdgePower started reporting that the battery was no longer holding charge.

I replaced the battery with another model, but the same problem appeared again. If I performed a battery reset and restarted the EdgePower battery charging function, the issue disappeared for some time.

After reading some forum discussions, I understood that using a battery with a higher capacity than expected could cause strange behavior with the internal charging management. For this reason, I decided to disable the internal battery charging function on the EdgePower and use an external lead-acid battery charger/maintainer instead.

With this setup, the external charger/maintainer reports that the battery is healthy and keeps it fully charged. The battery also works correctly during power outages.

The problem appears when the main AC power is interrupted and then restored.

When AC power fails, the EdgePower correctly switches to battery operation. The graphs show that the battery is working properly, and the runtime is consistent with the load and battery capacity.

However, when AC power returns, both the external charger/maintainer and the EdgePower are powered again, but the EdgePower continues to report that AC is missing. It keeps operating as if it were still running from battery, even though AC power is physically present. The external charger keeps charging/maintaining the battery, so the system continues to work, but the EdgePower status remains incorrect.

A software reboot or a full power cycle of the EdgePower does not solve the issue while the external charger remains connected to the battery.

The only way I have found to restore the correct AC status is:

1. Disconnect the external battery charger/maintainer from the battery.
2. Re-enable the EdgePower internal battery charging function from the software interface.
3. At that moment, the EdgePower immediately detects AC correctly again and changes status to AC present.
4. Then I disable the EdgePower internal charging function again.
5. Finally, I reconnect the external charger/maintainer.

After this procedure, the system works normally again until the next AC power outage/restoration event.

This behavior has been reproduced on two different installations, both using:

• EdgePower 54V 72W
• Firmware 1.14.0
• External lead-acid battery charger/maintainer
• Different batteries, with different capacity/model

For this reason, it looks like a possible firmware bug related to AC detection when the internal battery charging function is disabled and an external charger is connected to the battery.

Expected behavior:

When main AC power returns, the EdgePower should detect AC input correctly and switch its status back to AC operation.

Actual behavior:

When AC power returns, the EdgePower keeps reporting AC missing and continues to show battery operation, even though AC is physically present.

Has anyone else experienced this behavior?

Is this a known issue with firmware 1.14.0, or is there any recommended configuration when using an external battery charger/maintainer instead of the internal EdgePower charging function?

Thanks in advance.

@Edgepower@UI-Team

We use ubiquiti in our large networks.

This is the first time we realy need your help!

We do use UISP Power with UISP Switches Pro, Console, etc.

We are setting up some very special substations at the mountains - VERY VERY hard to get there.

Therefore we decide to use a third UPS for last way communication.

We choose UISP Power.

But we need this type of cable - Which can not be found to order.

PLEASE HELP US - We need at least 50 cables. Where can we order or find a product number?

Here is a picture from the cable, supplied with UISP Router/UAC Power supply for AC

BIG THANKS in advance for your help!

Best regards from Austria

All I want is the UISP Dual-Power Injector (UACC-Dual-Power-Injector) to be powered by 120V/240V AC power instead of the DC Transport power. What is holding this up, a patent or something, optoisolators design, just make it weather proof and it will sell for my rural customers.

I'm having ongoing issues with the Ubiquiti ETH-SP-G2 Surge Protectors. I have 20 units installed, paired with 10 sets of Ubiquiti antennas (one at each end). I'm using outdoor-rated Cat6A cable and have tested multiple types and brands of connectors.

Initially, I used Cable Matters shielded Cat6A connectors. When I connect these to port 1 on the surge protectors and run Cat6A patch cables from the other port to the switch, I notice a serious reliability issue: if I manually move the cables even slightly, I lose connectivity. The connection is not stable at all.

I also tested with Ubiquiti ToughCable RJ45 Cat6 connectors and experienced the exact same problem. I even tried using Cat5e patch cables, but they fit loosely and can shift just enough to cause disconnections.

What's concerning is that all of the ETH-SP-G2 units show this same behavior. I recall reading about similar issues in the past has anyone found a solid fix or workaround?

Appreciate any insights or suggestions.

Thanks!

Had anyone also had this issue and know how to fix it? Or should i file for warranty.

First thing I tried was to upgrade from firmware v2.0.9-hotfix-7 (last official release, from 2023) to the beta firmware v3.0.0-rc.9 but that didn't seem to fix the instability.

Then I opened the chassis and measured temperatures of around 55C with a thermal camera on the main chip with the small heatsink.

I did have cases in the past where adding a larger heatsink or a fan was the definite solution in restoring stability to various routers/cable modems, so on a hunch, I cut a hole in the chassis and added a 40mm fan (sorry to my trusty ER-X). Now the temperatures on the main chip are around 35C and stability seems better (pending longer testing, though).

Still, this is a bit odd... The router is in the cool basement not exposed to external heat, so why would it be suddenly overheating? Could it be due to some external intrusion (attempt?) activity? Or perhaps just from legitimate increased bandwidth and electromigration after many years of running that might effectively degrade the heat tolerance of the chip over time?

Is there any logging I can enable and share with the community (and how to sanitize it?) to look for signs of intrusion trouble?

CPU load is really low from what I can tell. The only unusual thing might be that I have my ER-X mounted upside down against the bottom of the basement stairs, so heat rising up might collect against the PCB rather than rising out of the chassis. But I think it has worked well in this orientation for years.

If you can give me some pointers, I'm happy to try and investigate this some more.

Attachments:

• ER-X running dashboard.png
• ER-X running with fan.jpg

Is this a replacement for the Ubiquiti INS-3AF-O-G Instant 802.3af Outdoor Gigabit Adapter?

Ive noticed its output is only 18v where the LTU stuff requires 22–27V DC. The description for the INS-8023af-O states "An Instant PoE Adapter designed for outdoor use that transforms almost any Ubiquiti PoE device into a fully compliant 48V, PoE-compatible product."

Can anybody help with clarification of the following

1. Will it allow LTU's to be powered from a 48v POE Switch
2. Is it Gigabit?
3. Am i going stupid?

Unfortunately, the internal batteries provided for the devices appear to be faulty. Both UISP-P devices show them as disconnected or not installed even though they are installed. Very rarely, I can push down on the battery and it will say the battery is in a degraded state. I tested the external battery feature and that works fine with 24v lead acid. It appears just the Li-ion internal batteries are the issue.

Has anyone seen this issue or did I just get unlucky and got two defective devices?

I just need to know if this connection is correct because I want to combine it with home assistant - The connection according to the picture will power the battery from the mains but also via unifi SunMax, but the mains power will be blocked and it will primarily be powered via solar, but if the battery drops to 20 percent, the mains power will automatically turn on to charge the battery to 80 percent where it will turn off again and be charged via solar. I just need info if I can connect it like this

Funktion "Switch DHCP to Static IP Address" not working.

my device powerbeam 5ac gen2 has no option to show point to multi point.only access point and point to point option in first page.can any one confirmed me ho to configure as a multipoint and where is a option. Thanks