puddly
puddly
@marcelkous I've annotated a portion of your log: ```python # Device has successfully finished its upgrade to 0x23086631 2024-04-02 12:04:52.587 DEBUG (MainThread) [zigpy.zcl] [0xDD77:1:0x0019] Decoded ZCL frame: Ota:upgrade_end(status=, manufacturer_code=4476, image_type=4354,...
Updates are initiated by the device and the device asks for individual pieces of firmware. It's not driven by ZHA. If an update halts, it is because the device stopped...
Conbee III issues will be fixed when 2024.2.0 is released in a few hours.
@niklasmeng please upload a debug log
Please try b9 once it is out, I think it should address some of your issues.
From your log, it looks like half of your Tuya plugs are going haywire and are sending about 30 requests per second back to the coordinator. The coordinator is trying...
~~The SiLabs flasher dependency will need to be upgraded as well in this PR, as it depends on bellows.~~ Done.
Looks like there is variable binding issue in the most recent zigpy release's listener matching that wasn't covered by unit tests: ``` 2024-02-05 23:22:44.813 DEBUG MainThread zigpy.device:manager.py:203 [0xb79c] OTA image_notify...
Issue resolved, it was just a `Direction` enum I missed in ZHA unit tests that needed to be flipped. In fact, the only use of `Direction` anywhere in ZHA. Tests...
You can just reload the ZHA integration after enabling debug logging: