Skip to content

ABL-100: set_time failed on GShockAPI.read_write_world_cities #1

@vikoadi

Description

@vikoadi

So I'm trying the GShockTimeServer with my ABL-100, it fails to set the time with the following logs

2025-08-06 22:59:59,792 gshock_api.logger INFO: ('Waiting for Connection...',)
2025-08-06 23:00:03,400 gshock_api.logger INFO: ('✅ Found: CASIO ABL-100WE (D2:CC:D3:1C:1C:23)',)
2025-08-06 23:00:05,380 gshock_api.logger INFO: ('Connected to CASIO ABL-100WE ()',)
2025-08-06 23:00:07,081 gshock_api.logger INFO: ("ErrorIO onReceived: bytearray(b'\\xff\\x81\\x1f')",)
2025-08-06 23:00:16,884 gshock_api.logger ERROR: ('Got error: Timeout occured waiting for response from the watch: ',)
2025-08-06 23:00:17,885 gshock_api.logger INFO: ('Waiting for Connection...',)

only after I commented out the line it can successfully set the time

await self.read_write_world_cities()

2025-08-06 23:32:39,843 gshock_api.logger INFO: ('Waiting for Connection...',)
2025-08-06 23:37:19,514 gshock_api.logger INFO: ('✅ Found: CASIO ABL-100WE (D2:CC:D3:1C:1C:23)',)
2025-08-06 23:37:21,360 gshock_api.logger INFO: ('Connected to CASIO ABL-100WE ()',)
2025-08-06 23:37:23,960 gshock_api.logger INFO: ('Time set at 2025-08-06 23:37:23.959968 on CASIO ABL-100WE',)
2025-08-06 23:37:24,108 gshock_api.logger ERROR: ('Got error: ',)
2025-08-06 23:37:25,109 gshock_api.logger INFO: ('Waiting for Connection...',)

do you need the btsnoop_hci of the original Casio application? I'll fetch it later

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions