Closed Buci007 closed 1 year ago
I dont have experience of Legrand remotes but if its doing checkins its very positive.
IKEA remotes is not doing it then being new paired and need being reconfigured
from the device card for getting reporting OK to the system.
Tyre doing one reconfigure of your remote and waking it up the sending commands to it.
Thanky you for your response. With reconfigure and push the on and off button on the switch I got a result failed. Details: cluster and binding all are NOK. Reconfigure again with short push on EZ button. (reset and pairing button) The reconfiguration is failed, but binding and reporting - OK. BinaryInput - OK, PowerConfiguration - OK, PollControl - OK, OnOff - NOK, LevelControl - NOK. Ckecking event fired in every hours. No other event fired if On/Off button is pressed. The switch worked 1-2 months without any problem before the battery changed. The switch use the standard zigpy.device.Device quirk. Is there any change can cause this behaviour?
I think (= not knowing) that ZHA is trying binding to much cluster then the device can handling and the reconfigure is failing (if looking in the log om sure you is having binding table full).
I see 2 ways trying fixing it.
Manage Zigbee Device
(the three .
) right from reconfigure) and try deleting some or all bindings and adding what you is needing (power, OnOff and Level and perhaps pull control).From your writing we can see that the 3 first is being made OK and the 2 last is not working and we like have its opposite.
I think its one light controller device so likely is using group binding and not device binding but you must testing what is working for knowing. If you is deleting all device and group binding you is not reporting any thing to ZHA (can being that is sending to group 0 as default then its working) and normally group 0 is the standard reporting group and the coordinator is the standard device if using device binding.
Sorry i cant saying exact what shall working or not then i have not experience of the device.
Edit: looks its using group bindings (from one other but not the same device) https://www.zigbee2mqtt.io/devices/067774.html.
Maybe that quirk can do the job:
Probably the device_automation_triggers
needs to be tunned.
Your device's signature match with the already defuned RemoteDimmer
quirk.
To check, remove any previous quirk for your device.
Copy the current legrand/dimmer.py
file to your local quirk folder:
Go to the RemoteDimmer
class and put your device in the MODELS_INFO
like this:
class RemoteDimmer(CustomDevice):
"""Remote dimmer ."""
signature = {
MODELS_INFO: [
(f" {LEGRAND}", " Remote dimmer switch"),
(f" {LEGRAND}", " Remote switch"),
],
Save changes, delete any __pycache__
folder and restart HA.
EDIT: fix typo
Is some one knowing if all devices is in-wall switches / dimmers for light commands ? I asking then normally users like having device automatons for all (in)possible "clicks". If its in-wall and is pure light controllers i think its best not implanting DA for it but some user like getting it for easy making clickomania of them.
Hi! I did what you suggested.
class RemoteDimmer(CustomDevice):
"""Remote dimmer ."""
signature = {
MODELS_INFO: [
(f" {LEGRAND}", " Remote dimmer switch"),
(f" {LEGRAND}", " Remote switch")
],
I add the missing "," at the end of the first device line, with this update the quirk is loaded without crashing. home-assistant_2023-01-16T13-06-30.798Z.log
The device signature lists that the quirk is used. Signature.txt
The switch is as a binary input sensor detected, as before and only fires "Legrand Remote switch Checkin event was fired" No any response on push Off or On buttons. Thanks!
Maybe I was not clear, the switch doesn't work, only fire "Checking event" :-( Do you have any other suggestion?
Fixing the quirk can helping with some functions but first you need getting the binding / reporting working so you is getting events in ZHA. As it was working before changing the battery i think its not one problem with the device firmware and also ZHA is doing the things right but its have limited binding table and need being deleted and added new for getting it reporting OK.
I add the device diagnostic, maybe it can help Legrand Remote switch diagnostic.txt
Thank you! You are right, but what can I do others? I binded it several times. I deleted the device and added again with "Add device". I made factory reset of the switch and tried everything was possible on my known based on the Legrand developer site. I did Reconfiguration as well. Binding and Reporting in the head I got OK. In the table LegrandPowerConfiguration, BinaryInput, PollControll i got OK. On/Off and LevelControl - NOK binding. In the Zigbee device handling I cannot bind manually. There are listed the devices can bind, but nothing happen if I try to bind. I really appreciate if you can advice me, what can I do.
Delete the device in ZHA and wait one minute (the database need committing the deletion) and then adding it in ZHA and only giving one name and aria and test if its sending events from OnOff cluster.
I deleted the device and waited 2 minutes. Then I restarted the system and device with name "Legrand Remote switch" is back with their Entities. After deleting it with reload the configuration of the SONOFF Zigbee 3.0 USB Dongle the switch was back again. I must deleted it 5 times with restart the system as well to avoide, that the switch come back. Currently I have 28 devices and 142 entities listed in the coordinator excluded this Legrand Switch.
After the switch is deleted, I tried to add with the standard and with the custom quirks as well. I tried to reconfigurate as well. PollControl sometimes binded, sometimes not. The On/Off and LevelControll clusters never binded. As you wrote there are the 2 cluster binding missing. Legrand Remote switch Diagnostic with the custom quirk.txt I got Checking Events and Battery info. Is there any solution to force these bindings?
This is a battery device. Have you tried to keep it awake during all the pairing process? Just push the button every second or so to prevent it from getting sleep until the pairing process ends.
I tried several type before, but I wanted to answer you after I made the test again. I found the info in HA community pages, that the device(s) come back automatically if they are not factory reset. I deleted the switch and did a factory reset with 20 second push on the EZ button. Waited 5 minutes. I started the Add device process. Pushed 1 second the EZ (pairing) button on the switch. Green light started blinking about 10-15 second. I pushed per second the Off button until the process stopped, about 30-40 second. On/Off cluster binded, the switch fire On / Off event :-) I guess the battery clusters didn't binded, no battery info :-( But I'm happy that it works again :-) Where can I see the the bindings if I missed to save the Binding login? I download the diagnostic data of the device and compared the working and not working variant. They are the same there and there isn't any infromation about bindings.. Thanks for you both!!!!
That is one personality of the device i have not seen before !!! Great that you is have getting it working ! You can trying adding binding of power configure cluster and deleting some other if its not working. And now you is knowing how getting it back if it stop working :-))
If you like making more advanced binding work you can using https://github.com/mdeweerd/zha-toolkit it working very well but is little more technical but it can reading all bindings in normal devices.
Glad to know you get it working again! Just to be sure, because you said that device was already working before the battery change (I didn't read this part 😓): Is the quirk needed for this device?
It doesn't cost anything to include the new device in the quirk, but I'd like to be sure.
No, I didn't use the custom quirk. I was able to bind with the standard. "zigpy.device.Device"
Hi all, I'm unfortunately having issues with battery powered switches from Legrand (067723) as well. The buttons (on/off) events only show up in HA assistant sometimes, but not always. When it works and I continue to press another button within <1 sec, the button presses are usually recognized within HA. However if I wait a little longer, nothing happens. Only after a couple of more clicks / seconds, HA starts recognizing the events again.
Does this issue sound familiar to anyone?
I've 3 Legrand battery switches of which 2 show an "N" at the end of their product number (067723N - google is not showing anything this). Only the switch without the N is working as expected...
Did anyone have similar issues / tips how this could be solved?
Thanks!
Hi WLR13, Check the firmware of the switches. Check the distance between switch and coordinator (big distance without router supported can cause this probleme) Check Legrand developer forum https://developer.legrand.com/forums/ 067723 is a Céliane wireless switch. There are 2 verions 067723A and 067723L
Hi EzEsAz,
Thanks, I'll do that. Just an update on the behavior. I was wrong when I said that the switch does not work sometimes. It just takes 5-10 seconds for the lights to come on... Sometimes it works instantly (as expected).
Will update here if I find out anything at Legrand forum.
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 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.
Probleme I used a Legrand 7 522 85 wireless On/Off switch until last week integrated in HA (Home Assistant 2023.1.0) with Sonoff Zigbee 3.0 Dongle Plus-E. The switch fired ZHA event e.g.: device_ieee: 00:04:74:00:00:c1:c3:be, endpoint_id: 1, command: "off" and I was able to use it for automatization. I had to change the battery and reconnect to the system. The switch is reconnected, but fire only "Checking event." Do not fire any events on push of the buttons. I tried to reconnect several time the reason is the same. I have a Legrand gateway as well and paired to this the switch. In the Legrand system the switch worked. I reset and connected again to HA, the result same, no event fired. Link to the switch: https://vikiwat.com/wireless-switch-netatmo-752285-vallena-life-cream-legrand Link to the Legrand developer site https://developer.legrand.com/documentation/compatible-product/ Wireless Switch On / Off, Cloud type: NLTOO, Product type ZLE18 is declared ZigBee 3.0 compatible product.
Describe the solution you'd like I would like to use again the switch
Signatures
```yaml { "node_descriptor": "NodeDescriptor(logical_type=Diagnostic information
```yaml { "home_assistant": { "installation_type": "Home Assistant Container", "version": "2023.1.0", "dev": false, "hassio": false, "virtualenv": false, "python_version": "3.10.7", "docker": true, "arch": "x86_64", "timezone": "Europe/Budapest", "os_name": "Linux", "os_version": "4.4.180+", "run_as_root": true }, "custom_components": { "sonoff": { "version": "3.3.1", "requirements": [ "pycryptodome>=3.6.6" ] }, "hacs": { "version": "1.29.0", "requirements": [ "aiogithubapi>=22.10.1" ] }, "powercalc": { "version": "v1.2.4", "requirements": [ "numpy>=1.21.1" ] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "config_flow": true, "documentation": "https://www.home-assistant.io/integrations/zha", "requirements": [ "bellows==0.34.5", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.90", "zigpy-deconz==0.19.2", "zigpy==0.52.3", "zigpy-xbee==0.16.2", "zigpy-zigate==0.10.3", "zigpy-znp==0.9.2" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "*2652*", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "1A86", "pid": "55D4", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus v2" ] }, { "vid": "10C4", "pid": "EA60", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*zigstar*", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "*conbee*", "known_devices": [ "Conbee II" ] }, { "vid": "10C4", "pid": "8A2A", "description": "*zigbee*", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "*zigate*", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "*zigate*", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "*bv 2010/10*", "known_devices": [ "Bitron Video AV2010/10" ] } ], "codeowners": [ "@dmulcahey", "@adminiuga", "@puddly" ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube*" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "*zigate*" }, { "type": "_zigstar_gw._tcp.local.", "name": "*zigstar*" }, { "type": "_slzb-06._tcp.local.", "name": "slzb-06*" } ], "dependencies": [ "file_upload" ], "after_dependencies": [ "onboarding", "usb", "zeroconf" ], "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp" ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 38346, "manufacturer": " Legrand", "model": " Remote switch", "name": " Legrand Remote switch", "quirk_applied": false, "quirk_class": "zigpy.device.Device", "manufacturer_code": 4129, "power_source": "Battery or Unknown", "lqi": 200, "rssi": -50, "last_seen": "2023-01-15T09:02:55", "available": true, "device_type": "EndDevice", "signature": { "node_descriptor": "NodeDescriptor(logical_type=Add device log
``` 0xC91F](S26R2ZB): Device seen - marking the device available and resetting counter [0xC91F](S26R2ZB): Update device availability - device available: True - new availability: True - changed: False [0xFE3D](TS0011): last_seen is 1984002.010282278 seconds ago and ping attempts have been exhausted, marking the device unavailable [0xFE3D](TS0011): Update device availability - device available: False - new availability: False - changed: False [0xF808](01MINIZB): Device seen - marking the device available and resetting counter [0xF808](01MINIZB): Update device availability - device available: True - new availability: True - changed: False Received a packet: ZigbeePacket(src=AddrModeAddress(addr_mode=Additional context Add any other context or screenshots about the feature request here.