puddly

Results 621 comments of puddly

Could you include a debug log of it correctly starting up with the last-working release?

It appears that even in this version, every single packet is failing to send but the error is being ignored: ```python 2022-10-06 22:07:13.621 DEBUG (MainThread) [zigpy_zigate.zigbee.application] APS Data confirm Fail...

Can you try to update your ZiGate's firmware? It looks like the latest version is now 3.21: https://github.com/fairecasoimeme/ZiGate/releases

I don't own a first generation ZiGate so I am not sure. @pipiche38 any ideas? Is this error code expected?

I'm referring to this: ```Python # Sending a `permit(0)` broadcast 2022-10-06 10:15:54.101 DEBUG (MainThread) [zigpy_zigate.zigbee.application] Sending packet ZigbeePacket(src=AddrModeAddress(addr_mode=, address=0x0000), src_ep=0, dst=AddrModeAddress(addr_mode=, address=), dst_ep=0, source_route=None, extended_timeout=False, tsn=10, profile_id=0, cluster_id=, data=Serialized[b'\n\x00\x00'], tx_options=,...

I've downgraded my ZiGate+ to 3.1e (the earliest firmware available for it) and it still works as before. It must be some problem with 3.1d.

All of these messages are logged as `DEBUG` because they are not errors, they're expected to happen for a device that has not finished initialization. This sounds like a Tuya...

I think a few things need to be cleared up before people start destroying their networks unnecessarily. There's **no need** to touch or "clean" `zigbee.db`: the file is checked for...

@Shulyaka If you have time to test, see if zigpy==0.60.1 (https://github.com/zigpy/zigpy/releases/tag/0.60.1) fixes things for you. I think pausing the watchdog during high-load periods will be enough of a stopgap to...

This seems like a bug with the radio library. Perhaps there should be a global concurrency limit for requests? It should be possible to multiplex Zigbee requests along with normal...