Description

Linovision LoRaWAN gateways support sending data packets to third party MQTT/HTTP/HTTPS server. We can create a new application on gateway, which can define the method of decoding the data sent from LoRaWAN end-device and choosing HTTP(S) data transport protocol to send data to HTTP(s) server.

Requirement

• Linovison LoRaWAN Gateway: IOT-G6x, IOT-G8x
• HTTP/HTTPS Server

Configuration

Step1. Enable the gateway built-in network server.

Go to Packet Forwarder > General to enable the localhost server address.

Enable the Network server on Network Server > General page.

Step2. Add an Application and Profiles.

Go to Network Server > Applications to add a new application, then click save.

Name: user-defined, arbitrary value

Description: user-defined, arbitrary value

Payload Codec: None or custom your decoder

Go to Network Server>Profiles to add a new profile, then click save.

Name: user-defined, arbitrary value

Max TXPower: default value

Other parameters can be checked from LoRaWAN nodes user guides or you can keep all settings by default.

Step3. Add LoRaWAN nodes to the gateway.

Go to Network Server > Device, add a new device, click save&apply.

Device Name: user-defined, arbitrary value

Description: user-defined, arbitrary value

Device-Profile: choose one of corresponding profiles added before.

Application: choose one of corresponding applications added before.

Other values can be confirmed with the LoRaWAN node manufacturers.

When the status of it is “activated”, that’s mean above steps are done correctly.

Step4. Forward data to HTTP(s) server.

Go to Network Server > Applications to add a “data transmission” for the application.

Fill in the HTTP(s) URL information for each data type, click save.

Uplink data: the URL address to receive all uplink data.

Join notification: the URL address to receive join notification.

ACK notification: the URL address to receive all ACK notification.

Error notification: the URL address to receive all error notification.

Note: If there is user credentials when we access to HTTP(s) server, please add HTTP header, and fill in correct account and password.

If we get data packet on the corresponding URL of HTTP server like below, that’s mean we have connected with HTTP server successfully.

Note: The difference of forwarding data to HTTPS server is that you need upload related gateway certification on your HTTPS server (Contact Linovision to get certification).

Description

When working as embedded network server, Linovision LoRaWAN gateways support both sending data packets to third party MQTT/HTTP/HTTPS server or receiving the downlink commands to transfer to LoRaWAN end devices.

Requirement

• Linovision LoRaWAN Gateway: IOT-G56, IOT-G63 V1, IOT-G65, IOT-G67, IOT-G8x (Firmware version 80.0.0.64 or later)
• MQTT Server/Broker
• MQTT Client tool: take MQTT Explorer as example

Configuration

Step1. Connect gateway to MQTT broker.

Refer article How to Connect LoRaWAN Gateway to MQTT Broker？to connect gateway to MQTT broker and ensure the broker and MQTT client can receive uplinks from devices.

Step2. Send Downlink Command from Gateway

Set the gateway to send downlink commands to device directly to check if the device can receive the downlink commands and take actions.

Device EUI: the device EUI to send downlink commands

Type: downlink command type. For Linovision devices, please select hex type.

Payload: downlink command content (get from device manufacturer). For Linovision devices, please refer to downlink command contents on corresponding user guides

Port: application port of device. It is 85 by default for Linovision devices.

Confirmed: after enabled, the device will send confirmed packet back to gateway if it receives the command. If not receive, the gateway will resend the downlink command 3 times at most.

Note: for class A type devices, the gateway will add the command to queue and send it when the class A device send uplinks.

Step3. Publish Topic on MQTT Explorer to send downlink data to device. 

Set a Downlink Data topic. If you need to send MQTT downlink to specific device, please add “$deveui” on the topic.

Example: /linovision/downlink/$deveui

Publish Topic Format :

/linovision/downlink/[devEUI]

Example :

From the gateway, we can get the device EUI about the device we want to control:

So we can publish a topic on the MQTT Explorer like below:

