CC3200 not showing in TeddyCloud

Software TeddyCloud
1

Hi,

I’m trying to add my third Box to TC. I already got a CC3200 and ESP32 Box running. So DNS and network is fine.

Here’s what I did:

cc3200tool -p /dev/tty.usbserial-A50285BI --reset dtr read_all_files ExtractedFromBox/

cc3200tool -p /dev/tty.usbserial-A50285BI --reset dtr read_flash backup.bin
c3200tool -p /dev/tty.usbserial-A50285BI --reset dtr read_file /sys/mcuimg.bin mcuimg.bin cc3200tool -p /dev/tty.usbserial-A50285BI --reset dtr write_file mcuimg.bin /sys/pre-img.bin cc3200tool -p /dev/tty.usbserial-A50285BI --reset dtr write_file hbng-bootloader/flash/sys/mcuimg.bin /sys/mcuimg.bin cd’ed into cert folder

Downloaded the server cert and cd’ed into the folder:

cc3200tool -p /dev/tty.usbserial-A50285BI --reset dtr write_file c2.der c2.der

This was wrong, because I was missing the /cert/ folder. So I did it again:

cc3200tool -p /dev/tty.usbserial-A50285BI --reset dtr write_file c2.der /cert/c2.der

Everything worked without any errors but when I try to add the box in TC, it won’t show in last step of adding a new box.

My config file is the following one:

Summary

{

"general": {

    "activeImg": "ofw1",

    "\_descWaitForPress": "Waits for an earpress on startup",

    "waitForPress": false,

    "\_descWaitForBoot": "Waits for an earpress before firmware boot",

    "waitForBoot": false,

    "waitTimeoutInS": 60,

    "\_descMinBatteryLevel": "Divide through 2785 to get voltage",

    "minBatteryLevel": 8869,

    "ofwFixFlash": "/sys/pre-img.bin",

    "\_descSerialLog": "Logging only works with the debug build!",

    "serialLog": false,

    "\_descLogLevel": "0:Trace - 5:Fatal",

    "logLevel": 0,

    "\_descLogColor": "Use colors in log output",

    "logColor": false

},

"ofw1": {

    "checkHash": false,

    "hashFile": false,

    "watchdog": true,

    "bootFlashImg": true,

    "flashImg": "/sys/pre-img.bin"

},

"ofw2": {

    "checkHash": true,

    "hashFile": false,

    "watchdog": true,

    "ofwFix": true,

    "ofwSimBL": true,

    "patches": \["altCa.305"\]

},

"ofw3": {

    "checkHash": true,

    "hashFile": false,

    "watchdog": true,

    "ofwFix": true,

    "patches": \["altCa.305", "altUrl.tc.fritz.box"\]

},

"cfw1": {

    "checkHash": false,

    "hashFile": false,

    "watchdog": true

},

"cfw2": {

    "checkHash": false,

    "hashFile": false,

    "watchdog": true

},

"cfw3": {

    "checkHash": false,

    "hashFile": false,

    "watchdog": true

},

"add1": {

    "checkHash": true,

    "hashFile": false,

    "watchdog": true,

    "ofwFix": true,

    "ofwSimBL": false,        

    "patches": \["blockCheck.310", "noCerts.305", "noPass3.310", "noPrivacy.305", "uidCheck.307"\]

},

"add2": {

    "checkHash": true,

    "hashFile": false,

    "watchdog": true,

    "ofwFix": true,

    "ofwSimBL": false,

    "patches": \["altCa.305", "altUrl.305"\]

},

"add3": {

    "checkHash": true,

    "hashFile": false,

    "watchdog": true,

    "ofwFix": true,

    "ofwSimBL": false,

    "patches": \["altCa.305", "altUrl.305"\]

}

}

This is the same l’m using on the other CC3200.

Flash folder structure looks like:
(I checked again cc3200tool -p /dev/tty.usbserial-A50285BI --reset dtr read_all_files ExtractedFromBox/ )

ExtractedFromBox

  • ca2.der
  • cert
  • fw
  • settings.cfg
  • sys
  • tmp
  • www

I have this additional ca2.der on /root. Is this a problem?

In the TC log it shows a certificate error:

