However there seems to be no way of finding the toniebox. When connecting the power, the green LED blinks a couple of times and stays green afterwards. The toniebox does appear briefly in my wi-fi devices, but only for a few seconds. I’ve tried this step several times and it produces the same problem over and over again so that I’m stuck at this step now.
I’m running teddycloud on a win10 via docker desktop
I don’t suspect a problem with the Teddycloud here.
Does the Toniebox work in its original state with the original firmware in your WLAN? Do you have a firewall or similar in the network that kicks the Toniebox out for whatever reason? Otherwise, go back and try again. Another question about the WLAN password, special characters or similar in it? If so, maybe use a different one - to test. And the Toniebox can only be used in 2.4GHz WLAN, not 5GHz, if you only have a 5GHz.
Toniebox switched on, Teddycloud running.
Ping to the Toniebox works perfectly.
Teddycloud switched off, Toniebox still on.
Ping to the Toniebox works fine until it switches off automatically (10 minutes)
Teddycloud switched off, Toniebox switched on.
Ping to Toniebox after startup without problems, then aborted.
Tonie (NFC), which does not yet recognize the Toniebox, WLAN connection is established, ping to the Toniebox works properly.
Since Teddycloud is not available, ping aborted.
Could it be that your Toniebox cannot reach the Teddycloud in your Docker instance of your Windows 10 client? Maybe the local Windows firewall is interfering! Can you switch this off to test it?
I’ve set everything up on my raspberry pi now, but the problem remains similar as in that the tonie box does not connect to my wifi. I also cannot reach the teddycloud via other network devices using the same ip that works on the host raspberry.
Now I have to ask in more detail. Teddycloud runs on a Raspi, ok. Is the Raspi connected to the network via WLAN or LAN?
You can access the Teddycloud web interface running on the Raspi with one device. But you can’t access the Teddycloud web interface with another device?
Not being able to access the Teddycloud is one thing, not being able to connect the Toniebox to the WLAN is another.
What does your network basically look like? Otherwise you could start with the basics, restart the router… can’t do any harm
In the first post I described my setup from a win10 PC. The raspberry pi is another device in my network and given that it should theoretically also be able to host the teddycloud, I’m giving that one a shot. Sorry for the confusion!
The raspi is connected via LAN → switch → router and so is the win10 PC fwiw. I have restarted all devices that would have anything to do with the network, but again, to no avail.
On the raspi, basically I can complete all the steps until flashing the ESP32 and then again, the tonie box just doesn’t appear. If I monitor my wifi access point as well as my router, I can see that the MAC Address of the tonie box does appear briefly (~30 sec) only to disappear again. The LED goes from blinking green to solid green and putting a tony on it, produces the ‘ameise’ error.
I’ve managed to set it up finally. The issue was the docker install as I didn’t use the DockerFile from the Revvox github and just winged it on the raspi. After re-installing everything with the correct docker file, I was able to set up the teddycloud on the raspi and also able to access the cloud via other network devices. This also lead to the tonie box connecting successfully to the cloud.
Thanks for the help and apologies if I wasn’t able to clearly state what the problem was.
Thanks, appreciate you helping out (as far as it was possible).
In the end, if you’re completely new to this, setting up docker is seemingly the bigger challenge than going through the steps with the teddycloud. Once docker is configured properly, I think there isn’t too much that can go wrong even if the whole UART reading/flashing feels a bit funky.
I’ve used the mydealz tutorial, but there, they are not elaborating on the docker part and also they’re setting it up via proxmox. Otherwise I’ve just followed the tutorial for all steps after the docker installation and it was generally smooth sailing.
