Bosch TRV II will not complete interview on ZHA with Sonoff dongle E

[RonnieLast]

The problem

Cannot complete the Zigbee interview process on three Bosch TRV II devices while using ZHA and the Sonoff dongle-E.

I have two brand new Bosch TRV II devices (supports standard Zigbee) and one Bosch TRV II [+M] device (supports zigbee or mater). HA Core is 2024.10.0 and the Sonoff ZBDongle-E running 7.4.3 of the coordinator firmware. If I try to integrate the Bosch TRV's then the interview process will not complete and the devices remain unpaired. The devices will not be detected on any subsequent device-add session unless I restart the ZHA integration from HA and then retry the pair operation again. Even after this the interview process will not complete and the TRV's remain excluded from HA.

What version of Home Assistant Core has the issue?

core-2024.10.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

zha

Link to integration documentation on our website

No response

Diagnostics information

config_entry-zha-01J9A3CNB4ASR4R7CQZ8S953AM.json home-assistant_zha_2024-10-14T14-44-12.125Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Two logs attached - debug output from ZHA during the attempted pairing of device with Zigbee EUI-64 of "30:e8:e4:00:00:d3:a1:9d" and the configuration output from ZHA. 
All that my untrained eye sees in the debug output is that the device appears to restart the initiation process multiple times:

2024-10-14 15:38:13.725 INFO (MainThread) [zigpy.application] New device 0xe304 (30:e8:e4:00:00:d3:a1:9d) joined the network

Additional information

I have installed the Sonoff on a USB-2 port and is connected via an extension cable away from the server. I do not believe that there are noise issues on the Zigbee channel which may be causing these issues and the error counters look relatively clean to me.

Can you please validate whether this is a ZHA issue or whether the Sonoff or Bosch could be to blame? I would replace the Sonoff with a Home Assistant ZBT-1 dongle, except there are none currently in stock that I can see. (Any ETA on when that device might return to stock?)

[home-assistant[bot]]

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zha documentation zha source _{^{(message by IssueLinks)}}

[puddly]

Are you joining the device with its install code (should be a QR code somewhere on the device/box)?

https://www.home-assistant.io/integrations/zha/#action-zhapermit

[RonnieLast]

Hi, no this is a join initiated within HA from the add option on the dongle info page: Other Zigbee devices can be added via this method and complete interview without issue. The Bosch TRV's do also have a 3D/QR barcode and an install code printed on the back cover so I tested the zha.permit method:

action: zha.permit data: duration: 60 qr_code: >- RB01SG0D8310182648008000000000000000000018FC2600000EE21BDLK0D87650F31900FEF8A6ADB5D5A0C97FCA17A

And now I have the TRV paired! So did I miss something in the documentation where the 'normal' join process no longer works, because I have a Sonoff device here also with a QR barcode, and it joined using the normal method?

[puddly]

I think this is basically the only device that refuses to join without the QR code.

When it joined before, was ZHA able to read any information about it? Or did it just join as an unknown device and then leave?

[RonnieLast]

No, it never joined before, just appeared as unknown device and then disappeared. ZHA had to be restarted before it would be detected again as unknown and the loop repeated.

[RonnieLast]

I'm good to close if this is an oddity with the Bosch devices and there is no defect in ZHA... are we able to confirm that?

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.