Topic: /linovision/downlink/24e124126a148401

Format: json

Content: 

send as below format and replace the data content as downlink command

{"confirmed": true, "fport": 85, "data": "CQEA/w=="}

JavaScript

After click Publish, we can go to Network Server > Packets to check. If the gateway have subscribe corresponding downlink topic data successfully, there will be at least one grayed message packet record.

Linovision Device Command Examples

The MQTT downlink command format is fixed as below:

{
"confirmed": true,       //Set as true or false
"fport": 85,            //application port of device
"data": "BwAA/w=="    //base64 format downlink command
}

----END---

Description

When working as embedded network server, Linovision LoRaWAN gateways support sending data packets to third party MQTT/HTTP/HTTPS server. We can create a new application on gateway, which can define the method of decoding the data sent from LoRaWAN end-device and choosing MQTT data transport protocol to send data to MQTT server.

Requirement

•  LoRaWAN Gateway: IOT-G8x (Firmware version 80.0.0.64 or later), IOT-G65, IOT-G67, IOT-G56, IOT-G63 V1
• MQTT Server/Broker
• MQTT client tool: take MQTT Explorer as example

Configuration

Step1. Enable the gateway built-in network server.

Go to Packet Forwarder > General to enable the localhost server address.

Enable the Network server on Network Server > General page.

Step2. Add an Application

Go to Network Server>Applications to add a new application, click save.

Name: user-defined, arbitrary value

Description: user-defined, arbitrary value

Step3. Connect gateway to MQTT broker.

Go to Network Server > Applications to add a “data transmission” for the application. One application can add only one MQTT integration.

Fill in the MQTT broker information and create topic to store different data type, click save.

Broker Address: IP address/domain of MQTT broker

Broker Port: communication port of MQTT broker

Client ID: user-defined, a unique ID identity of the client to the server.

User Credentials and TLS should be enabled and configured as required.

Note: if MQTT broker is HiveMQ, please do enable TLS and set the option as CA signed server certificate.

After MQTT configuration complete, you can check connection status here:

Step4. Add LoRaWAN nodes to the gateway.

Go to Network Server>Profiles to add a new profile, then click save. You can also use pre-defined profiles.

Name: user-defined, arbitrary value

Max TXPower: default value

Other parameters can be checked from LoRaWAN nodes user guide or you can keep all settings by default.

Go to Network Server>Device to add a new device, click Save&Apply.

Device Name: user-defined, arbitrary value

Description: user-defined, arbitrary value

Device-Profile: choose one of corresponding profiles added before.

Application: choose one of corresponding applications added before.

Other parameters can be confirmed with the LoRaWAN node manufacturers.

When the status shows as below, that’s mean above steps are done correctly.

Step5. Add uplink data topic.

Customize the uplink data to publish to MQTT broker and save the settings. If you add “$deveui” on your topic, you can replace it as real device EUI when subscribing topics. 

Example: /linovision/uplink/$deveui

Step6. Subscribe topic from MQTT client to get uplinks.

MQTT explorer is a comprehensive MQTT client and it can be replaced to other kinds of MQTT client tools(MQTT.fx, MQTT Box, etc.)

Open the MQTT Explorer, and fill in related MQTT server information in the popup window.

Name: user-defined

Protocol: mqtt://

Host: MQTT broker address

Port: broker port

User name/Password: if there is user credentials, please fill in it. If not, keep them blank.

Click ADVANCED,copy the Uplink data topic on the gateway, and paste it on the MQTT explorer, click +ADD.

Keep MQTT client ID by default,then click BACK and click CONNECT.

After while, the data will be forwarded to MQTT broker and the MQTT Exploerer can receive the data from MQTT server.

The uplink format is fixed as json and the content is as below.

