puddly
puddly
I think you downloaded the HTML files instead of the actual OTA images: ```Python # Your file In [11]: (168430090).to_bytes(4, 'little') Out[11]: b'\n\n\n\n' # GitHub HTML In [12]: requests.get('https://github.com/Koenkk/zigbee-OTA/blob/master/images/Xiaomi/20201218113852_lumi.relay.c2acn01_0.0.0_0046_20201216_6BB0FD.ota').content[:4] Out[12]:...
The frames you received seem like they are being decoded properly by bellows: ``` 76 26b1a96b2a164fa6904b2daa546d499d4e27a5edce67 03ff 7e control byte = 76 = 01001100 - bit 7: type = DATA...
Should have been fixed a few months ago.
If `self._api` is `None`, your device is not connected.
I've ordered a scene controller and will give this a try when I have some free time.
I believe I've addressed all of the issues you mentioned. Is there any `pre-commit`-like hook for the frontend that auto-formats everything properly, like there is for HA Core?
> ZHA or home assistant core made this worse because I have multiple dongles and I switched to another and changed the config entry Did you do a network backup/restore?...
The dongle lockup issue is something I can possibly take a look at in zigpy-znp. Can you make NVRAM backups of both a working and a broken dongle and email...
`bellows` is the wrong command. Take a look at the documentation: https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md#backup-and-restore
I see no differences in the NVRAM between the two. Both produce nearly identical network backups when written to my stick, with the only two differences being: 1. The network...