Lumi.switch.n0agl1 not working in ZHA

davinci · July 13, 2022, 6:14pm

This Aqara Switch T1 should be supported, but only reveals a temperature sensor of 0.3°C.

davinci · July 14, 2022, 6:56am

Is there anything I can do to make it work?

nickrout · July 14, 2022, 10:36am

Post logs for a start.

mikkelsiggaard · July 14, 2022, 11:13am

I have the Aqara Smart Plug (EU) that does exactly the same.
Shifts between 0.2 and 0.3 degrees.

mikkelsiggaard · July 14, 2022, 11:20am

When I check in Clusters, the value I get is “29”.

Could there perhaps be an error in (not) converting between Fahrenheit and Celsius?
0.3 degrees Celsius = 32.5 degress Fahrenheit.
29 is pretty close to 32.5.

davinci · July 14, 2022, 12:14pm

Do you have an actual switch? Mine is missing. I only have this sensor available.

mikkelsiggaard · July 14, 2022, 12:22pm

I have two of these

Both still work, but still with incorrect temperature.

Ksi · July 21, 2022, 12:15pm

Hello,

I just bought this device and had the exact same problem: no switch found in HA, and only a weird temperature sensor.
Then I removed the device and paired it again, while pressing the button every second like explained here, and finally the switch entity appeared

mikkelsiggaard · July 21, 2022, 2:01pm

I ended up migrating to Zigbee2MQTT, which I like a lot.

davinci · July 21, 2022, 5:13pm

Yes I am also back in Z2M, but good that it worked finally in ZHA.

GoGreenSI · July 23, 2022, 9:02am

Same issue here, with n0agl1 and ZHA.
Just strange temperature. No power meter and switch.

Ksi · July 27, 2022, 9:10am

How is Zigbee2MQTT better? (I never tried, but would like to know if it’s worth migrating from ZHA)

mikkelsiggaard · July 27, 2022, 10:52am

I don’t know if it is the MQTT part or what, but compatibility just seems better with the devices I’ve tested.

I like the UI better too.

For me migrating was pretty easy (with around 20 devices), and worth it.

GoGreenSI · August 2, 2022, 11:07pm

I have finaly found solution here:
https://github.com/zigpy/zha-device-handlers/issues/882#issuecomment-1046830221

downgrading Conbee II firmware from 26720700 to 26680700,
removing T1 device
restart HAS OS (not sure if this is necessary after fw downgrade)
add T1

… and have fully functional relay (except device temperature. Still 0.2)

Soullancer · September 11, 2022, 5:41pm

Hey guys

In using a sonoff zigbee 3.0 usb stick with the latest firmware and zha, latest home assistant firmware.

I keep getting the same issues as you guys trying to add a t1 switch with neutral (ssm-u01). Gets detected as a lumi without any functions but the broken 0.2 temp sensor.

Tried resetting and adding several times… but now I’m stuck with a useless switch

Can anyone help? Stuck in finding a solution to get my lights working as I only see a conbee solution and pressing the button while adding it to the ZigBee network doesn’t work aswell

nickrout · September 11, 2022, 8:05pm

Latest is not a version, nor is it easy to diagnose with no logs.

eesdil · November 17, 2022, 9:25am

Hi,

I am also using the Sonoff zigbee 3.0 usb stick and the lumi.switch.n0agl1 (two alternatives) and it is not fully operational.
I was able to manage to be able to switch off/on from HA, but when I turn on/off the phisical switch, then it is not triggering anything in HA. I guess it is using wrong cluster, I tried to debug in zha, but seemingly I have no idea how it is really working
The device temperature seemingly working if you check the raw data.
Also if I ready the attribute after the physical switching, it is reading and updating the correct data in HA

Metering:

Device temp:
Showing 0.2/0.3

I used this quirk for it:

github.com/zigpy/zha-device-handlers

[Device Support Request] Aqara T1 with neutral (lumi.switch.n0agl1) switch_type Support

opened 07:19PM - 26 Dec 21 UTC

alex-mikhaylov

**Is your feature request related to a problem? Please describe.** By default t…he Aqara's T1 with neutral (lumi.switch.n0agl1) `switch_type` is set to a rocker switch by default and cannot be changed via ZHA. This makes it impossible to use the switch with a momentary (push) button. **Describe the solution you'd like** Making it possible to change the `switch_type` attribute via ZHA. **Device signature - this can be acquired by removing the device from ZHA and pairing it again from the add devices screen. Be sure to add the entire content of the log panel after pairing the device to a code block below this line.** ```{ "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4447, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)", "endpoints": { "1": { "profile_id": 260, "device_type": "0x0100", "in_clusters": [ "0x0000", "0x0002", "0x0003", "0x0004", "0x0005", "0x0006", "0x0009", "0x000a", "0x0702", "0x0b04", "0xfcc0" ], "out_clusters": [ "0x0019" ] }, "21": { "profile_id": 260, "device_type": "0x0100", "in_clusters": [ "0x000c" ], "out_clusters": [] }, "31": { "profile_id": 260, "device_type": "0x0100", "in_clusters": [ "0x000c" ], "out_clusters": [] }, "41": { "profile_id": 260, "device_type": "0x0100", "in_clusters": [ "0x0012" ], "out_clusters": [] }, "242": { "profile_id": 41440, "device_type": "0x0061", "in_clusters": [], "out_clusters": [ "0x0021" ] } }, "manufacturer": "LUMI", "model": "lumi.switch.n0agl1", "class": "zigpy.device.Device" } ``` **Additional context** Zigbee2MQTT supports changing the switch_type - [link](https://www.zigbee2mqtt.io/devices/SSM-U01.html#switch-type-enum).

Versions:
Home Assistant 2022.11.3
Supervisor 2022.10.2
Operating System 9.3

Happy to provide any log.

thanks

TriffidXL · March 9, 2023, 3:09pm

I had the same problem initially. Your solution solved it for me too.
(Then I removed the device and paired it again, while pressing the button every second)
I am using ZHA with Home Assistant 2023.3.1

Update: the switch is working now but powermeter still does not :(.

Rofo · March 9, 2023, 7:09pm

You dont generally need to re-pair the device when you add a quirk. I’ve found that just restarting HA, or indeed, just restarting the ZHA integration is enough.

400HPMustang · April 9, 2023, 8:25pm

I came across this thread because I’m having the same problem, using a skyconnect and ZHA. I was hoping someone could help me get this working. I’m probably doing something wrong…

I have this in my configuration.yaml

zha:
  database_path: /config/zigbee.db
  enable_quirks: true
  custom_quirks_path: /config/custom_zha_quirks

I have a configuration file in the directory called switch.n0agl1.py and I copied the quirk from here and put it in the file.

I restarted HA and added the relay but I still just get a temperature sensor and an identify button.

What am I missing/doing wrong?