{
  "applicationID": 1,                   // application ID
  "applicationName": "cloud",           // application name
  "deviceName": "24e1641092176759",     // device name
  "devEUI": "24e1641092176759",         // device EUI
  "time": "2020-0327T12:39:05.547336Z", // uplink receive time
  "rxInfo": [                           // lorawan gateway information related to lora
    {
      "mac": "24e124fffef021be",        // ID of the receiving gateway
      "rssi": -57,                      // signal strength (dBm)
      "loRaSNR": 10,                    // signal to noise ratio
      "name": "local_gateway",          // name of the receiving gateway
      "latitude": 0,                    // latitude of the receiving gateway
      "longitude": 0,                   // longitude of the receiving gateway
      "altitude": 0                     // altitude of the receiving gateway
    }
  ],
  "txInfo": {                           // lorawan node tx info
    "frequency": 868300000,             // frequency used for transmission
    "dataRate": {
      "modulation": "LORA",             // LORA module
      "bandwidth": 125,                 // bandwidth used for transmission
      "spreadFactor": 7                 // spreadFactor used for transmission
    },
    "adr": false,                       // device ADR status
    "codeRate": "4/5"                   // code rate
  },
  "fCnt": 0,                            // frame counter
  "fPort": 85,                          // application port
  "data": "AWcAAAJoAA=="                // base64 encoded payload (decrypted)
}

FAQ

Q1.How to send decoded or customize uplink content to MQTT broker?

A1:  Yes, this needs to use Payload Codec feature on the gateway. Reference articles:

IOT-G56/G65/G67: How to Use Payload Codec on Linovision Gateway

IOT-G63 V1/G8x: How to Use Payload Codec on Linovision Gateway (Old)

Q2.What’s the troubleshooting when the status of MQTT server connection is “Disconnected”.

A2: 

1) Go to Maintenance > Tools >Ping , check if the gateway can ping to the broker address successfully.

2) Check if your MQTT client tool can connect to MQTT broker well, then follow the settings of MQTT client tool to configure the gateway.
3) Check if the gateway MQTT client ID is conflict with other MQTT clients.
4) Check if CPU load is too high, and if there is little available RAM and eMMC.
5) Change the log severity to Debug and replicate the disconnection problem, then download all log files and send them to support@linovision.com.

Q3.Why the connection status shows “connected” but MQTT client does not receive any data?
A3:
1)Ensure the devices has been added to gateway and go to Network Server > Packets to check if there are uplink packets from devices regularly.
2) Ensure the devices has been added to the correct Application.
3) Ensure the gateway firmware is upgraded to latest version. 
4) Change the log severity to Debug and replicate the disconnection problem, then download all log files and send them to support@linovision.com.

Power over Ethernet (PoE) emerges as a game-changer, seamlessly powering devices and transmitting data through a single cable. From security cameras to Wi-Fi networks, PoE has become ubiquitous. Yet, questions persist about its safety when mixing electricity and data.

To address these concerns, we conducted a striking experiment, submerging a powered PoE switch's RJ45 connector in water alongside a hand. Despite the unconventional scenario, PoE technology's safety features shine. With low voltage operation, active power management, and built-in protection mechanisms, PoE proves itself resilient against electrical hazards.

This demonstration not only reaffirms PoE's safety but also instills confidence in its reliability for network administrators and users. While extreme conditions are not the norm, understanding PoE's safety capabilities dispels doubts and underscores its suitability for powering network devices securely. Join us as we unravel the safety of Power over Ethernet, redefining modern connectivity standards.

To enhance comprehension of the PoE network system, it is essential to become acquainted with the PoE devices, as the initially published IEEE802.3af standard categorized Power over Ethernet (PoE) technology into two primary types of power devices: power sourcing equipment (PSE), which supplies power over the Ethernet cable, and powered devices (PD), which receive the power. Presented below is an introduction to power sourcing equipment and a selection of frequently asked questions.

• PoE PSE (Power Sourcing Equipment): PoE PSE denotes the equipment supplying power to PoE PDs. It can take the form of a PoE switch or a PoE injector. The PoE PSE injects power into the Ethernet cable, alongside data signals, enabling connected PoE PDs to receive both power and data through a single cable. It serves as the power source for PoE devices.

