Connection issues ANT cc3200

Software TeddyCloud
1

Hello everyone,

I’m also having connection issues. During the last CC3200 box flashing step, the codeword “ant” is heard.
I have teddycloud, Portainer with macvlan, and AdGuard Home in separate containers.
I assigned the hostname tc to the Fritzbox and have access through it. The TeddyCloud server is online (green), but not connected to Boxine/Toniecloud (orange).
Here is the log and script:

Blockquote
WARN |server_helpers.c:0806:httpServerUriNotFoundCallback| >> 404 /SETTINGS.CFG
WARN |tls_server_fsm.c:0260:tlsPerformServerHandshake| TLS handshake failure!
ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
ERROR|cloud_request.c:0233:web_request| Failed to resolve ipv4 address!
ERROR|platform_linux.c:0398:resolve_host| getaddrinfo Temporary failure in name resolution
INFO |cloud_request.c:0200:web_request| Connecting to HTTP server prod.de.tbs.toys:443…

Blockquote
services:
teddycloud:
container_name: teddycloud
hostname: teddycloud
image: Package teddycloud · GitHub
ports:
- 80:80 # Optional (für das Webinterface)
- 8443:8443 # Optional (für das Webinterface)
- 443:443 # Port ist notwendig für die Verbindung zur Box, darf nicht geändert werden!
volumes:
- certs:/teddycloud/certs # Zertifikate des Servers
- config:/teddycloud/config # Konfigurationsdatei für den Server und die Boxen
- content:/teddycloud/data/content # microSD-Darstellung für die Boxen
- library:/teddycloud/data/library # Bibliothek zur Verwaltung von Inhalten
- custom_img:/teddycloud/data/www/custom_img # Speicherort für benutzerdefinierte Bilder für benutzerdefinierte Tonies JSON
- firmware:/teddycloud/data/firmware # Firmware-Backups
- cache:/teddycloud/data/cache # Bild-Cache für Inhaltsbilder
restart: unless-stopped
networks:
macvlan0:
ipv4_address: 192.168.178.225
volumes:
certs:
config:
content:
library:
custom_img:
firmware:
cache:
networks:
macvlan0:
external: true

When I set the ngCfg.json to ofw3, the codeword doesn’t appear, but the Toniebox still doesn’t show up. Can someone please help me?

2

Can you post the ngcfg.json?

Besides your toniebox connection problem… orange boxine means cloud disabled. Can you enable it? Is teddycloud then connected to boxine/toniescloud? Or will the status switch to red? Looks like teddycloud has an dns issue.

3

Hi henryk,

Cloud is already enabled under Category cloud.
Here’s the ngCfg.json:

Blockquote
{
“general”: {
“activeImg”: “ofw2”,
“_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”, “altUrl.tc.fritz.box”]
},
“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”]
}
}

4

Ok. Looks fine at least.

You enabled allow new boxes in teddycloud?

You flashed the teddyclouds ca.der as c2.der on the toniebox?

Is the box shown as online in your FRITZ!Box (connected to WiFi)

Regards boxine: is there a x icon or a lock icon? If x, the Color should be a red.
You might add a dns server in your docker compose. It looks like teddycloud is not able to resolve domains.

5

Yes, new Tonieboxes are allowed.

c2.de flashed.

Shows as online in the Fritzbox.

Boxine is displayed with an x ​​symbol, but it looks orange to me.

In the Fritzbox, the AdGuard IP is entered under Internet/Access Data/DNS Server/DNSv4, DNSv6 Server.
And Local DNS Server under Network/Network Settings/IPv4 Settings.

In AdGuard under Custom Filter Rules I have entered the following, but I have also tried to disable AdGuard.
@@||api.revvox.de^
@@||prod.de.tbs.toys^
@@||rtnl.bxcl.de^

Can you explain where I have to set this?

Thanks

6

If you use teddycloud, you should remove the prod tb toys entry. This breaks the connection teddycloud boxine.

Maybe this fixes already the warnings in the docker logs. And no dns thing needs to be done.

You might add an entry in adguard which redirects tc.fritz.box to your teddycloud ip directly. It could be, that using adguard as dns server the tc.fritz.box url does not really work (even if it might work for other devices)

7

I removed prod.de.tbs.toys, but that didn’t help. But the DNS-rewriting in AdGuard from tc.fritz.box to 192.168.178.225 worked :slight_smile:
The code word “ant” no longer appears, and teddycloud recognizes the Toniebox!

However, Boxine is still not connected, and I get the error “Error retrieving Toniebox models.” Click on the “pen” to select the correct Toniebox model – the only option is “Model unknown/not set.”

Log:

Blockquote
ERROR|handler_reverse.c:0029:handleReverse| cloud_request_get() failed
ERROR|cloud_request.c:0233:web_request| Failed to resolve ipv4 address!
ERROR|platform_linux.c:0398:resolve_host| getaddrinfo Temporary failure in name resolution
INFO |cloud_request.c:0200:web_request| Connecting to HTTP server prod.de.tbs.toys:443…

Only the two WARN messages are fixed.

8

Then you may add a dns server in your docker compose and it might work afterwards.

9

Ok, in which docker compose do you mean, teddycloud?

Blockquote
restart: unless-stopped
dns:
-#IP from AdGuard
networks:
macvlan0:
ipv4_address: 192.168.178.225

Is that correct?

Edit: I tested it, unfortunately same problem.

10

Try a public dns server.

If it’s correct I don’t know, I don’t use it.

You may ask ChatGPT if your docker compose file is ok.

11

Perfect, that was the solution. Now I’m using DNS 1.1.1.1 - thank you very much!
Boxine is green and I can choose the model.

Do you know what the many errors in the AdGuard log mean, and Port 40967?
.53 Toniebox, .38 NAS

Blockquote
ERROR response received addr=192.168.178.1:53 proto=udp status=“exchanging with 192.168.178.1:53 over udp: read udp 192.168.178.38:40967->192.168.178.1:53: i/o timeout”

12

No, can’t help you here.