-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[New Device] Schneider Electric FLS/AIRLINK/4 #61
Comments
I've added support for this and the next experimental build will have a new plugin named nymea-plugin-zigbee-schneiderelectric. As I don't have such a device, I'd need you to test it. Please upgrade to experimental (the entire nymea system) or set up a test environment if you have a spare zigbee adapter available. Then install the new plugin. It should support both modes (single and dual). Please report back. |
Hi again. I have now tested the device, and i can get actions through. There's a few things missing:
EDIT: I have some other Schneider devices (not all unfortunately). I will open some issues on those as well, when i get the time. EDIT2: Nymea seems to think the device is offline after a while, and then greys it out for configuration. |
Hmm... I've looked at the z2m code and they also only bind to endpoint 21 and 22, documentation saying that in dual mode it would send presses on those endpoints, in single channel mode only on endpoint 21... Which buttons are hooked up to EP 23 and 24 and aren't working? Afaict, the device does not provide a PowerConfiguration input cluster, which would be required for battery status reporting. Also z2m doesn't seem to do anything in regard to the battery. As per zigbee spec, at least on/off doesn't provide press/release events. It only fires single on/off commands. For the LevelControl cluster (up/down), in theory there would be the possibility to implement start/stop (which often is pressed/released). However, as every remote control works differently, I can't tell for sure if this one actually does that (probably it does). Given those variations in devices, and espeicially since non-zigbee devices again act totally different, nymea tries to unify the behavior across all button devices by sending repeated up/down commands for the duration while it is pressed. |
I've now added some code to also bind to endpoints 23 and 24 and added some more debug output. Once it's build (in a couple of hours), please upgrade, re-add the remote to the network and then check out the logs (enable the ZigbeeSchneiderElectric category). Press each button and see what events in the logs it produces, then tell me which lines are produced by which buttons please. |
I'm sorry if i confused you. That was not my intention.
You are correct, endpoint 23 and 24 doesn't do anything. They don't generate any actions. Endpoint 21, handles the two buttons on top, and endpoint 22, handles those on the bottom.
Which is weird, because i believe it works in Deconz. But i can't back that claim up. I just know that the official gateway can readout the battery, so it's probably manufacture specific.
I know that Hubitat and Deconz indicates Press, Hold and Release as default. Double and triple press is also a thing, but a bit more rare. And i know that this device has the capability as i "wrote" a driver for hubitat for it. |
So everything is ok? I'll drop the code which I've added for EP 23 and 24 again then.
Well, there is an unknown cluster with ID 0xff17 on the device... That seems to be a manufacturer specific one... z2m doesn't handle it, perhaps deconz does? Do you happen to know where to find the device "drivers" for deconz?
That would only work using the manufacturer specific cluster again then... The others (namely OnOff and LevelControl) don't support that. OnOff only supports sending on or off commands. The LevelControl does support "Move", "Step" and "Stop" though which could be converted to a press and release I suppose... |
It would seem so. I will test some more, and get back to you.
I can only find this: https://github.com/dresden-elektronik/deconz-rest-plugin/blob/master/devices/wiser/fuga_4button_battery_switch.json
This is also visible in the Deconz DDF file above. |
Ok... Now I feel stupid... Why did I miss the PowerConfiguration cluster? Anyhow, added battery handling now. I still can't really make much sense of the pressed/released. But perhaps it would make sense if you enable logging for the ZigbeeSchneiderElectric category and evaluate the log of the events the device sends when pressing the buttons. |
I've tried this new version. Buttons still register, but i still see 4 different devices in the 'Things' section. I would expect 1 device, with 4 different functions like the Ikea Remote. Battery isn't reporting as of yet, but i will give it some time.
The way that Deconz handles it: Hubitat does something like that. When controlling a light you would put together some logic that would begin a fade with a hold, and stop the fade with the release. |
If you have 4 things than something is fishy.... can you tell me the thing class id of those things? in main menu -> configure things -> open it and it should tell the thing class id there. |
Not sure if this is what you want, but this is what I could find: Type Interfaces And the ID of the thing: ea6e8202-255d-41a2-b6f0-cfaf31120639 Can't locate a class ID |
right... that's what I was suspecting... it's picked up by the wrong plugin. Did you install the new nymea-plugin-zigbee-schneiderelectric? |
I’m not at home right now, so I can’t try to reconnect it. I’m almost certain that I did yesterday after an update though. The plug-in is installed with version 1.8.0+202303301613 Med venlig hilsenStephan Heinrichsen Den 31. mar. 2023 kl. 12.27 skrev Michael Zanetti ***@***.***>:
right... that's what I was suspecting... it's picked up by the wrong plugin. Did you install the new nymea-plugin-zigbee-schneiderelectric?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
After installation of the new plugin you'd have to remove and add the device from the network again, as a newly added plugin is not allowed to steal a device from another plugin which had picked it up earlier. |
I know, and I'm pretty sure I did that, more than once. And I'm pretty sure I did it yesterday to test the battery change. Will verify later. |
I have just verified that it's recognised as a remote control, even after removed from the network, Nymea and repaired. |
Ok... something's wrong then, but I can't spot the mistake yet. I've added some more logging. Please update, enable the ZigbeeSchneiderElectric logging category and check the logs while adding the device to the network. |
I've now tried with a fully updated Nymea. Reset the button, and repaired with Nymea.
|
Thanks. That was helpful. Found the mistake. the next build should cause it to be picked up by the correct plugin. |
And once again, life got in the way 😃.
I can see that you check for the release function in the logs.
|
It's a bit hard for me to follow what exactly is wrong without having such a device... Could you please add some info to each of the logs describing which button produced which line and what you would have expected instead? |
I suspected you would ask me that 😄. |
I don't understand it, but the Logs in the app, doesn't match the logs here. The ON and OFF is registered as one and the same in there.
|
ok. found a bug in the code about the bottom up/down being falsely mapped to top up/down |
Hi
Tried to add this button device to Nymea, but it’s not recognised properly.
It’s available in Z2M. Don’t know if that helps :).
The text was updated successfully, but these errors were encountered: