Btw maybe some additional insights on Tx-Rx, might be helping to some of you :
| Metric | Direction relative to Homey | Meaning |
|---|---|---|
| TX | Homey → Zigbee device | Frames transmitted by the Homey Zigbee coordinator |
| RX | Zigbee device → Homey | Frames received by Homey from devices |
Typical examples:
TX (Homey transmitting)
- On/Off commands
- Level control commands (dimmer)
- Zigbee cluster reads (
ReadAttributes) - Configuration writes (
WriteAttributes) - Binding or reporting configuration
- Network management traffic
RX (Homey receiving)
- Attribute reports (temperature, power, etc.)
- Motion or contact events
- Battery reports
- Device announcements
- Responses to Homey requests
TX Errors (Zigbee)
TX errors represent transmissions attempted by Homey that failed at the Zigbee MAC/network layer.
Typical technical causes:
- No acknowledgement (ACK) received
- Device unreachable
- Weak signal / interference
- Broken routing path
- Route failure
- Coordinator cannot find a valid route to the device
- Routing table expired
- Device asleep
- Common with battery devices
- Transmission happens outside wake window
- Network congestion
- Collision on the 2.4 GHz channel
- Wi-Fi overlap
- Frame retry exhaustion
- Zigbee retries transmission multiple times
- After retry limit → TX error recorded
Practical interpretation
| Pattern | Likely meaning |
|---|---|
| TX increasing normally | Homey sending commands/queries |
| RX increasing normally | Devices reporting data |
| TX errors increasing slowly | Normal mesh retries |
| TX errors increasing rapidly | Routing problem or unreachable device |
