TRENDnet 6-Outlet Managed PDU, TPI-06, Rackmount Power Distribution Unit, UL Certified, 1 x NEMA 5-15R Bypass Power Outlet, 1 x Gigabit RJ-45 Port, Overload Protection, Surge Protection 2160J, Black

Power costs are out of control right now, so I bought this PDU to better manage my power hungry devices like my server, NAS, and my a/c unit. I also connected one of my PoE switches and my router. Using the PDU and the Hive cloud service let’s my control power even when I’m not at home. I recently power cycled the router from work because the kids complained the internet was slow after school. It was pretty easy and worked! I also like that you can create a power schedule, so we’re not wasting any extra power for things that don’t need to be on all the time. I haven’t had it long enough to see if it has reduced my power bill, but I think it will.

I purchased this when I installed ethernet in my house. No problems with it in over 10 years time now

It's solid and it works. I have a few of these and was able to punch down all the cables with every single connection testing perfect the first time. Great quality for the price.

I'm an IT professional and I've been looking for a managed PDU for a while. To be able to control each power outlet, and manage the power consumption to troubleshoot remotely if there's an issue has been great. It sounded like there were a few people who had some buggy issues with the features, but I haven't experienced any problems a few weeks into consistent use. Also when I reached out to trendnet support, they let me know the newest firmware update is being released next week which is supposed to address any bugs they've had. Happy so far, and if you're looking for remote power management that has the capability to be cloud managed, this is it.

Unless you discover a problem, you'd never know if a patch panel performs to spec, but I trust Trendnet. The physical build it solid, no funky finishing, punches down the way it should, and patch cables don't get stuck.

