puddly

@bdraco ah, good point. It's already registered but there's no info about what keys are allowed, nor any public references to devices actually using it 😅. I'll see what I...

Marking as draft until I hear back from a few people. If there's an existing and active registration we'll have to rename this. If not, we'll continue with this name.

`_zigbee-gateway`'s format is undocumented and I'm unable to get any information about it. I'm moving to `_zigbee-coordinator` to avoid issues down the line.

Looks like CI is having some issues right now. Thanks for the review, @abmantis. I think I've addressed your review comments.

The device is likely reading from the `Time` cluster. I recently fixed a bug with it where the local time zone was not used but it's possible the value isn't...

I believe this is a device bug: ```python 2024-09-14 12:09:29.790 DEBUG (MainThread) [zigpy.zcl] [0x5481:1:0x000a] Decoded ZCL frame: Time:Read_Attributes(attribute_ids=[0]) 2024-09-14 12:09:29.791 DEBUG (MainThread) [zigpy.zcl] [0x5481:1:0x000a] Sending reply: Read_Attributes_rsp(status_records=[ReadAttributeRecord(attrid=0, status=, value=TypeValue(type=UTCTime, value=779656169))])...

I don't think it's a problem with encryption, it's a problem with the Python tar archive module.

We could try out 7z, which I think ticks all of the boxes (https://github.com/miurahr/py7zr). Or roll our own 🤷

Can we keep this open? This is still unresolved as far as I can tell.

Please attach both pieces of diagnostics information, I showed in the screenshot where you can download it: https://github.com/home-assistant/core/issues/124516#issuecomment-2364398602