Device Endpoints

The hosts, protocols and ports devices connect to when they push data to Perspio.

Devices that push data to Perspio connect to one of four endpoints, depending on the device family. The ingress connector you enable determines which one your devices use, and its onboarding instructions in the Perspio web app give the settings for that family.

Devices that Perspio collects from by polling a vendor's API, which is most connectors, don't connect to any of these. See Connectors for the difference between pull and push.

Endpoints

ProtocolAUUSDev
MQTTmqtt.perspio.ious-mqtt.perspio.iomqtt.perspio.dev
TCPtcp.perspio.ious-tcp.perspio.iotcp.perspio.dev
UDPudp.perspio.ious-udp.perspio.ioudp.perspio.dev
Azure IoT Hubingress.perspio.ious-ingress.perspio.ioingress.perspio.dev

Use the endpoint for the region your tenant is hosted in. Dev is a test environment you can point devices at before connecting them to production. See Network Endpoints for the rest of Perspio's hosts.

MQTT

Devices publish to port 1883. Each device family has its own topic.

Device familyTopic
Senquipdevices/SENQUIP/#
Milesightdevices/MILESIGHT/#
Lenzedevices/LENZE/#

TCP

Each device family has its own port.

Device familyPort
Teltonika10050
Deep Sea Electronics (DSE)11000
Topfly12000

UDP

Device familyPort
Positioning Universal (PUI)11500

Azure IoT Hub

Devices provisioned as IoT Hub device identities connect on the standard IoT Hub ports.

PortProtocol
8883MQTT
5671AMQP
443MQTT and AMQP over WebSockets, and HTTPS

Allowing Perspio through your network

Devices need outbound access to the endpoint and port for their family. The IP addresses behind these hostnames are dynamic, so allow them by hostname rather than by IP address.

📘

Need help connecting a device?

Contact [email protected] with the device make and model, and we'll confirm the endpoint, port and credentials for it.


Did this page help you?