so im using current time, day, year variables that are built-in in thunkable. I send it via BLE to a microcontroller to initialize the RTC. Before actually sending the ‘currentTime string’ you have to login the app and pair the device with the app, THEN when the pairing is done a screen open and i send the string. The string itself is attached in the blockcode of the third screen so you have to pass 3 steps before receiving the ‘currentTime string’. It feels like the currentTime is the one from when the app starts, not the actual time when you open the third screen so there a little delay with the device and the realtime.
What blocks are you using on the third screen? Post a screenshot. What happens if you separately (not related to BLE) assign the current time block to a label when the third screen opens? Does that work as expected?
yes it works great but theres a little delay between the time from thunkable and the real time on my computer si i supposed it was related with how thunkable saves the currentTime
How are you determining that the time is off? Is your computer synced to a time server? Is it different if you do as I suggested above and just display the current time block immediately when the screen opens?