Summary

Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0200:web_request| Connecting to HTTP server prod.de.tbs.toys:443…
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0252:web_request| trying IP: 10.10.1.244
Jan 31 23:25:05 teddycloud teddycloud[92]: WARN |tls_adapter.c:0582:tlsParseCertificateList| Server name mismatch!
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [532]
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0200:web_request| Connecting to HTTP server prod.de.tbs.toys:443…
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0252:web_request| trying IP: 10.10.1.244
Jan 31 23:25:05 teddycloud teddycloud[92]: WARN |tls_adapter.c:0582:tlsParseCertificateList| Server name mismatch!
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [532]
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0200:web_request| Connecting to HTTP server prod.de.tbs.toys:443…
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0252:web_request| trying IP: 10.10.1.244
Jan 31 23:25:05 teddycloud teddycloud[92]: WARN |tls_adapter.c:0582:tlsParseCertificateList| Server name mismatch!
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [532]
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0200:web_request| Connecting to HTTP server prod.de.tbs.toys:443…
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0252:web_request| trying IP: 10.10.1.244
Jan 31 23:25:05 teddycloud teddycloud[92]: WARN |tls_adapter.c:0582:tlsParseCertificateList| Server name mismatch!
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [532]
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0200:web_request| Connecting to HTTP server prod.de.tbs.toys:443…
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0252:web_request| trying IP: 10.10.1.244
Jan 31 23:25:05 teddycloud teddycloud[92]: WARN |tls_adapter.c:0582:tlsParseCertificateList| Server name mismatch!
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [532]
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0200:web_request| Connecting to HTTP server prod.de.tbs.toys:443…
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0252:web_request| trying IP: 10.10.1.244
Jan 31 23:25:05 teddycloud teddycloud[92]: WARN |tls_adapter.c:0582:tlsParseCertificateList| Server name mismatch!
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [532]
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0200:web_request| Connecting to HTTP server prod.de.tbs.toys:443…
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0252:web_request| trying IP: 10.10.1.244
Jan 31 23:25:05 teddycloud teddycloud[92]: WARN |tls_adapter.c:0582:tlsParseCertificateList| Server name mismatch!
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [532]
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0200:web_request| Connecting to HTTP server prod.de.tbs.toys:443…
Jan 31 23:25:05 teddycloud teddycloud[92]: INFO |cloud_request.c:0252:web_request| trying IP: 10.10.1.244
Jan 31 23:25:05 teddycloud teddycloud[92]: WARN |tls_adapter.c:0582:tlsParseCertificateList| Server name mismatch!
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|cloud_request.c:0262:web_request| Failed to connect to HTTP server! HTTP=Unknown HTTP Status Code error=Bad certificate [532]
Jan 31 23:25:05 teddycloud teddycloud[92]: ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed

I uploaded the server cert multiple times without success.

Additional: What means “Boxine” in the TC Webinterface? It’s red.

Anybody any ideas?

Do you need additional information?

Kind regards

Martin

Edit: I can switch to ofw1 and use the Box with any original tonie without any problems. Also loading cfw was possible.

2

Boxine is the original cloud. If it’s red, then the certs in client/cert (or certs/client) are not the right ones (check the ca.der if it’s from boxine) or any other problem with prevents reachable original cloud (blocked network, missing dns server,…)

Ensure the c2.der is the teddycloud one from certs/server folder (or downloaded from the gui)

3

I checked. I’m using general DNS rewrites on my AdGuard Home, so TC obviously can’t connect to the original cloud.
I will use altUrl.305.json instead to give TC access to the original cloud and redirect the boxes to my TC instance.

I’ll try if the “problem” box will show in TC now.

4

Exclude tc from the adguard redirect. That should help also (all devices except teddycloud shall follow the redirect route )

5

I tried everything…
I copied the server ca via samba and flashed it again.

upload server cert

m@Mac-mini-von-Martin-2 teddycloud % cc3200tool -p /dev/tty.usbserial-A50285BI --reset dtr write_file c2.der cert/c2.der

2026-02-01 11:08:44,175 – Connecting to target…

2026-02-01 11:08:46,687 – timed out while waiting for ack

2026-02-01 11:08:47,093 – Connected, reading version…

2026-02-01 11:08:47,101 – connected to target

2026-02-01 11:08:47,101 – Version: CC3x00VersionInfo((0, 4, 1, 2), (0, 0, 0, 0), (0, 0, 0, 0), (0, 0, 0, 0), (16, 0, 0, 0))

2026-02-01 11:08:47,101 – This is a CC3200 device

2026-02-01 11:08:47,101 – Switching to NWP bootloader…

2026-02-01 11:08:47,117 – Switching UART to APPS…

2026-02-01 11:08:47,133 – Resetting communications …

2026-02-01 11:08:48,557 – Uploading rbtl3100s.dll…

2026-02-01 11:08:48,558 – Reading rbtl3100s.dll from file /Users/martinsommer/Library/Python/3.8/lib/python/site-packages/cc3200tool/dll/rbtl3100s.dll

2026-02-01 11:08:48,558 – Getting storage list…

2026-02-01 11:08:49,293 – APPS version: CC3x00VersionInfo((0, 4, 0, 2), (0, 0, 0, 0), (0, 0, 0, 0), (0, 0, 0, 0), (16, 0, 0, 0))

2026-02-01 11:08:49,309 – File exists on target, erasing

2026-02-01 11:08:49,325 – Erasing file cert/c2.der…

2026-02-01 11:08:49,517 – Uploading file c2.der → cert/c2.der [1419, disk=1419]…

.

2026-02-01 11:08:49,853 – Read file after writing for verification…

2026-02-01 11:08:49,869 – Reading file cert/c2.der → /var/folders/q2/d55mzqj55mxcwmz6r87x4gxw0000gn/T/tmph4g0tjip

2026-02-01 11:08:49,950 – File cert/c2.der verified

2026-02-01 11:08:49,950 – Getting storage info…

2026-02-01 11:08:49,965 – storage #2 info bytes: 0x10, 0x0, 0x4, 0x0, 0x0, 0x0, 0x0, 0x0

2026-02-01 11:08:49,966 – Getting storage list…

2026-02-01 11:08:49,984 – Reading raw storage #2 start 0x0, size 0x2000…

..

2026-02-01 11:08:50,110 – [0] detected a valid FAT revision: 144

2026-02-01 11:08:50,110 – Getting storage list…

2026-02-01 11:08:50,128 – Reading raw storage #2 start 0x774, size 0x1774…

..

2026-02-01 11:08:50,230 – selected FAT revision: 144 (active)

2026-02-01 11:08:50,230 – FAT r144, num files: 30, used/free blocks: 938/86

2026-02-01 11:08:50,230 – All commands done, bye.

Added the tb certs via samba to /opt/teddycloud/certs/MAC on the tc server.
Nothing… Codewort “Eule”…