search

Mr-Markus / ZigbeeNet

A .NET Standard library for working with ZigBee
Eclipse Public License 1.0
131 stars 47 forks source link

Updated handling of adding nodes and associated notifications #71

Closed spudwebb closed 4 years ago

spudwebb commented 4 years ago

I ported the following changes:

https://github.com/zsmartsystems/com.zsmartsystems.zigbee/pull/557 https://github.com/zsmartsystems/com.zsmartsystems.zigbee/pull/671 https://github.com/zsmartsystems/com.zsmartsystems.zigbee/pull/685 https://github.com/zsmartsystems/com.zsmartsystems.zigbee/pull/808

spudwebb commented 4 years ago

No I don't have this problem, I get valid NodeDescriptor responses

[16:14:08 DBG] 17880104E15812: Node SVC Discovery: NodeDescriptorResponse returned NodeDescriptorResponse [20978/0 -> 0/0, cluster=32770, transId=, status=SUCCESS, nwkAddrOfInterest=20978, nodeDescriptor=NodeDescriptor [apsFlags=0, bufferSize=71, complexDescriptorAvailable=False, manufacturerCode=4107, logicalType=ROUTER, serverCapabilities=, incomingTransferSize=45, outgoingTransferSize=45, userDescriptorAvailable=False, frequencyBands=FREQ_2400_MHZ, macCapabilities=FULL_FUNCTION_DEVICE, MAINS_POWER, RECEIVER_ON_WHEN_IDLE, extendedEndpointListAvailable=False, extendedSimpleDescriptorListAvailable=False, stackCompliance=0]]
[16:14:09 DBG] 17880104E15812: Node SVC Discovery: request NODE_DESCRIPTOR successful.

your second problem is linked to the first one, because your ZigBeeNode.NodeDescriptor is null, ZigBeeNode.IsDiscovered() return false.

Mr-Markus commented 4 years ago

OK I understand that it is a subsequent error. I will test it with another device tomorrow. Maybe it is a firmware problem on device side. Otherwise everything else works fine 👍