Home/Support/Support Forum/Connectport x2e SE is showed unknown
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Connectport x2e SE is showed unknown

0 votes
help...! I have no idea what I had done, the connectport x2e SE turns unknown in the device cloud and the interface for digi Smart energy cant refresh (time out) and have no respond...

Status: Inactive
Node Type (Role): Unknown
Manufacturer ID: 0xFFFFFFFF
Gateway Device ID: 00409DFF-FF60CCDE

Thank you so much for your respond.
asked Oct 26, 2015 in Device Manager by zhen New to the Community (3 points)

Please log in or register to answer this question.

1 Answer

0 votes
The role is unknown because it is not joined with any other devices on the Smart Energy network.
answered Oct 27, 2015 by userid0 Veteran of the Digi Community (2,158 points)
But it is the gateway, before I configured it, it show it is coordinator and have basic cluster. For now, I cant even refresh the list of: https://digi-se.appspot.com/console?gateway=00409DFF-FF60CCDE
Is the device connected to the Device Cloud?  Is the Smart Energy framework running (main.py in the python menu)?
Yes, the gateway is connected to the Device Cloud and the Smart Energy Framework is running....
Is it possible that because of the firmware? The firmware of the gateway is 3.2.12.4.
for more informations, here followed the system log file:
Oct 21 20:32:48: System: Start
Oct 21 20:33:10: Security audit: + none root:python
Oct 21 20:33:12: Python autostart 1: Script 'main.py' starting.
Oct 22 13:40:21: chronyd: Successfully contacted an NTP server.
Oct 22 13:40:31: Python autostart 1: ERROR: script 'main.py' exited unexpectedly (code:1)
Oct 22 13:40:31: Security audit: + none root:python
Oct 22 13:40:32: Python autostart 1: Script 'main.py' starting.
Oct 22 13:40:39: Python autostart 1: ERROR: script 'main.py' exited unexpectedly (code:1)
Oct 22 13:40:40: Security audit: + none root:python
Oct 22 13:40:40: Python autostart 1: NOTE: delaying 2 seconds before taking action, due to recent reboots/restarts
...