home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.62k stars 30.38k forks source link

problem with Aqara Wireless Remote Switch H1 Double Rocker #122689

Open Tobbe8000 opened 2 months ago

Tobbe8000 commented 2 months ago

The problem

hi every time i restart home assistant it loses contact with this remote control.so then i have to pair it again and then it works again until i restart..you can excuse me if there is something wrong in this report is my first wrong report I am making.

What version of Home Assistant Core has the issue?

core-2024.7.3

What was the last working version of Home Assistant Core?

core-2024.7.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zigbee Home Automation

Link to integration documentation on our website

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

Diagnostics information

Example YAML snippet


### Anything in the logs that might be useful for us?

```txt
2024-07-24 17:17:09.375 ERROR (MainThread) [homeassistant.components.automation] Automation with alias 'Gardin Altan Aqara Dubbel Knapp Vägg' failed to setup triggers and has been disabled: device does not have trigger ('remote_button_short_press', 'right')
2024-07-24 17:17:09.377 ERROR (MainThread) [homeassistant.components.automation] Automation with alias 'Gardin Framsidan Vardagsrum Aqara Dubbel Knapp Vägg ' failed to setup triggers and has been disabled: device does not have trigger ('remote_button_short_press', 'left')

Additional information

No response

home-assistant[bot] commented 2 months ago

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)

Tobbe8000 commented 2 months ago

Löste det automatiskt

returnofthem commented 2 months ago

Hey @Tobbe8000 - how did you solve this? I have the exact same problem.

Tobbe8000 commented 2 months ago

hi, yes, my button works now, but unfortunately I don't know what was wrong when it suddenly started working again and has been running for a day.

Tobbe8000 commented 2 months ago

hi, yes, my button works now, but unfortunately I don't know what was wrong when it suddenly started working again and has been running for a day.

Mvh Tobias Ström Liljengård


Från: returnofthem @.> Skickat: den 28 juli 2024 22:55 Till: home-assistant/core @.> Kopia: Tobbe8000 @.>; Mention @.> Ämne: Re: [home-assistant/core] problem with Aqara Wireless Remote Switch H1 Double Rocker (Issue #122689)

Hey @Tobbe8000https://github.com/Tobbe8000 - how did you solve this? I have the exact same problem.

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/122689#issuecomment-2254641339, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A657YAJUGNZLK346JU3ZVSLZOVLEVAVCNFSM6AAAAABLRURRCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGY2DCMZTHE. You are receiving this because you were mentioned.Message ID: @.***>

returnofthem commented 2 months ago

Ah ok, that's good news for you but not for me!

In case it helps the maintainers, here are my details. My problem is identical - the switch never comes back after a power loss, reboot, or event just a restart of ZHA.

Versions Core: 2024.7.3 Supervisor: 2024.06.2 Operating System: 12.4 Frontend: 20240710.0

Last known good N/A, I'm a new Home Assistant user

Installation Type HAOS on Raspberry Pi 4b, 4GB

Integration causing the issue Zigbee Home Automation

Zigbee Zongle SONOFF Zigbee 3.0 USB Dongle Plus (E-version)

Diagnostics Log of ZHA restarting and losing the switch home-assistant_zha_2024-07-28T22-36-01.103Z.log

Device immediately after pairing

Device after ZHA restart or system reboot

Signature

{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": "0x0104",
      "device_type": "0x0103",
      "input_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x0012",
        "0xfcc0"
      ],
      "output_clusters": [
        "0x0003",
        "0x0006"
      ]
    },
    "2": {
      "profile_id": "0x0104",
      "device_type": "0x0103",
      "input_clusters": [
        "0x0003",
        "0x0012"
      ],
      "output_clusters": [
        "0x0003",
        "0x0006"
      ]
    },
    "3": {
      "profile_id": "0x0104",
      "device_type": "0x0103",
      "input_clusters": [
        "0x0003",
        "0x0012"
      ],
      "output_clusters": [
        "0x0003",
        "0x0006"
      ]
    }
  },
  "manufacturer": "LUMI",
  "model": "lumi.remote.b28ac1",
  "class": "zhaquirks.xiaomi.aqara.remote_h1.RemoteH1DoubleRocker3"
}
Tobbe8000 commented 2 months ago

try adding more zigbee products so you get a better zigbee network. that's probably what solved my problem.. because I was moving everything from other hubs to home assistant and when I got more electric lights it suddenly worked . I'm fairly new to Home Assistant, so unfortunately I can't help and read error logs as I haven't learned it yet.

Mvh Tobias Ström Liljengård


Från: returnofthem @.> Skickat: den 29 juli 2024 01:15 Till: home-assistant/core @.> Kopia: Tobbe8000 @.>; Mention @.> Ämne: Re: [home-assistant/core] problem with Aqara Wireless Remote Switch H1 Double Rocker (Issue #122689)

Ah ok, that's good news for you but not for me!

In case it helps the maintainers, here are my details. My problem is identical - the switch never comes back after a power loss, reboot, or event just a restart of ZHA.

Versions Core: 2024.7.3 Supervisor: 2024.06.2 Operating System: 12.4 Frontend: 20240710.0

Last known good N/A, I'm a new Home Assistant user

Installation Type HAOS on Raspberry Pi 4b, 4GB

Integration causing the issue Zigbee Home Automation

Zigbee Zongle SONOFF Zigbee 3.0 USB Dongle Plus (E-version)

Diagnostics Log of ZHA restarting and losing the switch home-assistant_zha_2024-07-28T22-36-01.103Z.loghttps://github.com/user-attachments/files/16405509/home-assistant_zha_2024-07-28T22-36-01.103Z.log

Device immediately after pairing Immediately.after.pairing.jpeg (view on web)https://github.com/user-attachments/assets/fac747e2-0571-4df5-86e4-7a6823e4231d

Device after ZHA restart or system reboot After.reboot.jpeg (view on web)https://github.com/user-attachments/assets/7f426470-bc00-49c1-9322-226ab727f7ee

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/122689#issuecomment-2254683560, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A657YALU7JA537IMILIGNPLZOV3PLAVCNFSM6AAAAABLRURRCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGY4DGNJWGA. You are receiving this because you were mentioned.Message ID: @.***>

returnofthem commented 2 months ago

I've also managed to solve my version of this problem. For me, what fixed it was flashing the Sonoff E dongle from using the Ember firmware back to using the latest EZSP firmware using this site: https://darkxst.github.io/silabs-firmware-builder/

The dongle is now running EZSP 7.3.1.0 build 176, and the switch stays linked even after fully powering off the Pi and doing a cold boot, whereas previously it wouldn't even stay linked after restarting the ZHA service.

puddly commented 2 months ago

Ember and EZSP are the exact same thing. What firmware version were you running before and which one are you running right now?

returnofthem commented 2 months ago

Ah ok, apologies - I'm still new to all this so not always clear on the terms.

Initially I was using this: https://github.com/darkxst/silabs-firmware-builder/blob/main/firmware_builds/zbdonglee/ncp-uart-hw-v7.4.3.0-zbdonglee-115200.gbl

I'm now running the version the tool above flashes if you just select "Zigbee (EZSP)" from the menu, which is reported as ESZP v 7.3.1.0 (SDK 4.3.1)

So one major version lower, which presumably is a more stable release. This is on me for following random guides on the internet, but the reason I did that is that whatever firmware was initially on the Sonoff dongle when I got it wouldn't pair with the Aqara switch at all.

puddly commented 2 months ago

Got it, thanks!

Just to confirm I'm reading this issue correctly: the Aqara H1 appears to "disconnect" if you restart HA while you were running EmberZNet 7.4.3. When you downgraded back to 7.3.1, it started working?

returnofthem commented 2 months ago

That's correct - if you take a look at my post above with the screenshots, you can see the before & after state of the device listing in ZHA. It's like it completely forgets everything it knows about it and is reporting "There's meant to be a device here but I have no idea what it is"