See for more information about the data usage of the a-TroniX Controller.
For troubleshooting high data usage, see also
See for wiring the Ethernet network.
Security policy: Download the PDF.
Most home and small business networks allow all outbound connections by default. You do not have to do anything in this case.
The a-TroniX Controller requires that outbound connections in the network firewall are allowed on the following ports:
The a-TroniX Controller does not require opening any network ports for inbound connections.
It is strongly discouraged and NOT necessary to configure your firewall to port forward or allow incoming TCP and UDP connections on the listed ports above! This is a serious security risk.
To avoid connectivity issues after future updates, it is recommended to whitelist all the eniris.be and eniris.io domains with a wildcard:
At least the following a-TroniX domains are used at present by the a-TroniX Controller:
The a-TroniX Controller is by default configured to use DHCP. You can change this to a fixed IP address in the 'Settings' tab of the commissioning interface.
Only configure a fixed IP address in the a-TroniX Controller if you have no other choice. It is recommended to always use DHCP, and configure your router to always assign the same IP address to the a-TroniX Controller instead!
Write down the IP address you configure. You will need this if the a-TroniX Controller would become inaccessible after changing the IP address!
Lost access to the commissioning interface If you lose access to the commissioning interface after setting a fixed IP address, then check out the troubleshooting section.
As an optional security measure, the a-TroniX Controller can be placed within a dedicated VLAN. When implementing this configuration, ensure that all devices requiring communication with the controller are assigned to the same VLAN.