Add Schneider Electric devices #1705
Conversation
- Fixed test definition
|
|
- Use ZCLAttributeDef for attribute
|
It might be possible to add According to Koenkk/zigbee2mqtt#10318 (comment), the device info are : ExpandAnd zigbee info from Jeedom community Zigbee infosVolets roulants module Schneider Electric Wiser CCT5015-0002W {
"ieee": "00:0d:6f:ff:fe:cb:52:11",
"nwk": 31119,
"status": 2,
"lqi": "231",
"rssi": "-65",
"last_seen": "1617382106.1621628",
"node_descriptor": "01:40:8e:5e:10:52:52:00:00:2c:52:00:00",
"endpoints": [
{
"id": 5,
"status": 1,
"device_type": 514,
"profile_id": 260,
"manufacturer": "Schneider Electric",
"model": "PUCK\/SHUTTER\/1",
"output_clusters": [
{
"id": 25,
"name": "Ota",
"attributes": []
}
],
"input_clusters": [
{
"id": 0,
"name": "Basic",
"attributes": [
{
"id": 0,
"name": "zcl_version",
"value": 3
},
{
"id": 1,
"name": "app_version",
"value": 2
},
{
"id": 2,
"name": "stack_version",
"value": 6
},
{
"id": 3,
"name": "hw_version",
"value": 1
},
{
"id": 4,
"name": "manufacturer",
"value": "Schneider Electric"
},
{
"id": 5,
"name": "model",
"value": "PUCK\/SHUTTER\/1"
},
{
"id": 6,
"name": "date_code",
"value": ""
},
{
"id": 7,
"name": "power_source",
"value": 1
},
{
"id": 16384,
"name": "sw_build_id",
"value": "002.004.018 R"
}
]
},
{
"id": 3,
"name": "Identify",
"attributes": []
},
{
"id": 4,
"name": "Groups",
"attributes": []
},
{
"id": 5,
"name": "Scenes",
"attributes": []
},
{
"id": 258,
"name": "Window Covering",
"attributes": []
},
{
"id": 2821,
"name": "Diagnostic",
"attributes": []
}
]
},
{
"id": 242,
"status": 1,
"device_type": 97,
"profile_id": 41440,
"manufacturer": null,
"model": null,
"output_clusters": [
{
"id": 33,
"name": "GreenPowerProxy",
"attributes": []
}
],
"input_clusters": []
}
],
"signature": {
"manufacturer": "Schneider Electric",
"model": "PUCK\/SHUTTER\/1",
"node_desc": {
"byte1": 1,
"byte2": 64,
"mac_capability_flags": 142,
"manufacturer_code": 4190,
"maximum_buffer_size": 82,
"maximum_incoming_transfer_size": 82,
"server_mask": 11264,
"maximum_outgoing_transfer_size": 82,
"descriptor_capability_field": 0
},
"endpoints": {
"5": {
"profile_id": 260,
"device_type": 514,
"input_clusters": [
0,
3,
4,
5,
258,
2821
],
"output_clusters": [
25
]
},
"242": {
"profile_id": 41440,
"device_type": 97,
"input_clusters": [],
"output_clusters": [
33
]
}
}
},
"class": "zigpy.device"
}
|
- Fix constant use
- Edit some attributes name
|
Well after resetting shutter controller, whether I push UP or DOWN, the cover was going down. I thought it was about calibration but it finally ended by breaking cover's motor. EDIT: My motors are back from the dead |
|
I’m planning to do a release today so that I can PR it to HA. Should I wait for this PR? Or are you ok with this potentially not making it in this release? We can update the lib throughout the beta so no pressure. |
|
Thanks for asking 🙏 This PR is definitely not ready. I only tested shutter and there is some weird behavior :
|
|
For the inverted cover we need to deal with that in ZHA |
|
What do you mean ? |
Never mind I misread this: |
- Add CH2AX/SWITCH/1 signature
I'm stuck with the covering. Didn't figure out how to go back to normal behavior. |
I’ve experienced an inverted cover in home assistant (different brand). I do feel like it’s something that should be catered for in zha (not brand specific). |
|
ZHA is using ZigBee standardized cluster/commands/attributes so it's up to the vendors to implement them properly into each of their device. |
|
I installed an NHPB/SHUTTER/1 myself and landed here after going down the rabbit hole of trying to calibrate the lift time from the default (which seems to be 2mn) and trying to get it to report position correctly (currently at -155% for some reason). Thanks for working on this and if there is anything I can help with having physical access to the device please let me now. |
|
I think RN we really need the Schneider electric gateway to know what unofficial zigbee command are sent to devices (eg. Calibration commands) |
|
Price is a tad steep for a brand new gateway but I'll try to find a refurbished or used one, It would be the gateway with the product ID CCTFR6310 right? Also I've just had something weird happen after a complete system reboot (not just HA), the current_position_lift_percentage (id: 0x0008) in cluster 0x0102 is now reporting live value changes (still false in the sense that it's based on a duration longer than the actual time but at least not stuck in a negative value in HA while being stuck at 255 in the cluster reading). It also seems that what the device reports is not the percentage opened but percentage closed. When HA shows 24% opened the device reports 76% in current_position_lift_percentage. I've mounted the device the right way up (which is with the writing on the back of the module upside down for some dumb reason, there's an arrow behind the button which indicates where up is) and upwards triggered from HA is upwards with the physical buttons as well. Which results in the weird behavior of the "up" command in HA actually making the blind go up but HA thinking it's closed when it's fully opened with current_position_lift_percentage reporting 100. Stuff you probably figured out already, I'll try to get my hands on a gateway! |
|
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions. |
|
Hey @axellebot, I'm wondering if there's anything I can do to revive this PR. I have a lot of SE devices that I could use to help debug stuff, especially the various dimmer/switch variations. Most devices seem to work fine with ZHA right now for basic functionality, but especially the calibration stuff seems to be entirely unsupported right now (see e.g. #2798) |
|
There is also now a wiser zigbee fan controller 41ECSFWMZ that I don't think has zigpy support yet. |
I've got one, and it works out of the box in zha. |
Oh good to know! Does the backlight configuration work? |
Yes. Behaviour described below. When you turn the fan on to low/med/high speed, the backlight correctly shows quarter/half/3-quarter lights. When you turn the fan off, the backlight correctly shows full (4-quarter) lights. After some time the backlight turns off again. If the fan is off and you turn the switch on, it just turns the backlight on to full to show it's off. After some time the backlight and switch turn off again. If the fan is on, and you turn off the switch, the fan turns off and the backlight shows full light. After some time the backlight turns off. Screenshots attached.
|
|
Oh thankyou, sorry I meant can you configure if the button led stays on or turns off, as you can in the wiser app? This was a driving force for me moving to z2mqtt for the other wiser mechs. |
I can't see an option for that, no. |
|
OK Thanks! |
|
@axellebot do you plan on updating and re-submitting your quirks in a new pull request? By the way, also check out #2928 and #2836 which are also about Schneider Electric Wiser |
I think it was a too big PR. It should be split in small PR. About my shutter device I'm not planning to work on a new PR any time soon. |
|
I've got a hold on a few Schneider Electric Zigbee devices specifications. List of files/devices:
Hopefully can help someone to make better integrations. @TheJulianJES let me know if there is a better place to put them other than google drive. |
This is priceless! A few of us built alot of this support into zigbee2mqtt based on sniffs from a wiser hub. could have saved spending the ridiculous wiser(cough tuya) hub with that information. Further, You might want to check out the z2m OTA repo. The Index is now populated with a number of links to latest OTA firmware for the 2AX / 10AX / DIMMER / Fan Controller devices that you could incorporate into ZHA. |
Wow, where did you come across these? Are there avenues to get these for other SE devices? |
|
Glad you can find it useful 🙂 And thanks for the tip about the OTA repo, will test it out! I got it from a technical support of a local producer which rebrands Schneider Electric devices. I can try to ask if there is more, but I think they sent me all they've got. |
|
@TheJulianJES let me know if I should create a new issue with this information, I'm not sure what's the best way to handle it. |
That's fantastic. In Australia/NZ the rebranded Schneider products are sold as 'clipsal' and their tech support doesn't want to help those looking to DIY zigbee implementation outside of their supported hardware. There are three other push button mechs that would be great to get the spec for, outside of the 'push button dimmer' that you provided. There's a 2A Switch, 10A Switch and an AC Fan controller. For the most part we've been able to work out clusters and attributes but there are still some unknowns around some functionality. Official documentation is always better than none! Great find. |
|
I wonder if this issue could be reopened and converted (or a new issue created) into a "tracking issue" so that we can collaborate on getting all of the devices supported in a structured way? |
|
Might these be good candidates for converting into a "Quirks V2" quirk instead? See these reference about the new "Quirks V2":
Summary; "Quirks V2" will allow ZHA-quirks developers to add support for a new device that uses non-standard Zigbee clusters and attributes without having to both create a quirk and modify both the codebase of the ZHA component in the Home Assistant code. This "Quirks V2" specifications is still being developers but there is initial "Quirks V2" documentation being worked on, see here -> https://github.com/zigpy/zha-device-handlers/blob/dm/quirks-v2-documentation/quirks_v2.md |
|
@Hedda from a review of the specification PDFs, my 2 cents would be that it'd be pretty easy to add support for these devices using the existing quirks architecture, because the devices are pretty ZCL-compliant, and any manufacturer specific stuff is pretty consistent across devices, ie. there'd be a lot of shared code for these devices (shared clusters, attributes, etc). From a selfish perspective I'd also love to get these devices supported using v1, and maybe later refactored to a v2, rather than waiting for v2 to be "ready," and in the meantime having the devices not be supported at all. |
Todo :