handleCloudContent fails with error Timeout on Raspberry Pi 1 with alpine Docker images

Hi,

thank you for this great project!

I had this Raspberry Pi Model B Rev 2 lying around, so I thought that that could work. I later found out that the architecture is only supported with the alpine docker image, so I used “teddycloud:tc_v0.6.4_alpine“.

Maybe someone has encountered a similar issue before and found the reason.

Description:
First everything seemed to work fine using custom tags and playing the associated TAF-files on the box. Some days later I encountered issues with newer TAF-encodes, where either the “slapping” to skip to the next chapter would not do anything or lead to the LED blinking red. This escalated further and now not even short single chapter TAFs are loaded when placing the Tag on the box. Instead the red LED is blinking and the box is shutting off.
The TAFs that were working in the beginning (so already stored on the Toniebox) still played okay though.

  1. Actions performed:
  • Encode and upload some audiofile(s) to teddycloud.
  • Check with teddycloud-webplayer that the resulting TAF-files are ok.
  • Assign TAF-file to custom tag.
  • Place custom tag on the box.
  1. Expected outcome:
  • The audio should be loaded from the teddycloud and start playing.
  1. Actual outcome:
  • No sound is played.
  • The red LED starts blinking for a few seconds.
  • The toniebox shuts off.
  1. Environment details:
  • Raspberry Pi Model B Rev 2
  • OS: Raspbian GNU/Linux 12 (bookworm)
  • Docker version: Docker version 28.5.0, build 887030f
  • TeddyCloud version: teddycloud:tc_v0.6.4_alpine
  • TeddyCloud alternate version with same issue (not tested for flashing the box, only encoding and serving): teddycloud:arch_develop_linux-arm-v6_alpine
  1. Logs:

INFO |server.c:0432:httpServerRequestCallback| UA=toniebox-esp32-eu/v5.233.0, ESPFW=eu/v5.233.0
INFO |handler_cloud.c:0448:handleCloudContent| >> client requested content for rUID “abcdef”, auth 00000000…
INFO |handler_cloud.c:0684:handleCloudContent| Serve local content from /teddycloud/data/library/song.taf
INFO |handler_api.c:2720:handleApiContentJsonSet| Updated content json of /teddycloud/data/content/default/“abcdef”
ERROR|handler_cloud.c:0698:handleCloudContent| >> file /teddycloud/data/library/song.taf not available or not send, error=Timeout [220]…
INFO |server.c:0961:server_init| 3 open HTTPS API connections
INFO |server.c:0961:server_init| 4 open HTTPS API connections
INFO |server.c:0432:httpServerRequestCallback| UA=toniebox-esp32-eu/v5.233.0, ESPFW=eu/v5.233.0
INFO |handler_cloud.c:0092:handleCloudOTA| >> OTA-Request for 5 with timestamp 1669853893 (2022-12-01 00:18:13)
INFO |handler_cloud.c:0184:handleCloudOTA| >> Replaced OTA query cv=1669853893 with new OTA query cv=1
INFO |handler_cloud.c:0234:handleCloudOTA| >> No OTA (newer) found for 5
INFO |server.c:0432:httpServerRequestCallback| UA=toniebox-esp32-eu/v5.233.0, ESPFW=eu/v5.233.0
INFO |handler_cloud.c:0092:handleCloudOTA| >> OTA-Request for 2 with timestamp 1 (1970-01-01 00:00:01)
INFO |handler_cloud.c:0184:handleCloudOTA| >> Replaced OTA query cv=1 with new OTA query cv=1
INFO |handler_cloud.c:0234:handleCloudOTA| >> No OTA (newer) found for 2
WARN |handler_cloud.c:0237:handleCloudOTA| >> Box tried to enforce firmware delivery, but nothing here to serve!
INFO |server.c:0432:httpServerRequestCallback| UA=toniebox-esp32-eu/v5.233.0, ESPFW=eu/v5.233.0
INFO |handler_cloud.c:0092:handleCloudOTA| >> OTA-Request for 6 with timestamp 1534781997 (2018-08-20 16:19:57)
INFO |handler_cloud.c:0184:handleCloudOTA| >> Replaced OTA query cv=1534781997 with new OTA query cv=1
INFO |handler_cloud.c:0234:handleCloudOTA| >> No OTA (newer) found for 6
INFO |server.c:0432:httpServerRequestCallback| UA=toniebox-esp32-eu/v5.233.0, ESPFW=eu/v5.233.0
INFO |handler_cloud.c:0092:handleCloudOTA| >> OTA-Request for 3 with timestamp 1715951512 (2024-05-17 13:11:52)
INFO |handler_cloud.c:0184:handleCloudOTA| >> Replaced OTA query cv=1715951512 with new OTA query cv=1
INFO |handler_cloud.c:0234:handleCloudOTA| >> No OTA (newer) found for 3
WARN |mutex_manager.c:0153:mutex_manager_check| Mutex 7 locked for 330
INFO |server.c:0432:httpServerRequestCallback| UA=toniebox-esp32-eu/v5.233.0, ESPFW=eu/v5.233.0
INFO |handler_cloud.c:0817:handleCloudFreshnessCheck| Content (448 of 448)
INFO |handler_cloud.c:0825:handleCloudFreshnessCheck| Found 28 tonies:
INFO |handler_cloud.c:0885:handleCloudFreshnessCheck| uid: E00403500EEA3256, nocloud: 0, live: 0, updated: 0, audioid: 18E957B0 (2025-10-10 19:00:00, custom)
ERROR|mutex_manager.c:0161:mutex_manager_check| Mutex 7 locked for 1085
WARN |mutex_manager.c:0123:mutex_unlock| <mutex 7 had a warning
ERROR|mutex_manager.c:0128:mutex_unlock| <mutex 7 had an error

Best regards!

Also, just to mention it: I did not receive a confirmation mail within some hours after registering for this forum, which is why I used Github to login instead.

It seems that increasing the (newly added in the develop version?) server connection timeout option to 5000 ms has fixed the issue!

Is there any harm in having such a long timeout?

You’’ll have to reflash the box, as it was either not set up before flashing or you did a factory reset after flashing. Otherwise you’ll have some other problems, too.

Box tried to enforce firmware delivery, but nothing here to serve!

1 Like

Ok, thanks. No other reason for that message? I set it up by creating a tonies-account because I could not find a way to get it to connect to Wifi without that. I was sure it had the latest firmware before flashing.

No factory reset has been done.

I did change the Wifi after flashing by holding both buttons for a few seconds, connecting to its Wifi etc.

But I guess that does not count as a factory reset.

Factory reset is turn it upside down with connected power and then press both

Yes, so it must be that the box was not set up correctly before flashing?

How will I know that it is, if I decide to flash it back and forth again? Because, if I remember correctly, the tonies-website said that the firmware was updated in the process of setting up the Wifi. If that is not sufficient, what am I missing?

If it plays a Tonie after you connected it to tonies, then the update should be done.

1 Like

Thanks!
It plays uploaded audio with the “Kreativ-Tonie” fine, so I hope it will continue to work without re-flashing.