Thanks - good point about the US states - we don't generally have much of an issue here but it must be a pain if you live near a timezone border.
It does sound a bit like the simplest solution for now might be to send E.setTimeZone(amt, name) instead of just E.setTimeZone(amt) (and maybe set it in the settings too). You could then override that function in the watch face that displays it so you can get updated when there is a change.
do you have a clean way of debugging Gadgetbridge/Bangle interactions?
If you connect your phone via USB then you can get the Android LogCat as part of Android Studio. If you filter it on the text UART it should show you what's going on, so that can be a good step.
You can also go to the app loader in Gadgetbridge and then click on 'remote' and can connect the Web IDE on the desktop to it, but right now the app loader page has to be visible.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Thanks - good point about the US states - we don't generally have much of an issue here but it must be a pain if you live near a timezone border.
It does sound a bit like the simplest solution for now might be to send
E.setTimeZone(amt, name)
instead of justE.setTimeZone(amt)
(and maybe set it in the settings too). You could then override that function in the watch face that displays it so you can get updated when there is a change.If you connect your phone via USB then you can get the Android LogCat as part of Android Studio. If you filter it on the text
UART
it should show you what's going on, so that can be a good step.You can also go to the app loader in Gadgetbridge and then click on 'remote' and can connect the Web IDE on the desktop to it, but right now the app loader page has to be visible.