Unable to to connect Moes IP55 Smart Button to ZHA

[tekhiegit]

The problem

I'm unable to pair a new MOES IP55 Smart Button to ZHA, here is the log that is produced when searching for new device in ZHA...

Received a packet: ZigbeePacket(src=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0F08), src_ep=1, dst=AddrModeAddress(addr_mode=<AddrMode.NWK: 2>, address=0x0000), dst_ep=1, source_route=None, extended_timeout=False, tsn=0, profile_id=260, cluster_id=6, data=Serialized[b'\x18\x03\n\x00\x00\x10\x00'], tx_options=<TransmitOptions.NONE: 0>, radius=29, non_member_radius=0, lqi=45, rssi=None) [0x0F08:1:0x0006] Received ZCL frame: b'\x18\x03\n\x00\x00\x10\x00' [0x0F08:1:0x0006] Decoded ZCL frame header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=0, direction=<Direction.Client_to_Server: 1>, disable_default_response=1, reserved=0, is_cluster=False, is_general=True), tsn=3, command_id=10, *direction=<Direction.Client_to_Server: 1>) [0x0F08:1:0x0006] Decoded ZCL frame: OnOff:Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=<Bool.false: 0>))]) [0x0F08:1:0x0006] Received command 0x0A (TSN 3): Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=<Bool.false: 0>))]) [0x0F08:1:0x0006] Attribute report received: on_off=<Bool.false: 0>

This is the button I'm trying to pair.. https://moeshouse.com/en-gb/products/waterproof-zigbee-scene-switch

I'm using a Sonoff USB stick... ZNP = Texas Instruments Z-Stack ZNP protocol: CC253x, CC26x2, CC13x2 by ZHA

Can anyone help?

What version of Home Assistant Core has the issue?

core-2023.5.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @dmulcahey, @adminiuga, @puddly, 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.

_{^{(message by CodeOwnersMention)}}

---

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

[puddly]

ZHA does not search for devices, instead devices search for your network. If they do not connect, either you have interference issues and the coordinator cannot communicate, the device is not being reset properly, or it cannot communicate for similar reasons.

[MattWestb]

I think the resettle / paring button is on the underside under the battery latch or its one pinhole i have not seen this device in real only the ROK. Then its pared its have some ground functionality but all functions in not implanted then the quirk is not being tested for it.

[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.