I purchased this TRENDnet TPI-06 PDU in early January 2025 and initially, the product appeared promising. I installed it immediately upon receipt, updated it to the latest firmware available at the time, and configured it to use the local web GUI interface only — intentionally avoiding their Hive cloud management platform, as I prefer to avoid third-party remote control over critical infrastructure equipment.The PDU was installed to power three servers and a monitor, all protected behind a commercial-grade battery backup system. For the first two months, it operated without incident.First Signs of Failure (Early March 2025):In early March, following an extended power outage, I safely powered everything down and then brought the servers and equipment back online without issue. Shortly after, I needed to temporarily add another device and attempted to log in to the PDU’s GUI to enable an unused outlet. This is where problems began.Across multiple browsers (Microsoft Edge, Chrome, Brave) and devices (PC and phone), I encountered an issue where the login screen would load, but after submitting valid credentials, the interface would hang and remain blank. Only by using Chrome in Incognito Mode was I finally able to access the GUI.Firmware Update – New Problems Introduced:To attempt to resolve this login issue, I checked TRENDnet’s site and found a firmware update (version 1.1.0.20) released in February. I followed the recommended process to upgrade the firmware while connected via LAN and with the PDU running on a UPS to ensure power stability. The update process was exceptionally slow and offered no clear progress indication. After waiting over an hour without successful access, I manually power-cycled the unit. It eventually came back online, retaining my prior configuration.However, soon after, the PDU hard-powered off all outlets without warning, abruptly shutting down my servers. On inspection, the system logs were filled with repeated Safe Voltage event errors: "4R-US [PService] Pservices - Detect occurrence of Safe Voltage event." These errors were clearly erroneous. The power in my environment is rock solid at 110V — verified by both my UPS and independent voltage meters. There were no actual voltage fluctuations.Attempts to Resolve – No Improvement:I adjusted the PDU’s Safe Voltage Range Settings, widening the minimum and maximum thresholds (100V to 125V), but this had no effect. The logs continued to fill rapidly with false voltage errors. I then disabled the Safe Range feature entirely, which initially stopped the unit from shutting off the outlets but did not stop the flood of error messages in the logs.Factory Reset – Hardware Reset Button Ineffective:At this point, I attempted to factory reset the unit to see if a clean start would clear the fault condition. Following the instructions in the User Manual, I used the hardware Reset button — holding it down for the recommended 5+ seconds while powered on. Although the LEDs and reboot indicated reset had occurred, none of my settings were cleared. I repeated this process multiple times, including attempts to power cycle while holding the button and holding the button during boot. In every case, the PDU’s configuration remained intact and unchanged, which should not happen with a factory reset.TRENDnet Support Ticket – Communication and System Failures:On March 21st, after repeated failures, I submitted a detailed support ticket to TRENDnet, including all of the above information and asking whether a firmware downgrade might resolve the issue (noting that prior firmware versions were not available for download on their website).Seven days passed with no response. When I manually checked the ticket status, I discovered that they had posted a response without sending an email notification. Their reply merely stated that the ticket had been forwarded to another department — and that had occurred three days earlier on the 25th. I updated the ticket at that point, providing additional information about the temporary success of disabling Safe Range Settings and mentioning further problems with date/time inconsistencies in the logs (even with proper NTP configuration).TRENDnet support replied the same day, apologizing for the delay and acknowledging that the forwarding of my ticket had failed in their system. However, their reply was unhelpful — they simply stated, "Downgrading the firmware will make no effect" (with no technical explanation) and advised me to factory reset the unit, which I had already documented in detail as ineffective. It was clear they either had not fully read or considered the information I provided.Further Troubleshooting – Reset via GUI & New Errors:Nine days after opening the ticket, I attempted a factory reset via the web GUI instead of the hardware button. This time, the reset worked — all configurations were cleared. I reconfigured the unit from scratch, hoping this would finally resolve the issues.Unfortunately, new problems began immediately. The logs began filling with repeated outlet connection and disconnection messages (e.g., [pdu_outlet_connection] outlet x was connected followed by [pdu_outlet_disconnection] outlet x was disconnected). Outlets began shutting off randomly again, with no clear cause, and the previous Safe Voltage errors persisted much less often, but sporadically. Disabling the Safe Range Settings this time no longer prevented the random outlet shutdowns.TRENDnet Ticket System Malfunctions:To add to the frustration, TRENDnet’s support portal is being extremely problematic. I attempted over 20 times to update my ticket with detailed descriptions of these new errors and log files. Each time, I encountered persistent "Invalid Input" errors. I went to the effort of stripping down my post content, checking for problematic characters or syntax, running the text through AI sanitization, and even shortening the text length — all with no success. Ultimately, I resorted to putting my detailed update into a text file and attaching that and the new log file with only a brief message pointing to the attachments. Even then, the system mis-associated the detailed update attachment to the original post within the ticket and the new log file to this short post, forcing me to write another post explaining this - which it would also not take! I resorted to the same method again, attaching a text file with this short explanation to and even shorter message. I'm talking about a sentence or two hear!Summary:After a week, plus, of troubleshooting and support ticket updates, the TRENDnet TPI-06 PDU remains unusable in my production environment. It has repeatedly hard-shut down my servers without cause, despite stable power conditions and proper configuration. The firmware appears to be unstable and unreliable, and the support experience has been slow, circular, and ineffective.While the web interface is clean and the feature set is appealing, the core functionality of a PDU is to reliably deliver power — and this unit has categorically failed to do so.At this point, I am waiting to see if TRENDnet will step up to resolve this issue — either by replacing the unit or offering a refund. If not, I will have no choice but to remove it permanently and seek an alternative solution. For anyone considering this product, I strongly advise against using it in any environment where uptime and equipment reliability are important.

We've been running Cat 6 cables throughout the house, even though we have wireless, as a wired connection is always faster and Cat 6 can also be used to run different types of signals...not just network.All of these outlets run back to my server closet and to this patch panel. Which, provided you have the punch down tool, is easy to use and is much easier than making RJ-45 plug ends!Punching down is way easier than crimping. Amazon ships super fast and this a great product.

It’s a patch panel, not much to say other than it works great and fits perfectly. The punch down posts are tight and I’m confident cables won’t back out. Every port I punched down and tested seems to be transmitting perfectly, overall it’s a good purchase, maybe a bit overkill for home use but for the price why not?