Seneye Web Server and Sensor Node
network and Internet requirements
seneye products run on standard Ethernet, WiFi and Internet network protocols.
If you are using the products with a “normal” home internet connection then you will not need to worry about the following information.
If your network is in any way managed, has firewalls or restricted access then you may need to adjust your settings or add rules to allow communication.
Seneye Web Server (SWS) and Seneye Sensor Node connection requirements
Local Area Network connection
A local IP address is required for each SWS/Node on the network.
This can be granted with DHCP or Static port from the router.
The Local IP address can be fixed internally in the SWS/Node on the GUI of the SWS.
If an LAN cable is used, then it should be at least CAT5 compliant
The SWS/Node will check for an internet connection (WAN access) and connection to the seneye cloud.
Telemetry is uploaded to the seneye cloud by UDP on port 26517.
Readings are uploaded using HTTPS/HTTP on port 80/port 443.
NTP protocol is used to sync the time and date. UDP/port123.
If UPNP is enabled on the router, the SWS/Node will request a port from the router for two way communications.
If a port is granted, this allows for instantaneous synchronisation between changes on the cloud and the seneye device.
If UPNP is not available then the SWS/Node will sync with the servers periodically.
External ports can be manually configured on the GUI of the SWS.
Seneye Sensor Node only
48 volt POE input complying with IEEE_802.3 is required to power the Node.
MAC addresses for each node can be provided upon request