• PoE PD (Powered Device): PoE PD refers to the device that draws power from the PoE network infrastructure. It encompasses various device types, such as IP phones, wireless access points, IP cameras, and network switches. The PoE PD consumes power from the PoE PSE, allowing it to operate without the need for a separate power source. Typically, it features an Ethernet input for data communication and a power input to receive power from the PoE PSE.

IP cameras play a crucial role in business surveillance systems, providing visibility and insights into your operations. They are equally popular for home security purposes. PoE switches for IP cameras have become increasingly common, simplifying cabling by combining power and data transmission over a single Ethernet cable. These switches offer versatile solutions for both home and business surveillance needs. In this article, we will discuss the key factors to consider when choosing a PoE switch, share some purchasing tips, and empower you to make an informed decision that aligns with your specific requirements.

Why Use the PoE Switch for IP Camera Systems?

• Power and Data Integration: The PoE switch efficiently combines power and data transmission on a single line, eliminating the need for separate power supplies for each camera or traditional power boxes.
• Extended Cable Runs: PoE switches enable longer distance connections without concerns about voltage loss or cable quality. While Ethernet is typically limited to 328 feet, the range can be easily extended by using PoE network switches or extenders. This flexibility is particularly beneficial for outdoor and large-scale surveillance setups.
• Simplified Cabling: With PoE technology, both power and data can be transmitted through a single Ethernet cable. This simplifies the cabling process and reduces installation costs.
• Multiple Device Connectivity: PoE switches are available in various port configurations, allowing you to connect multiple IP cameras and other PoE devices to a single switch. This facilitates efficient management and scalability within your surveillance system.

How to Choose The Suitable PoE Switch for IP Camera Systems?

Factors to Consider When Choosing a PoE Switch for IP Security Cameras:

1. Port Speed, Port Numbers, and Power Requirements: Consider the bandwidth capacity offered by the PoE switch, such as fast-Ethernet switches (10-100 Mbps) or gigabit switches (1 Gbps). Evaluate the number of ports needed to connect your IP cameras and ensure their power requirements are supported.
2. Power Supply Voltage: Verify that the switch's power supply voltage matches the voltage requirements of your IP cameras to prevent malfunctions and potential damage.
3. Power Budget: Assess the switch's power budget, which is the maximum wattage it can provide. Make sure the total wattage required by the connected devices, including IP cameras, does not exceed the switch's maximum power budget. Check the budget per port to ensure it can adequately power your cameras.
4. Managed vs. Unmanaged PoE Switches: Determine whether you require a managed or unmanaged PoE switch. Unmanaged switches are plug-and-play, suitable for simple setups and home users. Managed switches offer advanced features like network optimization, remote control, and enhanced network status monitoring, making them ideal for larger surveillance projects in enterprises or large facilities.

Tips for Choosing the Right PoE Switch for Your IP Camera System:

• Calculate Power Requirements: Determine the total power needed by your IP cameras and ensure the PoE switch's power budget can handle the load.
• Plan for Expansion: Consider potential future camera expansions and choose a switch with additional ports to accommodate future growth.
• Consider Environmental Conditions: If your cameras will be installed in harsh environments, opt for industrial PoE switches that are specifically designed to withstand extreme conditions.
• Evaluate the Scale of the Project: For large-scale surveillance projects, a managed PoE network switch provides greater flexibility, control, and oversight, allowing for optimized network performance and centralized management.

By following these tips, you can select a PoE switch that meets your specific power requirements, allows for future scalability, suits the environmental conditions, and provides the desired level of control and management for your IP camera system.To make an informed decision, consider the following tips.

How to Connect IP Cameras to a PoE Switch?

Connecting IP cameras to a PoE switch might sound complex, but it's relatively straightforward. Here are the general steps involved:

1. Start by connecting your router to the LAN port on the PoE switch using an Ethernet cable (Cat5e or Cat6). This establishes the network connection between the switch and your router.

2. Plug the power cable into the PoE switch and connect it to a power outlet or a surge protector. This provides power to the switch and ensures its operation.

3. Take Ethernet cables and connect each IP camera to the available ports on the PoE switch. Ensure a secure and stable connection by properly inserting and securing the cables.

4. To view and record the footage from the IP cameras, add them to your Network Video Recorder (NVR) or a compatible surveillance software. This step allows you to manage and access the camera feeds.

5. If remote access is required for viewing the camera feeds from outside your local network, make sure your router is connected to the internet. This enables remote access to the cameras using the appropriate network configurations.

Note: If you need a PoE switch for demanding environments like traffic control cabinets, factory floors, or outdoor locations with extreme temperatures, consider Linovision's industrial PoE switches. These switches comply with IEEE 802.3af/at PoE standards, automatically detect power requirements, and provide power accordingly. They are designed to withstand high levels of vibration and shock, making them ideal for outdoor surveillance deployments in harsh conditions ranging from -40°C to 75°C.

Summary

Selecting the appropriate PoE switch is crucial to ensure an efficient and dependable IP camera system. By taking into account factors such as port numbers, power supply voltage, power budget, maximum power supply, bandwidth capacity, and the choice between managed and unmanaged switches, you can tailor your selection to meet your specific requirements. At Linovision, we offer a range of PoE switches including unmanaged and managed options with varying port configurations (4-port, 5-port, 8-port, 16-port, 24-port), as well as industrial switches designed for diverse IP camera security systems. For more information, please visit the Linovision PoE Switches page.

IPC608AC, it is LINOVISION 4K Ultra HD Anti-corrosion Camera with Tailored Coating, POE IP Camera with Intuitive WEB GUI and Mobile APP, Designed for Sea Shores, Marine, Chemical Factories, Mining Industry, Ports. 

Outstanding Features: 

• 4K ULTRA HD RESOLUTION - Presenting 8 Megapixels (3840x2160) vivid video with 4x more details than regular HD camera; Wide view angle; Efficient bandwidth control with the advanced H.265 compression.
• ANTI-CORROSION DESIGNED - Stainless steel with special coating tailored to resist corrosion, dedicated anti-corrosion cable, powerful sealing performance, designed to be used in corrosive environment permanently. 
• EASY REMOTE ACCESS - Comes with intuitive WEB GUI, compatible to Chrome/Safari/IE/Edge and no plug-in or ActiveX is required; Free mobile App with Cloud access; Also provide PC based VMS software to centralized manage tens of cameras from different sites. Offer API for 3rd party access.
• MAX 30m IR DISTANCE - Equipped with 2 IR LEDs to enable max 30m night vision distance.
• 800m LONG RANGE VERSION IS AVAILABLE - Working with POE-EXT3001LP(2 Pack), the transmission distance can be extended to 800m. It is widely used in Mining Industry and other places where need long distance application. 

Power over Ethernet (PoE) is a well-established technology that allows both data and power to be transmitted over the same Ethernet cable, providing significant time and cost savings for local area networks (LANs). In today's market, you will come across different types of PoE switches, including PoE switches, PoE+ switches, and PoE++ switches. But do you understand the differences between these three types? And how do you make the right choice among them?

What Is PoE and PoE Switch?

What is PoE? Power over Ethernet (PoE) is a technology defined by the IEEE 802.3af standard in 2003. It enables powered devices (PDs) such as VoIP phones to receive power, up to 12.95W, through Ethernet cabling using two of the available twisted pairs.

Then what is a PoE switch? A PoE switch, on the other hand, is a type of power sourcing equipment (PSE) that incorporates PoE technology. It provides power to PDs via Ethernet cables, facilitating network connectivity. Typically, an 802.3af PoE switch supports a maximum power consumption of 15.4W per PoE port, with a voltage range between 44V and 57V. The PDs connected to the PoE switch operate within a voltage range of 37V to 57V.

What Is PoE+ and PoE+ Switch?

PoE+ technology, defined by the IEEE 802.3at standard in 2009, is an advancement of PoE technology. With increasing power requirements of devices like wireless access points, PoE+ was introduced to support higher power consumption.

Similar to PoE switches, PoE+ switches also deliver power over two pairs of Ethernet cables. However, PoE+ adds an additional power class that can provide up to 25.5W of power to a powered device (PD) within a voltage range of 42.5V to 57V. Each port of a PoE+ switch can deliver a maximum power of 30W within a voltage range of 50V to 57V.

What Is PoE++ and PoE++ Switch?

In the pursuit of providing even more power for a wider range of devices, the IEEE 802.3 standard further upgraded PoE+ technology to PoE++ (IEEE 802.3bt standard) in 2018. PoE++ is divided into two types: Type 3 and Type 4. Type 3 enables power delivery of up to 51W to a PD using either two or all four twisted pairs in a copper cable. Type 4 allows power delivery of up to 71W to a PD using all four twisted pairs in an Ethernet cable.

PoE++ switches are the next generation of PoE+ technology. They support up to 60 watts of power per port under Type 3 and provide the highest power level for Power over Ethernet switches, delivering up to 100W per PoE port under Type 4.

PoE vs. PoE+ vs. PoE++ Switch: Which to Choose?

The choice of a PoE switch depends on specific requirements. To help make an optimal selection, consider the following aspects: specifications and applications.

Specifications of PoE vs. PoE+ vs. PoE++ Switch

Based on the information provided, the following reference chart summarizes detailed specifications of PoE, PoE+, and PoE++ switches:

Note: The provided figures are theoretical and the total power capacity of PoE series switches in real-world applications may be oversubscribed when multiple devices use less than the maximum power. For example, having a switch with all PoE++ Type 4 ports doesn't mean all ports will be utilized at maximum load 24/7. Therefore, it is important to calculate the power requirements of all connected powered devices and choose appropriate patch cables for your PoE design.

Applications of PoE vs. PoE+ vs. PoE++ Switch

The key differences between PoE, PoE+, and PoE++ switches lie in their operational modes and power delivery, which determine their applications.

PoE switch

An 802.3af switch, also known as a PoE Type 1 switch, is typically used to support devices that require power delivery of less than 15.4W. Examples include:

• Basic VoIP phones used over the internet

• Wireless access points with two antennas for small networksStationary security cameras without pan, tilt, and zoom

• Sensors, meters, etc.

• Stationary security cameras without pan, tilt, and zoom functionality

PoE+ switch

PoE+ switch with 30W output can power Type 2 devices, such as:

• IP telephones that offer fax, text messaging, and voice calls

• Wireless access points with six antennas

• Remote-controlled pan, tilt, and zoom (PTZ) surveillance cameras

• Biometric sensors that collect biological characteristics

PoE++ switch

A PoE+ switch with 30W output is capable of powering Type 2 devices, such as:

• Two-way video phone calls in a conferencing system

• Building management devices such as gate or door controllers

• Thin clients connected remotely to a server-based computing environment

• Remote patient monitoring devices

And the PoE++ Type 4 switch can support devices such as laptops and TVs.

If your data center or network has relatively low power requirements, a PoE switch would be suitable. However, if you need a more powerful and versatile network that can accommodate a diverse range of devices, a PoE+ or PoE++ switch would be a better choice. These switches offer increased power capacity and performance, allowing for more devices to be connected without being limited by port restrictions. They are particularly beneficial when building infrastructures with higher demands or when planning for future upgrades.

Of course, if your existing PoE network design meets your current demands and is adequate for your requirements, there is no need to change it. It is always wise to assess your specific needs and choose the appropriate switch that aligns with your power and performance requirements.

Linovision PoE++ Switch

The main features of three Linovision PoE++ switches are shown below.

Conclusion

As power requirements continue to increase, the evolution of PoE technology has led to the development of PoE+, and subsequently PoE++. Similarly, PoE-based switches have advanced to PoE+ switches, and now to PoE++ switches. This article has provided insights into the distinctions between PoE, PoE+, and PoE++ switches, as well as their respective applications. We hope this information has inspired you to select a suitable PoE network switch for your needs.

PoE (Power over Ethernet) technology revolutionizes the way power and data are transmitted over Ethernet cables. It enables Power Sourcing Equipment (PSE), such as a PoE switch, to deliver power and data simultaneously to Powered Devices (PD), including IP cameras and VoIP phones. This integration simplifies cabling installation, eliminates the need for separate power cables, and reduces overall costs.

To regulate the power delivery to PDs, the Institute of Electrical and Electronic Engineers (IEEE) has established various PoE standards, including IEEE 802.3af, 802.3at, and 802.3bt. These standards define the maximum power that PSEs can provide and the power requirements for PDs.

Let's delve into the details of these PoE standards and their associated wattage.

PoE Standards Introduction

PoE standards encompass three main types: IEEE 802.3af, IEEE 802.3at, and IEEE 802.3bt. These standards establish the minimum power that Power Sourcing Equipment (PSE) can provide and the maximum power that Powered Devices (PD) can receive.

Understanding PoE Wattage

As previously explained, IEEE 802.3af provides a maximum power output of 15.4W per port, while PoE+ (IEEE 802.3at) supports up to 30W. However, when connecting multiple devices to a single PoE/PoE+ switch, it becomes crucial to ensure that the combined power requirements of these devices do not exceed the maximum power wattage supported by the switch. This ensures that the switch can reliably provide sufficient power to all connected devices without overloading its capacity. Careful consideration and planning are necessary to avoid exceeding the switch's power limitations and maintain stable operation.

For example, let's take the LINOVISION POE-SW708GM-DC12V, a managed PoE++ switch with 8 RJ45 ports and 2 SFP ports. Compliant with IEEE 802.3af/at/bt standards, this switch has a total power budget of 240W. This means it can concurrently power 8 devices compliant with PoE+ standards (30W x 8 = 240). It can also support 8 devices compliant with PoE standards (15W x 8 = 120W).

However, there is no need for concern as modern network switches are designed to be intelligent. When a device is connected, the switch automatically detects whether it is compatible with PoE or PoE+. If the device requires a low power of 5W, the switch supplies exactly that amount. If the device demands a higher power of 20W, the switch adjusts accordingly. And if you connect a device without PoE capability, rest assured that the switch will provide data transmission only.

How Much PoE Wattages are Need?

The power needs of your devices depend on what you're connecting. Most devices, such as security cameras, IP phones and standard wireless APs, require no more than 30 watts.

However, certain devices, such as 802.11ac wireless access points with multiple USB ports and radios, may require over 30 watts for optimal performance. In such cases, PoE++ or PoH switches are the ideal solution. It's worth noting that some devices can adapt to lower power availability by using fewer radios or disabling certain features.

Linovision Managed Switches: Your PoE Solution

At Linovision, we offer a range of PoE/PoE+/PoE++ switches that comply with the PoE standards, providing enhanced security and improved capabilities. These switches are available in 4,5,8 and 48 port options. They support layer 2+ switching features like VLAN and offer advanced management options such as WEB, CLI, TELNET, and SNMP. FS PoE/PoE+ switches can power any 802.3af or 802.3at compliant device on the market, providing flexibility and security. The table below provides specifications for four of our PoE/PoE+/PoE++ switches:

Summary

It is essential to have a clear understanding of PoE standards and wattage to ensure effective device connections. By aligning your devices' power requirements with the appropriate PoE standard, you can ensure smooth and reliable operation. PoE technology simplifies complex cabling setups and offers flexibility in power delivery.