Sixfab Core -- Not working

I’ve gone through the guide on adding a new device, but it never shows in the dashboard(see screenshot).

The device status shows “Online” in the SIM List. However when I click on the device, then go to the “Device(beta)” tab, I only ever see the prompt for creating a device.

Is this functionality knowingly down or are there steps I can take to troubleshoot?

Hi @zach.newman ,

Did you execute the code you copied in the “Device(beta)” tab? If so, can you share the outputs of the command executed from the terminal, please?

Yes, I’ve done so a couple of times now. Here’s the output-

[INFO]  Sixfab user already exists, updating...
[INFO]  Updating sudoers...
[INFO]  Sudoers updated
[INFO]  Updating system package index...
[INFO]  Installing Sixfab ATCom tool...
[INFO]  Sixfab ATCom installed
[INFO]  Initializing environment file...
[INFO]  Initialized environment file
[INFO]  Agent source already exists, updating...
[INFO]  Installing agent dependencies...
[INFO]  Installed agent dependencies.
[INFO]  Initializing agent service...
[INFO]  Agent service initialized successfully.
[INFO]  Manager source already exists, updating...
[INFO]  Installing manager dependencies...
[INFO]  Installed manager dependencies.
[INFO]  Initializing manager service...
[INFO]  Manager service initialized successfully.
[INFO]  Setting default network priority : eth0 > wlan0 > usb0 = wwan0
[DONE]  Installation completed successfully.

Thanks!

No problem with setup.
Could you also please provide me with the following information(logs&files)?

  • All logs of core_manager and core_agent services
  • /home/sixfab/.core/logs/agent-log
  • /home/sixfab/.core/logs/cm-log
  • Raspberry Pi Model
  • Mini PCIe Module

it would be a great help to me. Thanks.

agent-log

2021-03-11 04:43:51,925 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:43:51,927 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:44:21,955 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:44:21,956 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:44:51,986 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:44:51,987 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:45:22,015 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:45:22,016 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:45:52,045 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:45:52,046 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:46:22,076 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:46:22,077 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:46:52,105 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:46:52,106 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:47:22,135 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:47:22,136 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:47:52,165 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:47:52,166 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:48:22,195 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:48:22,196 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:48:52,225 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:48:52,226 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:49:22,255 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:49:22,256 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:49:52,287 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:49:52,287 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:50:22,315 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:50:22,316 --> monitoring.py  ERROR    System data not exists!
2021-03-11 04:50:52,345 --> monitoring.py  ERROR    Monitoring data not exists!
2021-03-11 04:50:52,346 --> monitoring.py  ERROR    System data not exists!

cm-log(This one is very long, but appears to be the following on a loop)

2021-03-11 04:53:03,873 --> identify.py    INFO     [?] System identifying...
2021-03-11 04:53:03,878 --> identify.py    DEBUG    [+] Modem vendor name
2021-03-11 04:53:03,906 --> identify.py    WARNING  Modem vendor couldn't be found with method 1!
2021-03-11 04:53:04,575 --> identify.py    WARNING  Modem vendor couldn't be found with method 2!
2021-03-11 04:53:05,128 --> identify.py    WARNING  Modem vendor couldn't be found with method 3!
2021-03-11 04:53:05,129 --> identify.py    CRITICAL Modem vendor identification failed!
2021-03-11 04:53:05,130 --> cm.py          CRITICAL identify_setup() -> Modem is not supported!
2021-03-11 04:53:05,130 --> cm.py          CRITICAL First identification failed. Retrying to identify required parameters!

Raspberry Pi 3 Model B Plus Rev 1.3

BG96 module(Cellular IoT HAT – LTE-M & NB-IoT & eGPRS)

Sixfab Core does not support Cellular IoT HAT.

Ah, okay.

Do you happen to know if there are plans to eventually support the Cellular IoT HAT?

Also, are there any other services you’d recommend for similar, remote access functionality based on the hardware I’m using? The cloud-based dashboard is a much more appealing solution the reverse tunnels I’m currently using.

There is currently no plan to support Cellular IoT HAT.

Okay, thanks. If any other solutions for that type of functionality come to mind, I’d welcome the suggestions.

1 Like

I have the exact same log files and I have supported hardware (Telit LE910C1-NF)… Raspberry Pi 3B+ with latest Raspbian OS. Sixfab core install seems to go well, tried the recommended diagnostics and get the expected results. Using the kit with SIM card that Sixfab sells.

Hi @nathan ,

Please do the following:

  • Upgrade by downloading the latest firmware from the module product page.
  • Restart core services(core_manager & core_agent)

That fixed it. Thanks!