It looks like when you set it to use DHCP, it was able to configure itself and connect to the iDigi Platform, and that is why it is showing up as connected.
So, when you click to add devices, it shows other devices in the list that you don’t know about? When you add devices, it tries to make it easier by searching your local network for Digi devices. So, if you happen to be at an office location where other people might have Digi devices plugged in, it could be listing those.
That’s right, now you can continue on with some of the documents/tutorials to explore ways you can interact with the other devices through your X4.
The X4 did not immediately “connect”, but I noticed it when I checked from my work office. I hope it stays connected. It is possible that others in the office have the other devices.
I added the device via automatic discovery.
I can ping the iDigi server from the device fine.
I can see the remote connection appear occasionally in Management/Connection
I turned on the trace and it showed it was connecting and authenticating properly and this repeats every 10 seconds.
Unfortunately it still always shows as disconnected.
Any other ideas?
Have you made sure to add your device through developer.idigi.com? Also, can you post the log from trace for a couple connection attempts?
I am finding similar issues with X4 iDigi connectivity from my office , could it be a fire wall issue if so, can someone confirm the port that needs to be enabled?
Some replies suggest port 3197 is this valid for developer.idigi.com server?
Hello,
me too I have exactly the same problem, our Digi ConnectPort X4 is connected on our company network by Ethernet with static IP with the DNS of Google 8.8.8.8 for the primary and 8.8.4.4 for the secondary and DNS Priority : Static.
Remote Management (the section iDigi for the firmware 2.10.0.7 in our case) is configured well with : developer.idigi.com
For iDigi Server Address as indicated below my login on iDigi.
The config box : Automatically reconnect to iDigi after being disconnected is marked well with :
Reconnect after 10 secs
iDigi detects well in automatic the gateway with its MAC address.
But iDigi marks it as : Disconnected. By making a double click above we have no access there (although I had the proof that we could connect in a gateway even if this one is marked Disconnected).
Connect the gateway on another network, with another switch / router / Internet Box is not a solution, to “try” maybe (I am going to make the try because I see that for some that worked), but is needed a valid solution on the long term and on any structure of network.
Have you any ideas ? We we ask the question as regards one or several TCP ports as it already was mentioned and also about a Java applet "Device Manager " iDigi’s which permit to configure iDigi in the case of problems of firewall or NAT.
For us it was a DNS problem in Network Advanced Parameters of Digi ConnectPort X4, the solution we have found is to use “nslookup” from a dos command with a PC connected on the local network. It give a DNS IP Address, and then copy this IP in the section DNS Primary of the Network Advanced Parameters.
And this is OK with Status : Connected.
TCP port 3197 and 3199 must be open.
Is there a HTTP Service that does the connectivty to the remote server (idigi), i am unable to connect using HTTP, below is the telnet log from the device?
56153:edp:DEBG:Trying HTTP
56412:edp:DEBG:Connected at socket level
56412:edp:DEBG: Local address: 10.14.30.222:44766
56412:edp:DEBG: Remote address: 204.236.210.198:80
56414:edp:DEBG:Current IP=10.14.30.114 type=0x1
56414:edp:DEBG:MDH: set keep-alive params: RX=60 TX=60 wait=3
56682:edp:DEBG:HTTP failed
Is port 3197 sufficient for TCP Connections or do we require 3199 as well?
There used to be an HTTP mode of connection, but that is not supported by iDigi.
The device will use either 3197 or 3199 for its connection to iDigi, depending on whether you have selected TCP or SSL as the Connection Method, which is located in Advanced Settings of the Remote Management page.
If you use the Dia, and use the cwm_exist/idigi_db presentations (or in a standalone app, the cwm_data/idigi_data modules), these will push up to iDigi using HTTP or HTTPS.
So, you’ll need 3197 (TCP) or 3199 (SSL) for the connection to iDigi (remote management, firmware updates, commands to device, etc.), and optionally HTTP/HTTPS if you use code in python to push data up to iDigi from the device.