Do I have to connect the Toniebox to the existing network beforehand? Or does the client take care of this during setup?
So, to be on the safe side, I also stored the WiFi network in the Toniebox beforehand. Then I reflashed it (of course, I imported the backup beforehand). This time I made sure that the password was correct.
Now the following happens:
I can see in the router that the Toniebox appears briefly when I do a freshness check - and then disappears again immediately. Then the code word “ant” appears again.
The log from the Docker container now looks a bit more meaningful (much more before that - not sure what you need):
INFO |esp32.c:1380:esp32_get_partition| Search for partition ‘assets’
INFO |esp32.c:1399:esp32_get_partition| Found partition ‘assets’ at 0x00F000
INFO |esp32.c:1102:esp32_fat_extract_folder| Write 'CERT\CA.DER to ‘/teddycloud/certs/client/48ca4344f5e0/CA.DER’ (1419 bytes)
INFO |esp32.c:1102:esp32_fat_extract_folder| Write 'CERT\CLIENT.DER to ‘/teddycloud/certs/client/48ca4344f5e0/CLIENT.DER’ (1030 bytes)
INFO |esp32.c:1102:esp32_fat_extract_folder| Write 'CERT\PRIVATE.DER to ‘/teddycloud/certs/client/48ca4344f5e0/PRIVATE.DER’ (1190 bytes)
INFO |handler_api.c:1232:move_cert_file| Skipped identical CLIENTINFO |handler_api.c:1232:move_cert_file| Skipped identical PRIVATEINFO |handler_cloud.c:0041:handleCloudTime| >> respond with current time
INFO |mqtt.c:0687:mqtt_init_box| Skipping client ‘Toniebox’ (cn: ‘default’)
INFO |esp32.c:1380:esp32_get_partition| Search for partition ‘assets’
INFO |esp32.c:1399:esp32_get_partition| Found partition ‘assets’ at 0x00F000
INFO |esp32.c:1102:esp32_fat_extract_folder| Write 'CERT\CA.DER to ‘/teddycloud/certs/client/48ca4344f5e0/CA.DER’ (1419 bytes)
INFO |esp32.c:1102:esp32_fat_extract_folder| Write 'CERT\CLIENT.DER to ‘/teddycloud/certs/client/48ca4344f5e0/CLIENT.DER’ (1030 bytes)
INFO |esp32.c:1102:esp32_fat_extract_folder| Write 'CERT\PRIVATE.DER to ‘/teddycloud/certs/client/48ca4344f5e0/PRIVATE.DER’ (1190 bytes)
INFO |handler_api.c:1232:move_cert_file| Skipped identical CAERROR|handler_api.c:1336:handleApiESP32ExtractCerts| Different CLIENT already exists at /teddycloud/certs/client/48ca4344f5e0/client.der
WARN |tls_server_fsm.c:0260:tlsPerformServerHandshake| TLS handshake failure!
INFO |server.c:0931:server_init| 2 open HTTPS Web connections
INFO |server.c:0931:server_init| 1 open HTTPS Web connections
INFO |server.c:0931:server_init| 0 open HTTPS Web connections
WARN |tls_server_fsm.c:0260:tlsPerformServerHandshake| TLS handshake failure!
INFO |server.c:0931:server_init| 2 open HTTPS Web connections
INFO |server.c:0931:server_init| 0 open HTTPS Web connections
The good thing is that the existing Tonies can be played again. This was not possible before.
But the connection to the cloud is of course not possible without WiFi.
Out of curiosity, with esp boxes you can’t add/change a wifi connection without flashing?
At least from a user testimonial here, where I suggested they add their wifi connection via the hotspot of the Toniebox itself, it worked. This was a cc3200 box though.
Not sure about that. Works fine on my site and I do not change anything.
Maybe you can try the original WiFi setup with the modified firmware?
You can add a new WiFi without flashing as on every box. Just use the default process for that. Pressing both ears very long and connect to the box wifi ap
1 Like
Does anyone have any idea why the Toniebox is connected to the network for a short time and then disconnects again immediately?
Like described here:
So I tried again today after restarting everything - without success.
I still have no idea why the Toniebox connects to the router for 2-3 seconds and then immediately disconnects again.
Any suggestions on how to deal with the problem?
If the router really kicks your Toniebox, I don‘t know why this should have anything to do with Teddycloud or the exchanged certificate.
But if you want to be 100% sure that your Toniebox doesn‘t have WiFi issues in general, reflash the original firmware and try to use it with the original Toniecloud/Boxine. Then recheck if it works flawless and stays connected to your router‘s WiFi.
The box is still on? Or does the box shutdown/crash after these few seconds?
Why would the router kick the box after granting access? Sounds more like a toniebox related issue.
The box is still on? Or does the box shutdown/crash after these few seconds?
The box is connected, then disappears immediately. Placing the Tonie on the box (which is already saved on the SD card) and it starts playing immediately. So I don’t think it has crashed. When doing the freshnesscheck and placing a tonie on the box, it starts playing. Box appears in router. Box is telling me “Ant” and music starts again.
So I have now flashed back the original version. And tried to connect to the WLAN (mobile hotspot) there, but have the same problem (ant). And I no longer know what to do.
To make it even easier and less error-prone, I have renamed the hotspot and removed the password. And then entered this when changing the Toniebox password. But the error remains the same.
Have you also tried to connect it to your Router instead of the mobile hotspot? Same behaviour?
Tested on a Fritz!Box right now. Same issue.
Tested with a guest network too.
Disabled 5ghz. Still the same.
Fritz!Box output for the toniebox: Last connection 23.11.2024, 13:51
Another thought came to my mind: Is it possible that WIFI is fried if the box is able to connect (for a short while)? Fried = not working? (would be my assumption)
Or could the connection problem be caused if not the right “backup”/original firmeware was flashed back on the box?
In case anyone is experiencing the same problem:
I used the wrong file to flash back the original Toniebox firmware.
Luckily I found another backup - with this one the wifi connects again (if using the original toniebox firmeware).
When flashing again, the problem still exists and I wifi can’t connect.
I will look into this again tomorrow.
Update: I flashed the original firmeware again - and wifi is working (tested with a creative tonie, changed songs on it and box is playing the new ones)
Following some hints from the telegram channel. If you are jonas, then nothing new for you 
The mentioned ip 172.19…:
It sounds like the internal docker ip. Not the right ip.
Is teddycloud reachable from all devices in your network with this ip? What is the internal ip of your computer in your network? ( cmd → ipconfig /all ) Is this the ip shown in your FRITZ!box for the teddycloud server?
Can you also post your docker-compose.yaml ? Check if the ports are not outcommented with #
Hello,
I had the same problem, it was solved by updating the Teddycloud to the newest Version.
Maybe this will help you as well.
I forgot to tell, that I flashed the Toniebox again after updating the Teddycloud.