You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The last_timestamp attribute on the device tracker appears to be being interpreted as already local rather than as UTC. My timezone is +1200, and the last_timestamp attribute is 12 hours behind what it should be.
For example, this evening NZ time at around 2024-04-27 05:43 UTC, in developer tools, for several of my Tiles, we have: last_timestamp: "2024-04-26T17:40:24.824000+00:00"
Note that the date is April 26, which is 12 hours behind the current time.
In the entity dialog attributes list we have: Last timestamp April 27, 2024 at 5:40:24 AM
This appears to be trying to show as a local time (+1200) but is also 12 hours behind.
When I use pytile directly I get the correct last_timestamp in UTC i.e. 2024-04-27 05:40:24.824000
I'm not sure but this may have started around when #106009 was fixed.
What version of Home Assistant Core has the issue?
core-2024.4.4
What was the last working version of Home Assistant Core?
Example line from debug logs showing result.last_tile_state.timestamp of 1714204427284 (about 2024-04-27 07:53 UTC) which showed up as 2024-04-26T19:53:47.284000+00:00 in the last_timestamp attribute:
Hey there @bachya, mind taking a look at this issue as it has been labeled with an integration (tile) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of tile can trigger bot actions by commenting:
@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign tile Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
The problem
The last_timestamp attribute on the device tracker appears to be being interpreted as already local rather than as UTC. My timezone is +1200, and the last_timestamp attribute is 12 hours behind what it should be.
For example, this evening NZ time at around 2024-04-27 05:43 UTC, in developer tools, for several of my Tiles, we have:
last_timestamp: "2024-04-26T17:40:24.824000+00:00"
Note that the date is April 26, which is 12 hours behind the current time.
In the entity dialog attributes list we have:
Last timestamp April 27, 2024 at 5:40:24 AM
This appears to be trying to show as a local time (+1200) but is also 12 hours behind.
When I use pytile directly I get the correct last_timestamp in UTC i.e.
2024-04-27 05:40:24.824000
I'm not sure but this may have started around when #106009 was fixed.
What version of Home Assistant Core has the issue?
core-2024.4.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Tile
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tile/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Example line from debug logs showing result.last_tile_state.timestamp of 1714204427284 (about 2024-04-27 07:53 UTC) which showed up as 2024-04-26T19:53:47.284000+00:00 in the last_timestamp attribute:
2024-04-27 19:58:46.699 DEBUG (MainThread) [pytile] Data received from /tiles/abcdefghabcdefgh: {'version': 1, 'revision': 1, 'timestamp': '2tus': 'ACTIVATED', 'node_type': None, 'activation_timestamp': 1659310781143, 'name': 'Backpack', 'description': None, 'image_url': None, 'product': 'O': 'BACKPACK', 'owner_user_uuid': 'abcdefgh-19d5-4b35-a8e1-abcdefgh', 'thumbnail_image': None, 'group': None, 'tile_uuid': 'c4b5053749cd8fff', 'fion': {'fw10_advertising_interval': None}, 'last_tile_state': {'connectionStateCode': 0, 'ringStateCode': 0, 'uuid': 'abcdefghabcdefgh', 'tile_uuid': 'ent_rssi': 0.0, 'battery_level': 0.0, 'latitude': -41.0000000, 'longitude': 175.0000000, 'altitude': 74.4, 'raw_h_accuracy': 150.0, 'v_accuracy': 1.0,client_uuid': None, 'connection_event_timestamp': 0, 'last_owner_update': 0, 'partner_id': None, 'partner_client_id': None, 'speed_accuracy': 1.5, 'coFalse, 'h_accuracy': 150.0, 'voip_state': 'OFFLINE'}, 'firmware': {'expected_firmware_version': '41.04.10.0', 'expected_firmware_imagename': 'Tile_FW_4800000, 'expected_ppm': None, 'expected_advertising_interval': None, 'security_level': 1, 'expiry_timestamp': 2029564726523, 'expected_tdt_cmd_configcycle_start': '2023-01-09', 'battery_replaced_at': '1703715435579'}, 'battery_status': 'NONE', 'serial_number': None, 'auto_retile': False, 'all_user_780436, 'product_friendly_name': None, 'lf_id': None}}
Additional information
The text was updated successfully, but these errors were encountered: