Z-stack Home 1.2.2 HA profile Light Toggling

Do you check endpoint in your zclSampleSw_DstAddr?

If you find time then please have a look at it(this is 2nd priority). Here i have included sniffer log. Sorry for file size to be too large. I am not getting similar packets and that's why i have included such big file. I was testing toggling command through hyper terminal one ready made zigbee product which is power outlet and which acts as router. In sniffer log you can see the packet details after i had started. In log you can find another end device packets also with short address 0xbe85 which was already connected to the coordinator. please do not concentrate and ignore packets with short address (0xbe85).
Packet No 9537 is the packet where i had powered on the router(readymade device) and during this time i had disabled SECURE=1 and TC_LINKKEY_JOIN. Till packet no 9791 you can see that router was not associating to the coordinator.
Then i had enabled SECURE=1 & TC_LINKKEY_JOIN as you had told before that for these devices we need to enable these parameters. you can see in log that 0x7697 short address was assigned to the router and later it got disassociated and again short address was assigned(0x7364). After this you can see in log that router is not polling for data at zc and even if i restarted and factory reseted it, its not sending any beacon or device annce and thereafter i am getting only broadcast message from router which is some unknown command.
Same thing was happening while testing phillips hue also after enabling those parameters and i was getting similar kinds of packets for hue also. Why using "SECURE=1 and TC_LINKKEY_JOIN" is making such change and there after device is not able to associate with the network? Rest i will be continuing tomorrow.ab.psd

In Previous sniffer log one of my zed(with short address 0xbe85) was in on condition. then i had switched on centralite. hue was not switched on at all. I had mentioned hue to just to tell the behaviour in packet reception was similar when i had factory reseted hue. In my previous log only i was getting device annce and APS frames after i had enabled SECURE=1 and TC_LINKKEY_JOIN. After that i am not getting these device annce and aps frame packets. I have included the new sniffer log when only zc and centralite is in on condition.

I do know the importance of using Ubiqua Packet Analyzer which is very helpful in getting detailed process of packet transmission through air but its not possible for me to afford such huge amount(999$ which may be approx 60000-65000 in indian rupees). I am extremely sorry for that.

b.psd

Previous log shows the packet transmission when my zc was in on condition and later i had switched on centralite. Similar kinds of packets are received when i power recycle centralite every time. I have included new low which shows packet received when i had factory resetted it. Is it getting associated with my zc?

c.psd

Hi Yikai,

Is it possible that sniffer will capture data transmission to an unassociated device in a network? I mean if i know the short address and if i want to send some data to that device even if the device is not in network then will there be any packet seen in the sniffer log? No matter packet is delivered to destination or not.

Again centralite device is not associating with my zc as you can see in the log. Even after factory resetting its not associating. sniffer shows zc powered on first and centralite device swithced off and later centralite device factroy resettede.psd

Hi Yikai,

Here i have included sniffer log for data transmission when my zc and centralite is in on condition. Initially, only my zc is in ON condition and centralite is in off condition. Then i had powered on centralite. The APS packets are received as seen in the sniffer log.

1)I want to know whether centralite is associated with my zc.

2)from sniffer log i can see that centralite has short address as 0x86d6. So if i send active end point request from hyper terminal with 0x86d6 as nwkaddr then will sniffer capture this request.8081.router.psd

Hi Yikai,

Sorry for not replying to your post. I was busy in some important work and couldn't find time to work on zigbee.

1)Actually i wanted to send some MT command like active end point request to centralite through hyper terminal using the short address as seen in the sniffer log. I had sent this request but i am not finding any request packet transmitted over the air.

2)Here i have included the data packets captured by ubiqua packet analyzer. I have downloaded trial version. In this log initially zc was powered and later i had powered on centralite. Can you please tell me whether centralite is asociated with my zc?  If its associated  then how can i test centralite? is it by plugging light to the terminal and sending light toggle command. I am trying to attach .cubx log but its not getting attached

I don't see any beacon request and association in your sniffer log so I believe the centralite device doesn't join ZC. Do you do factory reset on  centralite device and do permit join on your ZC to make it join?

I had enabled permit join NLME_PermitJoiningRequest(0xff); in void zclSampleSw_Init( byte task_id )
 of zcl_samplesw file. For resetting centralite i had continuously pressed the button provided in it and held for sometime until the green status button glows while powering it. I find these kind of packets in sniffer log. I had repeated the resetting process like this twice or thrice. I don't find any association packet. I had enabled security SECURE=1 & TC_LINKKEY_JOIN. If its my own designed device then i can doubt in fw and make some changes but what i can do in these readymade
devices. Similar thing results for hue also(hue packets not available in this sniffer log.

I am doing following process to factory  reset.Is it correct?