-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
[zigpy-integration] Allowing Endpoint allocation on ConBee/RaspBee for Livolo, Schnider and fancy devices #1145
Comments
@manup related to the previous discussion in dresden-elektronik/deconz-serial-protocol#17 |
I probably missed something I understood that deConz set 0x01 and 242 ( 0xf2 ), but he was not mentioning 0x50 ( 80 ) |
What does the |
After the startup, here is how I retreive the list of Ep
Here is what I got in the logs
|
You can read the simple descriptor for each endpoint by sending a loopback request to The reason I ask is because the Conbee has three endpoint "slots" and seems to return three types of responses when you read them:
I need to be able to distinguish "real" endpoints from the "invalid" endpoint, which for me looks like this: SimpleDescriptor(
endpoint=184,
profile=7329,
device_type=19200,
device_version=18,
input_clusters=[],
output_clusters=[],
) You say that your Conbee has an endpoint |
Hi, the 0x50 is a very old endpoint which was used for proprietary OTA, it isn't used anymore. You can safely reconfigure it. |
I'm keen to reconfigure it, but Why is not the Zigpy layer doing by default ? |
Personally I'd do it in the application, different applications using zigpy might have different needs. |
Ok, sound fine with, but right now from zigpy standpoint I can only add_endpoints and not remove any |
Originally posted by @puddly in zigpy/zigpy-deconz#172 (comment)
@puddly so if you use |
This is what I understood, basically zigpy_deconz handle EndPoint slots, and so by default there is one slot left (slot 2) |
Hi, I've checked the current firmware code, there is indeed a fixed setting of 2 endpoints. Do you have an overview of how many/which endpoints and their clusters you're using? |
Does that mean you can not simply make and release a new firmware image for ConBee/RaspBee that support more endpoints? |
@manup, I would say the max , but I think if we can extend to one at least and probably 2 Eps would be the best. I don't expect an end user having all strange devices on the same setup. As the clusters are concerned, on the TI / CCxxx / ZNP stack we are just having the Basic Cluster for those Endpoint, as the principle is anyhow all commands send are forwarded back to UART. |
FYI, most users actually do put all their devices on the same setup, at least in my experience many users (but not every user) aim to keep all their Zigbee devices on a single Zigbee network if they know that consolidating them takes the best advantage of Zigbee's mesh networking technology. And another reason is that most Zigbee implementations only support a single Zigbee Coordinator, see example this discussion about having multiple coordinators in one setup at the same time -> zigpy/zigpy#673 |
I do agree, but from a statistical point of view I do not expect a user having ALL this crasy devices which required as many EndPoints. I'm just taking in consideration the deConz memory limitation and indeed we just need to balance between a reasonable need comparing to an unlimited one. Of course unlimited or something like 8 to 10 additional Eps would be great, but I don't think this would make sense, while we might have only few users in the world needing it |
In regards of mixed networks with all kinds of devices, I can also confirm everything thinkable is put together by users :) I'll try to extend two additionals possible endpoints, likely in a second segment in nvram to be up and backward compatible. I'd recommend to configure a few more clusters than Basic for at least one endpoint to support a wider range of devices: IAS ACE and Time server clusters, and IAS Zone, IAS WD client clusters. Some devices actively probe the coordinator for them. |
@manup happy to test any new firmware |
@manup any update on the firmware capable of addressing more than 2 Eps ? |
Hi @pipiche38 sorry got a bit occupied with bug fixing in various places. |
Can you please try the following test version 0x26790700. It provides four configurable endpoints with index 0..3, prior versions have only two endpoints 0..1. Initially the new last two endpoints aren't configured. The new endpoints are placed in a different NVRAM section to be backward compatible for up- and downgrades. deCONZ_ConBeeII_0x26790700.bin.zip For a test I configured the endpoint 0x11 with Identify client cluster additionally to 0x01 and 0xf2. |
Cool glad it works, I'll put this in the official firmware release. Side note to be handle old and this version: There is no command to query how many endpoints are supported, but if the configuration is done for an endpoint ouside the valid index range UNSUPPORTED status is returned. |
Thanks very much for your support. PR for moving from 2 to 4 Max Eps submitted |
@manup I have a few questions about the endpoints implementation.
|
By default the two extra endpoints with index 2 and 3 are not set, which is determined by an invalid application endpoint number as 0x00 or 0xFF, they are also not returned in an ZDP_Active_ep request.
Yes, like the default configuration above, configuring an endpoint number 0x00 or 0xFF disables it.
Basically yes, in the firmware the endpoint configuration is just stored in an array, currently with the size 4. So I think your code here should work.
I haven't seen this yet, but if this happens it should be fixed in the firmware. |
@manup do you have any estimated plan when the firmware will be released ? |
@manup I just tried flashing your beta build of the Conbee II firmware and the extra endpoints indeed are present. However, I'm unable to get any other firmware to run! The Conbee is unresponsive until I flash this beta firmware again: I can't downgrade to either Is there any way to clear NVRAM or otherwise reset the Conbee so that I can use it with older firmwares? |
@manup do you have any update if and when this will be released ? |
1 similar comment
@manup do you have any update if and when this will be released ? |
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. |
@manup is the firmware released ? |
When doing a zdp_active_endpoint_request to the deConz key , we get 3 Eps
0x00 - Ok ZDO
0x01 - ok ZCL
0x50 - what is that ?
cc: @puddly, @deufo
The text was updated successfully, but these errors were encountered: