Lumi.switch.n0agl1 not working in ZHA

nickrout · April 9, 2023, 10:25pm

Logs. (10 chars)

400HPMustang · April 9, 2023, 10:28pm

Sorry, I don’t know what you mean. Could you please be more specific?

nickrout · April 9, 2023, 11:02pm

Post your logs.

400HPMustang · April 9, 2023, 11:08pm

my logs are too big to pastebin and it appears I can’t attach a text file here? is there anything I can do to narrow down the logs and get you the specific information you’re asking for?

nickrout · April 10, 2023, 2:16am

I’m not asking for anything, just telling you what you need to supply if you want a problem solved.

Restart HA. A new log will be started. Play with the switch. The logs should be short enough to post somewhere.

Rofo · April 13, 2023, 9:23am

Did you see my note on that thread about the new variant of the switch, and the changes you have to make to the new models work ?

Could that be the issue for you ?

Simply use the quirk above and change the models line from this:-

MODELS_INFO: [(LUMI, “lumi.switch.n0agl1”)],

to

MODELS_INFO: [(LUMI, “lumi.switch.n0agl1”),(LUMI, “lumi.switch.n0acn2”)],

And it starts working.!

solomalee · April 23, 2023, 11:08am

Initially Aqara T1 associates with ZHA showing only Diagnostic: Device Temperature and Identify (plus hidden LQI & RSSI).

Here’s how I got it working…

Removed the device from ZHA
Reset by pressing and holding the button on the Aqara T1 for 8 seconds.
Started device discovery in ZHA
Repeatedly pressed the button on the Aqara T1 during the interview process (about every second).
After about 20 seconds many more entities for the device are reported

Controls: Light
Sensors: Active Power, Power Factor, Summation Delivered
Configuration: Previous Value

Thanks to @Ksi for the setup trick!

Gilles2 · June 9, 2023, 3:13pm

Do you confirm you get actual values for the Sensors: Active Power, Power Factor, Summation Delivered ?
On my side, they are reported and available… but always at 0 value.
Thanks

Skywiper · September 21, 2023, 7:42pm

Can anyone confirm whether this trick worked to actually get values on entities like Active Power etc.?

Thanks!

Rofo · September 22, 2023, 2:28pm

Since HA release 2023.9.x (not sure exactly), you no longer need a local quirk to run this device, its baked into ZHA core quirks now.

I have a few variants of these T1s and it looks like the n0agl1 still doesn’t correctly report active power, but it does show as an entity, and ‘summation delivered’ does appear to work:

However, variant n0acn2 does work:

homeroleal · November 6, 2024, 1:01pm

The issue open related to this topic (seems that there is no resolution)

github.com/zigpy/zha-device-handlers

[Device Support Request] Aqara T1 relay `lumi.switch.n0agl1`

opened 03:23PM - 10 May 21 UTC

mbw2001

priority: high Xiaomi

**Is your feature request related to a problem? Please describe.** I have added… the lumi.switch.n0agl1 to home assistant, it is a relay but identified as a lightbulb. As I am using it for a fan for the bathroom that is misleading. Secondly toggle from lovelace, doesn't work. PowerOff works, but PowerOn doesn't. I assume that is related to being identified as a lightbulb, but I don't know for sure. Sending zha_cluster_command with: ```yaml ieee: 'XXX' endpoint_id: 1 cluster_id: 6 cluster_type: in command: YYY command_type: server ``` The the command being 1 to turn on and 0 to turn off works perfectly, but doesn't integrate well with the UI. **Describe the solution you'd like** Providing a correct device type, and fixing the poweroff and power toggle functionality. **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.** ```json { "node_descriptor": "NodeDescriptor(byte1=1, byte2=64, mac_capability_flags=142, manufacturer_code=4447, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=0, *allocate_address=True, *complex_descriptor_available=False, *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, *is_valid=True, *logical_type=<LogicalType.Router: 1>, *user_descriptor_available=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** I have failed in actually making the quirk myself, but I got my HomeAssistant setup with the custom quirks folder, so I will happily test, and provide feedback and/or more information if needed.