I got it halfway to work but I think it might be a bug
manualy assign taf file to the id I see in the docker log
# assign content to tonie figurine (adjust tonie_id!)
tonie_id=2c8d1aab500104e0
assign_resp=$(curl -s -w "\nHTTP %{http_code}\n" \
"http://$teddycloud_ip/content/json/set/$tonie_id" \
--data-raw "source=lib://$taf_file")
echo "Assign response: $assign_resp"
after that I see the tonie E0:04:01:50:AB:1A:8D:2C with the taf file assigned to it in teddycloud (was not there before).
Ear press to sync to toniebox
custom tag –> playing file –> working
After that, teddycloud changes the tonie with this ID E0:04:01:50:AB:1A:8D:2C
to FF:FF:FF:FF:AB:1A:8D:2C and I am unable to see the assigned taf file i.e unable to change the taf file via teddycloud.
Custom Tag is still working, even after ear press. Probably because the SD card has the data correctly mapped, but teddycloud somehow got it mixed up with `FF:FF:FF:FF`
INFO |server.c:0432:httpServerRequestCallback| UA=TB/1620325289 SP/34471936 HW/1048932, FW=1620325289, SP=34471936, HW=1048932
INFO |handler_cloud.c:0448:handleCloudContent| >> client requested content for rUID 2c8d1aab500104e0, auth 00000000...
INFO |handler_cloud.c:0314:dumpRuidAuth| Dumped rUID 2c8d1aab500104e0 and auth into content.json
INFO |handler_cloud.c:0684:handleCloudContent| Serve local content from ...
/edit
it seems it is a similar problem to: Custom NFC Tag not working - #11 by justM4D