izivkov
commented
5 months ago I'll look into it. It seems like the time is getting set twice, the first time at 5:25 and the second time at 6:37. What is the time on the pi?
Open bodydisplaynone opened 5 months ago
izivkov
commented
5 months ago I'll look into it. It seems like the time is getting set twice, the first time at 5:25 and the second time at 6:37. What is the time on the pi?
bodydisplaynone
commented
5 months ago Time seems to be correct according to multiple watches and devices around the house.
izivkov
commented
5 months ago Please update the code from GitHub again. I found one problem, but may not have fixed all issues. The problem might be that the watch does not like to update the time very frequently, and it just fails silently. If this is the case, wait for a while between updates. Anyway, give it a try and see what happens.
bodydisplaynone
commented
5 months ago I just tested it and while it failed for the first time, it passed the next. I also tried to break things again and updated the time twice within 30 seconds and it worked fine. 10 minutes later before I left home I updated it again successfully.
I'll keep running the server and do manual/automatic updates in the next few days and post the results.
izivkov
commented
5 months ago Ok, thanks for finding the issue. You may want to create some startup scripts to restart the server upon reboot. You also don't need all the files in the repository, just Python files. I have a script to put all the necessary files into the dust directory. If you came up we with something useful, feel free to contribute back to the project by creating a merge request.
Anyway, let me know how this is working for you as a server for your watches.
On Wed, Jun 19, 2024, 2:08 AM bodydisplaynone @.***> wrote:
I just tested it and while it failed for the first time, it passed the next. I also tried to break things again and updated the time twice within 30 seconds and it worked fine. 10 minutes later before I left home I updated it again successfully.
I'll keep running the server and do manual/automatic updates in the next few days and post the results.
— Reply to this email directly, view it on GitHub https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2177823220, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7M37RKNIRBYZ7Q66MT323ZIEN4HAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZXHAZDGMRSGA . You are receiving this because you commented.Message ID: @.***>
bodydisplaynone
commented
5 months ago I am using a screen instance to keep the server running when I detach from ssh. In the past few days I have observed the following issues:
For example, today I tried to sync the watch after not being able to do so in the past 3 days. I connected to ssh, last message was 10: Button pressed but no matter what I did the watch did not connect. I restarted the server, pressed the button and the watch connected, received the data (OK) but the RCVD does not show.
izivkov
commented
5 months ago Thanks for reporting. I'll look into these. I'm not normally using the this server, so you are tests are invaluable.
On Sun, Jun 23, 2024, 12:42 PM bodydisplaynone @.***> wrote:
I am using a screen instance to keep the server running when I detach from ssh. In the past few days I have observed the following issues:
- Sometimes the watch connects and syncs it even says OK, but the RCVD symbol does not display after the transaction is completed.
- Sometimes after connecting I receive the "10: Button pressed" log in the console and then nothing happens after. Usually, when this occurs, the watch never reconnects and I have to restart the server completely.
— Reply to this email directly, view it on GitHub https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2185148429, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7M37SIR5CFUDRPXBKIJ6LZI33IXAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBVGE2DQNBSHE . You are receiving this because you commented.Message ID: @.***>
izivkov
commented
5 months ago Did you get any further?
I did some tests, and this could happen if you press the watch button before the watch has disconnected. For example, press the lower-right button and while the time is being set (check the logs), press the same button again. The logs will stop after saying something like:
('write: XXX',)The reason this happens is that the PC sent something to the watch (write...), the watch got a button press, and abandoned sending back the data to the PC.
Now, usually, the watch's button is disabled while it is processing, so I will have to look into it. However, in normal operation, automatically updating the time, this should not happen.
Let me know what you think.
bodydisplaynone
commented
5 months ago I did not experiment too much in the last few days, however, I still not get the RCVD symbol after disconnecting.
What usually happens is I press the button and wait, the watch eventually says OK but no RCVD symbol and it also removes if it had one from before (e.g. phone app sync).
Regarding the write error, I never pressed the button again while the logs were running in the terminal. What usually happens for example that I get a random thought to sync, press the button, the terminal says "10: Button pressed" and nothing follows after. The server becomes unresponsive after that and I have to restart it in order to work again.
Maybe this can be a disconnection issue where the watch receives the time but does not disconnect, hence the missing RCVD symbol and the write:10 error the next time I press it while I'm home?
izivkov
commented
5 months ago Ok, interesting, I got the RCVD. Does the time actually adjust? Like if you change the time manually to some random value, and then use app, is it set to the correct time?
That watch are you using?
On Mon, Jul 1, 2024, 9:59 AM bodydisplaynone @.***> wrote:
I did not experiment too much in the last few days, however, I still not get the RCVD symbol after disconnecting.
What usually happens is I press the button and wait, the watch eventually says OK but no RCVD symbol and it also removes if it had one from before (e.g. phone app sync).
Regarding the write error, I never pressed the button again while the logs were running in the terminal. What usually happens for example that I get a random thought to sync, press the button, the terminal says "10: Button pressed" and nothing follows after. The server becomes unresponsive after that and I have to restart it in order to work again.
Maybe this can be a disconnection issue where the watch receives the time but does not disconnect, hence the missing RCVD symbol and the write:10 error the next time I press it while I'm home?
— Reply to this email directly, view it on GitHub https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200232723, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7M37TJTSNP5GHZB34HSX3ZKFOCNAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQGIZTENZSGM . You are receiving this because you commented.Message ID: @.***>
izivkov
commented
5 months ago Also, do you get the RCVD when using the Android app?
On Mon, Jul 1, 2024, 10:22 AM Ivo Zivkov @.***> wrote:
Ok, interesting, I got the RCVD. Does the time actually adjust? Like if you change the time manually to some random value, and then use app, is it set to the correct time?
That watch are you using?
On Mon, Jul 1, 2024, 9:59 AM bodydisplaynone @.***> wrote:
I did not experiment too much in the last few days, however, I still not get the RCVD symbol after disconnecting.
What usually happens is I press the button and wait, the watch eventually says OK but no RCVD symbol and it also removes if it had one from before (e.g. phone app sync).
Regarding the write error, I never pressed the button again while the logs were running in the terminal. What usually happens for example that I get a random thought to sync, press the button, the terminal says "10: Button pressed" and nothing follows after. The server becomes unresponsive after that and I have to restart it in order to work again.
Maybe this can be a disconnection issue where the watch receives the time but does not disconnect, hence the missing RCVD symbol and the write:10 error the next time I press it while I'm home?
— Reply to this email directly, view it on GitHub https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200232723, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7M37TJTSNP5GHZB34HSX3ZKFOCNAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQGIZTENZSGM . You are receiving this because you commented.Message ID: @.***>
bodydisplaynone
commented
4 months ago Android app works fine. There are some occasions where the watch does not connect for some reason and I have to press forget or restart the app but it sets the time properly and reminders/alarms etc. seems to work too. RCVD also shows up on the watch after OK.
The only watch I own is the GW-B5600.
I attached a screenshot of the latest hang of the python server. In the past few days I wasn't able to sync at all with it, so I opened the terminal and saw the write: 10 again, as usual, the last line of the code before everything breaks. I interrupted the server, restarted it, and literally after starting it the receive button (single press and wait) caused another write: 10. Nothing happens after that and the server just hangs completely until I restart it.
Which I did, then pressed the receive button (once), logs are filling, got the message OK but no RCVD. Also, the watch did not set the time correctly. I added a few extra minutes manually before to test it but even if it says OK the time remains incorrect after syncing.
So in my experience, I either get a write: 10 at a random point and the server just hangs, or, if it connects, I get OK but no RCVD and the time also remains uncorrect.
On Mon, 1 Jul 2024, 4:31 pm Ivo Zivkov, @.***> wrote:
Also, do you get the RCVD when using the Android app?
On Mon, Jul 1, 2024, 10:22 AM Ivo Zivkov @.***> wrote:
Ok, interesting, I got the RCVD. Does the time actually adjust? Like if you change the time manually to some random value, and then use app, is it set to the correct time?
That watch are you using?
On Mon, Jul 1, 2024, 9:59 AM bodydisplaynone @.***> wrote:
I did not experiment too much in the last few days, however, I still not get the RCVD symbol after disconnecting.
What usually happens is I press the button and wait, the watch eventually says OK but no RCVD symbol and it also removes if it had one from before (e.g. phone app sync).
Regarding the write error, I never pressed the button again while the logs were running in the terminal. What usually happens for example that I get a random thought to sync, press the button, the terminal says "10: Button pressed" and nothing follows after. The server becomes unresponsive after that and I have to restart it in order to work again.
Maybe this can be a disconnection issue where the watch receives the time but does not disconnect, hence the missing RCVD symbol and the write:10 error the next time I press it while I'm home?
— Reply to this email directly, view it on GitHub < https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200232723>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA7M37TJTSNP5GHZB34HSX3ZKFOCNAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQGIZTENZSGM>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200324639, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFM4KFH2OM36SEB4524JC5TZKFR3RAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQGMZDINRTHE . You are receiving this because you authored the thread.Message ID: @.***>
izivkov
commented
4 months ago OK, thanks for the feedback. I just updated the code to address the hanging issue (write: 10). It works for me now, I ran it for a couple of days with no problem. Please let me know if the latest code fixes this for you.
I am not sure why RCVD is not showing on your watch. If you get OK on the watch, RCVD should display as well.
Anyway, get the latest code and see if the hanging issue still occurs for you. I will look into possible reasons for RCVD not working.
Regards, Ivo
On Thu, Jul 4, 2024 at 5:18 PM bodydisplaynone @.***> wrote:
Android app works fine. There are some occasions where the watch does not connect for some reason and I have to press forget or restart the app but it sets the time properly and reminders/alarms etc. seems to work too. RCVD also shows up on the watch after OK.
The only watch I own is the GW-B5600.
I attached a screenshot of the latest hang of the python server. In the past few days I wasn't able to sync at all with it, so I opened the terminal and saw the write: 10 again, as usual, the last line of the code before everything breaks. I interrupted the server, restarted it, and literally after starting it the receive button (single press and wait) caused another write: 10. Nothing happens after that and the server just hangs completely until I restart it.
Which I did, then pressed the receive button (once), logs are filling, got the message OK but no RCVD. Also, the watch did not set the time correctly. I added a few extra minutes manually before to test it but even if it says OK the time remains incorrect after syncing.
So in my experience, I either get a write: 10 at a random point and the server just hangs, or, if it connects, I get OK but no RCVD and the time also remains uncorrect.
On Mon, 1 Jul 2024, 4:31 pm Ivo Zivkov, @.***> wrote:
Also, do you get the RCVD when using the Android app?
On Mon, Jul 1, 2024, 10:22 AM Ivo Zivkov @.***> wrote:
Ok, interesting, I got the RCVD. Does the time actually adjust? Like if you change the time manually to some random value, and then use app, is it set to the correct time?
That watch are you using?
On Mon, Jul 1, 2024, 9:59 AM bodydisplaynone @.***> wrote:
I did not experiment too much in the last few days, however, I still not get the RCVD symbol after disconnecting.
What usually happens is I press the button and wait, the watch eventually says OK but no RCVD symbol and it also removes if it had one from before (e.g. phone app sync).
Regarding the write error, I never pressed the button again while the logs were running in the terminal. What usually happens for example that I get a random thought to sync, press the button, the terminal says "10: Button pressed" and nothing follows after. The server becomes unresponsive after that and I have to restart it in order to work again.
Maybe this can be a disconnection issue where the watch receives the time but does not disconnect, hence the missing RCVD symbol and the write:10 error the next time I press it while I'm home?
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200232723>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200324639>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/AFM4KFH2OM36SEB4524JC5TZKFR3RAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQGMZDINRTHE>
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209571121, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7M37XTWSELCFANLD2SLV3ZKW3ZNAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGU3TCMJSGE . You are receiving this because you commented.Message ID: @.***>
bodydisplaynone
commented
4 months ago Not sure if my watch is the culprit but I get the same behaviour.
I just pulled the changes, started the server, pressed the button, received OK but the time did not update.
I pressed the button again, got write:10 and the server just hangs.
Restarted the server, logs running, watch says OK but no RCVD.
Next try I got a write: 10 again and the server just hangs.
I'll try to reboot the whole raspi and update/upgrade to see if it helps.
On Thu, 4 Jul 2024, 11:31 pm Ivo Zivkov, @.***> wrote:
OK, thanks for the feedback. I just updated the code to address the hanging issue (write: 10). It works for me now, I ran it for a couple of days with no problem. Please let me know if the latest code fixes this for you.
I am not sure why RCVD is not showing on your watch. If you get OK on the watch, RCVD should display as well.
Anyway, get the latest code and see if the hanging issue still occurs for you. I will look into possible reasons for RCVD not working.
Regards, Ivo
On Thu, Jul 4, 2024 at 5:18 PM bodydisplaynone @.***> wrote:
Android app works fine. There are some occasions where the watch does not connect for some reason and I have to press forget or restart the app but it sets the time properly and reminders/alarms etc. seems to work too. RCVD also shows up on the watch after OK.
The only watch I own is the GW-B5600.
I attached a screenshot of the latest hang of the python server. In the past few days I wasn't able to sync at all with it, so I opened the terminal and saw the write: 10 again, as usual, the last line of the code before everything breaks. I interrupted the server, restarted it, and literally after starting it the receive button (single press and wait) caused another write: 10. Nothing happens after that and the server just hangs completely until I restart it.
Which I did, then pressed the receive button (once), logs are filling, got the message OK but no RCVD. Also, the watch did not set the time correctly. I added a few extra minutes manually before to test it but even if it says OK the time remains incorrect after syncing.
So in my experience, I either get a write: 10 at a random point and the server just hangs, or, if it connects, I get OK but no RCVD and the time also remains uncorrect.
On Mon, 1 Jul 2024, 4:31 pm Ivo Zivkov, @.***> wrote:
Also, do you get the RCVD when using the Android app?
On Mon, Jul 1, 2024, 10:22 AM Ivo Zivkov @.***> wrote:
Ok, interesting, I got the RCVD. Does the time actually adjust? Like if you change the time manually to some random value, and then use app, is it set to the correct time?
That watch are you using?
On Mon, Jul 1, 2024, 9:59 AM bodydisplaynone @.***> wrote:
I did not experiment too much in the last few days, however, I still not get the RCVD symbol after disconnecting.
What usually happens is I press the button and wait, the watch eventually says OK but no RCVD symbol and it also removes if it had one from before (e.g. phone app sync).
Regarding the write error, I never pressed the button again while the logs were running in the terminal. What usually happens for example that I get a random thought to sync, press the button, the terminal says "10: Button pressed" and nothing follows after. The server becomes unresponsive after that and I have to restart it in order to work again.
Maybe this can be a disconnection issue where the watch receives the time but does not disconnect, hence the missing RCVD symbol and the write:10 error the next time I press it while I'm home?
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200232723>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200324639>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209571121>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA7M37XTWSELCFANLD2SLV3ZKW3ZNAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGU3TCMJSGE>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209579437, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFM4KFF5PEMCYSK567PW2EDZKW5M3AVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGU3TSNBTG4 . You are receiving this because you authored the thread.Message ID: @.***>
izivkov
commented
4 months ago Ok. The black should unblock after 5 seconds now.
On Thu, Jul 4, 2024, 6:01 PM bodydisplaynone @.***> wrote:
Not sure if my watch is the culprit but I get the same behaviour.
I just pulled the changes, started the server, pressed the button, received OK but the time did not update.
I pressed the button again, got write:10 and the server just hangs.
Restarted the server, logs running, watch says OK but no RCVD.
Next try I got a write: 10 again and the server just hangs.
I'll try to reboot the whole raspi and update/upgrade to see if it helps.
On Thu, 4 Jul 2024, 11:31 pm Ivo Zivkov, @.***> wrote:
OK, thanks for the feedback. I just updated the code to address the hanging issue (write: 10). It works for me now, I ran it for a couple of days with no problem. Please let me know if the latest code fixes this for you.
I am not sure why RCVD is not showing on your watch. If you get OK on the watch, RCVD should display as well.
Anyway, get the latest code and see if the hanging issue still occurs for you. I will look into possible reasons for RCVD not working.
Regards, Ivo
On Thu, Jul 4, 2024 at 5:18 PM bodydisplaynone @.***> wrote:
Android app works fine. There are some occasions where the watch does not connect for some reason and I have to press forget or restart the app but it sets the time properly and reminders/alarms etc. seems to work too. RCVD also shows up on the watch after OK.
The only watch I own is the GW-B5600.
I attached a screenshot of the latest hang of the python server. In the past few days I wasn't able to sync at all with it, so I opened the terminal and saw the write: 10 again, as usual, the last line of the code before everything breaks. I interrupted the server, restarted it, and literally after starting it the receive button (single press and wait) caused another write: 10. Nothing happens after that and the server just hangs completely until I restart it.
Which I did, then pressed the receive button (once), logs are filling, got the message OK but no RCVD. Also, the watch did not set the time correctly. I added a few extra minutes manually before to test it but even if it says OK the time remains incorrect after syncing.
So in my experience, I either get a write: 10 at a random point and the server just hangs, or, if it connects, I get OK but no RCVD and the time also remains uncorrect.
On Mon, 1 Jul 2024, 4:31 pm Ivo Zivkov, @.***> wrote:
Also, do you get the RCVD when using the Android app?
On Mon, Jul 1, 2024, 10:22 AM Ivo Zivkov @.***> wrote:
Ok, interesting, I got the RCVD. Does the time actually adjust? Like if you change the time manually to some random value, and then use app, is it set to the correct time?
That watch are you using?
On Mon, Jul 1, 2024, 9:59 AM bodydisplaynone @.***> wrote:
I did not experiment too much in the last few days, however, I still not get the RCVD symbol after disconnecting.
What usually happens is I press the button and wait, the watch eventually says OK but no RCVD symbol and it also removes if it had one from before (e.g. phone app sync).
Regarding the write error, I never pressed the button again while the logs were running in the terminal. What usually happens for example that I get a random thought to sync, press the button, the terminal says "10: Button pressed" and nothing follows after. The server becomes unresponsive after that and I have to restart it in order to work again.
Maybe this can be a disconnection issue where the watch receives the time but does not disconnect, hence the missing RCVD symbol and the write:10 error the next time I press it while I'm home?
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200232723>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200324639>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209571121>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209579437>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/AFM4KFF5PEMCYSK567PW2EDZKW5M3AVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGU3TSNBTG4>
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209596044, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7M37VA2JG62ON6ATAOGE3ZKXA4VAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGU4TMMBUGQ . You are receiving this because you commented.Message ID: @.***>
bodydisplaynone
commented
4 months ago I had the chance in the morning to give a few tries before leaving for work.
All updates/upgrades were done on the system and after a reboot, the write: 10 error seems to be gone. I did 3 attempts, the watch connected and disconnected successfully after each button press.
However, if there is a time mismatch, the watch still does not update nor I get the RCVD symbol. I checked the logs and the server logs and sets the time (Time set at ... [correct time]...) but the watch does not adjust accordingly.
Ivo Zivkov @.***> ezt írta (időpont: 2024. júl. 5., P, 0:14):
Ok. The black should unblock after 5 seconds now.
On Thu, Jul 4, 2024, 6:01 PM bodydisplaynone @.***> wrote:
Not sure if my watch is the culprit but I get the same behaviour.
I just pulled the changes, started the server, pressed the button, received OK but the time did not update.
I pressed the button again, got write:10 and the server just hangs.
Restarted the server, logs running, watch says OK but no RCVD.
Next try I got a write: 10 again and the server just hangs.
I'll try to reboot the whole raspi and update/upgrade to see if it helps.
On Thu, 4 Jul 2024, 11:31 pm Ivo Zivkov, @.***> wrote:
OK, thanks for the feedback. I just updated the code to address the hanging issue (write: 10). It works for me now, I ran it for a couple of days with no problem. Please let me know if the latest code fixes this for you.
I am not sure why RCVD is not showing on your watch. If you get OK on the watch, RCVD should display as well.
Anyway, get the latest code and see if the hanging issue still occurs for you. I will look into possible reasons for RCVD not working.
Regards, Ivo
On Thu, Jul 4, 2024 at 5:18 PM bodydisplaynone @.***> wrote:
Android app works fine. There are some occasions where the watch does not connect for some reason and I have to press forget or restart the app but it sets the time properly and reminders/alarms etc. seems to work too. RCVD also shows up on the watch after OK.
The only watch I own is the GW-B5600.
I attached a screenshot of the latest hang of the python server. In the past few days I wasn't able to sync at all with it, so I opened the terminal and saw the write: 10 again, as usual, the last line of the code before everything breaks. I interrupted the server, restarted it, and literally after starting it the receive button (single press and wait) caused another write: 10. Nothing happens after that and the server just hangs completely until I restart it.
Which I did, then pressed the receive button (once), logs are filling, got the message OK but no RCVD. Also, the watch did not set the time correctly. I added a few extra minutes manually before to test it but even if it says OK the time remains incorrect after syncing.
So in my experience, I either get a write: 10 at a random point and the server just hangs, or, if it connects, I get OK but no RCVD and the time also remains uncorrect.
On Mon, 1 Jul 2024, 4:31 pm Ivo Zivkov, @.***> wrote:
Also, do you get the RCVD when using the Android app?
On Mon, Jul 1, 2024, 10:22 AM Ivo Zivkov @.***> wrote:
Ok, interesting, I got the RCVD. Does the time actually adjust? Like if you change the time manually to some random value, and then use app, is it set to the correct time?
That watch are you using?
On Mon, Jul 1, 2024, 9:59 AM bodydisplaynone @.***> wrote:
I did not experiment too much in the last few days, however, I still not get the RCVD symbol after disconnecting.
What usually happens is I press the button and wait, the watch eventually says OK but no RCVD symbol and it also removes if it had one from before (e.g. phone app sync).
Regarding the write error, I never pressed the button again while the logs were running in the terminal. What usually happens for example that I get a random thought to sync, press the button, the terminal says "10: Button pressed" and nothing follows after. The server becomes unresponsive after that and I have to restart it in order to work again.
Maybe this can be a disconnection issue where the watch receives the time but does not disconnect, hence the missing RCVD symbol and the write:10 error the next time I press it while I'm home?
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200232723>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200324639>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209571121>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209579437>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209596044>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA7M37VA2JG62ON6ATAOGE3ZKXA4VAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGU4TMMBUGQ>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209603921, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFM4KFENEFYP6HB6JKC5YMDZKXCNNAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGYYDGOJSGE . You are receiving this because you authored the thread.Message ID: @.***>
izivkov
commented
4 months ago Ok, if you could please send me some logs to look at, I might find something unusual.
Thanks
On Fri, Jul 5, 2024, 6:07 AM bodydisplaynone @.***> wrote:
I had the chance in the morning to give a few tries before leaving for work.
All updates/upgrades were done on the system and after a reboot, the write: 10 error seems to be gone. I did 3 attempts, the watch connected and disconnected successfully after each button press.
However, if there is a time mismatch, the watch still does not update nor I get the RCVD symbol. I checked the logs and the server logs and sets the time (Time set at ... [correct time]...) but the watch does not adjust accordingly.
Ivo Zivkov @.***> ezt írta (időpont: 2024. júl. 5., P, 0:14):
Ok. The black should unblock after 5 seconds now.
On Thu, Jul 4, 2024, 6:01 PM bodydisplaynone @.***> wrote:
Not sure if my watch is the culprit but I get the same behaviour.
I just pulled the changes, started the server, pressed the button, received OK but the time did not update.
I pressed the button again, got write:10 and the server just hangs.
Restarted the server, logs running, watch says OK but no RCVD.
Next try I got a write: 10 again and the server just hangs.
I'll try to reboot the whole raspi and update/upgrade to see if it helps.
On Thu, 4 Jul 2024, 11:31 pm Ivo Zivkov, @.***> wrote:
OK, thanks for the feedback. I just updated the code to address the hanging issue (write: 10). It works for me now, I ran it for a couple of days with no problem. Please let me know if the latest code fixes this for you.
I am not sure why RCVD is not showing on your watch. If you get OK on the watch, RCVD should display as well.
Anyway, get the latest code and see if the hanging issue still occurs for you. I will look into possible reasons for RCVD not working.
Regards, Ivo
On Thu, Jul 4, 2024 at 5:18 PM bodydisplaynone @.***> wrote:
Android app works fine. There are some occasions where the watch does not connect for some reason and I have to press forget or restart the app but it sets the time properly and reminders/alarms etc. seems to work too. RCVD also shows up on the watch after OK.
The only watch I own is the GW-B5600.
I attached a screenshot of the latest hang of the python server. In the past few days I wasn't able to sync at all with it, so I opened the terminal and saw the write: 10 again, as usual, the last line of the code before everything breaks. I interrupted the server, restarted it, and literally after starting it the receive button (single press and wait) caused another write: 10. Nothing happens after that and the server just hangs completely until I restart it.
Which I did, then pressed the receive button (once), logs are filling, got the message OK but no RCVD. Also, the watch did not set the time correctly. I added a few extra minutes manually before to test it but even if it says OK the time remains incorrect after syncing.
So in my experience, I either get a write: 10 at a random point and the server just hangs, or, if it connects, I get OK but no RCVD and the time also remains uncorrect.
On Mon, 1 Jul 2024, 4:31 pm Ivo Zivkov, @.***> wrote:
Also, do you get the RCVD when using the Android app?
On Mon, Jul 1, 2024, 10:22 AM Ivo Zivkov @.***> wrote:
Ok, interesting, I got the RCVD. Does the time actually adjust? Like if you change the time manually to some random value, and then use app, is it set to the correct time?
That watch are you using?
On Mon, Jul 1, 2024, 9:59 AM bodydisplaynone @.***> wrote:
I did not experiment too much in the last few days, however, I still not get the RCVD symbol after disconnecting.
What usually happens is I press the button and wait, the watch eventually says OK but no RCVD symbol and it also removes if it had one from before (e.g. phone app sync).
Regarding the write error, I never pressed the button again while the logs were running in the terminal. What usually happens for example that I get a random thought to sync, press the button, the terminal says "10: Button pressed" and nothing follows after. The server becomes unresponsive after that and I have to restart it in order to work again.
Maybe this can be a disconnection issue where the watch receives the time but does not disconnect, hence the missing RCVD symbol and the write:10 error the next time I press it while I'm home?
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200232723>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200324639>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209571121>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209579437>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209596044>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209603921>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/AFM4KFENEFYP6HB6JKC5YMDZKXCNNAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGYYDGOJSGE>
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2210594717, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7M37VDFNWGWJ4KFFKLIV3ZKZV6LAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGU4TINZRG4 . You are receiving this because you commented.Message ID: @.***>
bodydisplaynone
commented
4 months ago Sure, I'll run a few tests during the weekend and send the results!
On Fri, 5 Jul 2024, 2:36 pm Ivo Zivkov, @.***> wrote:
Ok, if you could please send me some logs to look at, I might find something unusual.
Thanks
On Fri, Jul 5, 2024, 6:07 AM bodydisplaynone @.***> wrote:
I had the chance in the morning to give a few tries before leaving for work.
All updates/upgrades were done on the system and after a reboot, the write: 10 error seems to be gone. I did 3 attempts, the watch connected and disconnected successfully after each button press.
However, if there is a time mismatch, the watch still does not update nor I get the RCVD symbol. I checked the logs and the server logs and sets the time (Time set at ... [correct time]...) but the watch does not adjust accordingly.
Ivo Zivkov @.***> ezt írta (időpont: 2024. júl. 5., P, 0:14):
Ok. The black should unblock after 5 seconds now.
On Thu, Jul 4, 2024, 6:01 PM bodydisplaynone @.***> wrote:
Not sure if my watch is the culprit but I get the same behaviour.
I just pulled the changes, started the server, pressed the button, received OK but the time did not update.
I pressed the button again, got write:10 and the server just hangs.
Restarted the server, logs running, watch says OK but no RCVD.
Next try I got a write: 10 again and the server just hangs.
I'll try to reboot the whole raspi and update/upgrade to see if it helps.
On Thu, 4 Jul 2024, 11:31 pm Ivo Zivkov, @.***> wrote:
OK, thanks for the feedback. I just updated the code to address the hanging issue (write: 10). It works for me now, I ran it for a couple of days with no problem. Please let me know if the latest code fixes this for you.
I am not sure why RCVD is not showing on your watch. If you get OK on the watch, RCVD should display as well.
Anyway, get the latest code and see if the hanging issue still occurs for you. I will look into possible reasons for RCVD not working.
Regards, Ivo
On Thu, Jul 4, 2024 at 5:18 PM bodydisplaynone @.***> wrote:
Android app works fine. There are some occasions where the watch does not connect for some reason and I have to press forget or restart the app but it sets the time properly and reminders/alarms etc. seems to work too. RCVD also shows up on the watch after OK.
The only watch I own is the GW-B5600.
I attached a screenshot of the latest hang of the python server. In the past few days I wasn't able to sync at all with it, so I opened the terminal and saw the write: 10 again, as usual, the last line of the code before everything breaks. I interrupted the server, restarted it, and literally after starting it the receive button (single press and wait) caused another write: 10. Nothing happens after that and the server just hangs completely until I restart it.
Which I did, then pressed the receive button (once), logs are filling, got the message OK but no RCVD. Also, the watch did not set the time correctly. I added a few extra minutes manually before to test it but even if it says OK the time remains incorrect after syncing.
So in my experience, I either get a write: 10 at a random point and the server just hangs, or, if it connects, I get OK but no RCVD and the time also remains uncorrect.
On Mon, 1 Jul 2024, 4:31 pm Ivo Zivkov, @.***> wrote:
Also, do you get the RCVD when using the Android app?
On Mon, Jul 1, 2024, 10:22 AM Ivo Zivkov @.***> wrote:
Ok, interesting, I got the RCVD. Does the time actually adjust? Like if you change the time manually to some random value, and then use app, is it set to the correct time?
That watch are you using?
On Mon, Jul 1, 2024, 9:59 AM bodydisplaynone @.***> wrote:
I did not experiment too much in the last few days, however, I still not get the RCVD symbol after disconnecting.
What usually happens is I press the button and wait, the watch eventually says OK but no RCVD symbol and it also removes if it had one from before (e.g. phone app sync).
Regarding the write error, I never pressed the button again while the logs were running in the terminal. What usually happens for example that I get a random thought to sync, press the button, the terminal says "10: Button pressed" and nothing follows after. The server becomes unresponsive after that and I have to restart it in order to work again.
Maybe this can be a disconnection issue where the watch receives the time but does not disconnect, hence the missing RCVD symbol and the write:10 error the next time I press it while I'm home?
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200232723>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200324639>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209571121>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209579437>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209596044>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209603921>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2210594717>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA7M37VDFNWGWJ4KFFKLIV3ZKZV6LAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGU4TINZRG4>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2210802443, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFM4KFFVD6TX3WYIABK65GDZK2HNZAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQHAYDENBUGM . You are receiving this because you authored the thread.Message ID: @.***>
bodydisplaynone
commented
4 months ago Here is the first log I got today morning, let me know if you need a better resolution, this was screened from my phone ssh but I think it's readable.
First few attempts return OK w/o RCVD and no time adjustment is being made, last one is write:10 and the server just froze again. I get no response at all.
On Fri, 5 Jul 2024, 3:36 pm Paksi Jocó, @.***> wrote:
Sure, I'll run a few tests during the weekend and send the results!
On Fri, 5 Jul 2024, 2:36 pm Ivo Zivkov, @.***> wrote:
Ok, if you could please send me some logs to look at, I might find something unusual.
Thanks
On Fri, Jul 5, 2024, 6:07 AM bodydisplaynone @.***> wrote:
I had the chance in the morning to give a few tries before leaving for work.
All updates/upgrades were done on the system and after a reboot, the write: 10 error seems to be gone. I did 3 attempts, the watch connected and disconnected successfully after each button press.
However, if there is a time mismatch, the watch still does not update nor I get the RCVD symbol. I checked the logs and the server logs and sets the time (Time set at ... [correct time]...) but the watch does not adjust accordingly.
Ivo Zivkov @.***> ezt írta (időpont: 2024. júl. 5., P, 0:14):
Ok. The black should unblock after 5 seconds now.
On Thu, Jul 4, 2024, 6:01 PM bodydisplaynone @.***> wrote:
Not sure if my watch is the culprit but I get the same behaviour.
I just pulled the changes, started the server, pressed the button, received OK but the time did not update.
I pressed the button again, got write:10 and the server just hangs.
Restarted the server, logs running, watch says OK but no RCVD.
Next try I got a write: 10 again and the server just hangs.
I'll try to reboot the whole raspi and update/upgrade to see if it helps.
On Thu, 4 Jul 2024, 11:31 pm Ivo Zivkov, @.***> wrote:
OK, thanks for the feedback. I just updated the code to address the hanging issue (write: 10). It works for me now, I ran it for a couple of days with no problem. Please let me know if the latest code fixes this for you.
I am not sure why RCVD is not showing on your watch. If you get OK on the watch, RCVD should display as well.
Anyway, get the latest code and see if the hanging issue still occurs for you. I will look into possible reasons for RCVD not working.
Regards, Ivo
On Thu, Jul 4, 2024 at 5:18 PM bodydisplaynone @.***> wrote:
Android app works fine. There are some occasions where the watch does not connect for some reason and I have to press forget or restart the app but it sets the time properly and reminders/alarms etc. seems to work too. RCVD also shows up on the watch after OK.
The only watch I own is the GW-B5600.
I attached a screenshot of the latest hang of the python server. In the past few days I wasn't able to sync at all with it, so I opened the terminal and saw the write: 10 again, as usual, the last line of the code before everything breaks. I interrupted the server, restarted it, and literally after starting it the receive button (single press and wait) caused another write: 10. Nothing happens after that and the server just hangs completely until I restart it.
Which I did, then pressed the receive button (once), logs are filling, got the message OK but no RCVD. Also, the watch did not set the time correctly. I added a few extra minutes manually before to test it but even if it says OK the time remains incorrect after syncing.
So in my experience, I either get a write: 10 at a random point and the server just hangs, or, if it connects, I get OK but no RCVD and the time also remains uncorrect.
On Mon, 1 Jul 2024, 4:31 pm Ivo Zivkov, @.***> wrote:
Also, do you get the RCVD when using the Android app?
On Mon, Jul 1, 2024, 10:22 AM Ivo Zivkov @.***> wrote:
Ok, interesting, I got the RCVD. Does the time actually adjust? Like if you change the time manually to some random value, and then use app, is it set to the correct time?
That watch are you using?
On Mon, Jul 1, 2024, 9:59 AM bodydisplaynone @.***> wrote:
I did not experiment too much in the last few days, however, I still not get the RCVD symbol after disconnecting.
What usually happens is I press the button and wait, the watch eventually says OK but no RCVD symbol and it also removes if it had one from before (e.g. phone app sync).
Regarding the write error, I never pressed the button again while the logs were running in the terminal. What usually happens for example that I get a random thought to sync, press the button, the terminal says "10: Button pressed" and nothing follows after. The server becomes unresponsive after that and I have to restart it in order to work again.
Maybe this can be a disconnection issue where the watch receives the time but does not disconnect, hence the missing RCVD symbol and the write:10 error the next time I press it while I'm home?
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200232723>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2200324639>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209571121>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209579437>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209596044>,
or unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2209603921>,
or unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2210594717>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA7M37VDFNWGWJ4KFFKLIV3ZKZV6LAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQGU4TINZRG4>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/izivkov/GShockTimeServer/issues/11#issuecomment-2210802443, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFM4KFFVD6TX3WYIABK65GDZK2HNZAVCNFSM6AAAAABJQOHBMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJQHAYDENBUGM . You are receiving this because you authored the thread.Message ID: @.***>
izivkov
commented
4 months ago Sorry, I did not get any screenshots or videos
bodydisplaynone
commented
4 months ago Looks like email reply does not attach files properly to github. Here is the screen again.
I'm having an issue where the watch connects but sets the time incorrectly.
The logger shows the proper time but in my experience the actual time is set back to where the server started, in this example to around 5:25 pm.
https://github.com/izivkov/GShockTimeServer/assets/22660372/d2d5bb27-7b8d-454d-976d-77c1e4fb2b83