puddly

Oh, I guess it is documented in `swra371a.pdf`, including the CRC location. That could have saved me some time. I still can't get my CRC verification code working (the bootloader...

Finally got it: the CRC is computed by skipping the two *pairs* of CRC bytes: https://github.com/zha-ng/zigpy-znp/blob/7e9367480ec3a7602c215c59c27a9bafe604a28b/zigpy_znp/tools/flash_write.py#L21-L56 At this point the implementation in `zigpy_znp.tools.flash_write` is stable-ish. > I do like having...

Are there firmware revisions still affected by this? I think instead of removing the quirk, we can just add a way to stop applying it depending on the device's current...

There's no way to do it at the moment, it will have to be added to zigpy.

The device type is `ON_OFF_LIGHT = 0x0019` so that's right. It also has the following input clusters: ```Python 0 zigpy.zcl.clusters.general.DeviceTemperature, zigpy.zcl.clusters.general.Identify, zigpy.zcl.clusters.general.Groups, zigpy.zcl.clusters.general.Scenes, zigpy.zcl.clusters.general.OnOff, zigpy.zcl.clusters.general.Alarms, zigpy.zcl.clusters.general.Time, zigpy.zcl.clusters.smartenergy.Metering, zigpy.zcl.clusters.homeautomation.ElectricalMeasurement, 64704 ```...

Until there's conclusive evidence that this is a firmware problem, I don't think that's necessary. If you are able to reliably join and use the device with one firmware version...

The lint error with Python 3.7 and 3.8 is unrelated to this PR but can be fixed with `# pylint: disable=too-many-ancestors` or the appropriate pylint config: ```toml [DESIGN] max-parents=9 ```

Agreed. I'm still doing some more testing (specifically preventing IPython lockups when using aiosqlite within an interactive session) but maybe it's better to keep track of *every* observed event loop...

@ldo Installing it with `pip install git+https://github.com/ldo/dbussy` does change the line number to 4811 but the same errors still occur. As for the example scripts, `signal_listener`, `stats_server_ravelled`, `bus_monitor`, and a...

That's interesting. I at least get an `asyncio.base_futures.InvalidStateError: invalid state` error but adding a small delay after the `import numpy` line does fix it. Could it be a timing issue?...