This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Z-stack Home 1.2.2 HA profile Light Toggling

Other Parts Discussed in Thread: Z-STACK

Which file i can get port & pin configuration of led connected in light project for toggling,on and off process under home automation in z-stack home 1.2.2?

  • hue sends single beacon only as i said before Dono what's problem with all these dvices. You had sent some manufacturer list and their readymade products. How can i get pricing details and all for those products? I want to know pricing structure of smoke detector and presence sensor
  • You should contact manufacture to get price list or you can search Zigbee products on Amazon or eBay.
  • Hi yikai,
    I had gone through various discussion about network formation about hue and bridge at www.everyhue.com . In all these discussion i found people discussing about nwk formation of bridge and 3 set of lights provided with it. None of these discussion discusses about nwk formation with some other zc. Yesterday i was testing hue and centralite for finding reason for not associating. What i found is both devices are not getting factory resetted properly. I want to confirm this whether its getting resetted correctly.
    1)if factory reset is done then will device retain its short address and PAN id in NV memory? In my case even after factory reset both devices are retaining these parameters. if PANid is retained by hue then i don't think it will associate with my zc which has different PANID.
    2)before factory reset hue and remote will be forming a network. evenif i factory reset hue then after disassociating it will again form nwk with remote then when and how it will associate with my zc? According to my understanding hue should not associate with remote after factory reset then only it can join with my zc. Am i correct?
  • 1. No, device won't device retain its short address and PAN id in NV memory.
    2. After factory reset to Hue, it will send beacon request for a while to search Zigbee HA network to join (I don't remember exact time that hue will do this). If it cannot find HA network to join, it will turn to ZLL profile and form a ZLL network.
  • 1)What needs to be done to factory reset? like if i want to factory reset my device then how can i do that. Is it through hardware or software?
    2)hue is constantly changing its operating channel. Sometimes it operates on channel 11,sometimes on channel 15 sometimes on channel 25etc. Why its changing its channel? If my zc is programmed for some other channel then will my zc associate with hue at all?
  • 1. To reset Philips Hue, I have told you that you need a special remote controller to reset it.
    2. In Zigbee ZLL profile, it can form network on any of 16 channels. When you do factory reset to Hue, it will send beacon request on all 16 channels and search one suitable to join. It doesn't matter that which channel your ZC is on.
  • 1) a. Do a scan request ( ZLL spec page 53) over all Zigbee channels (primary channel, secondary channel). The hue will response with a scan response (ZLL spec 66).
    b. once you get the response, extract the channel and ieee address field of the hue.
    c. use the information you get from b) to issue a factory reset

    2) if hue is constantly changing channel, then it might be scanning for a network to join which means it is in factory new condition. In this case, all you need to do is to send a permit join command to coordinator to let it join.
  • Hi YM Liang,
    Thanks for your kind reply.
    1)Can you please refer me the link for the ZLL document you are referring? I want to know how i can factory reset using the scanned channel number and ieee address.
    2)My zc is in indefinite permit join mode only as other zed is able to associate with it. As i had discussed,there is problem in resetting hue which is not getting done properly as its retaining the short address and PANid which gets conflict with my zc PANid and is the reason for no association with my zc
  • 1. These information are revealed in ZigBee Light Link 1.0 Specification.
    2. From your sniffer log, your Philips hue is not properly factory reset.
  • 1) you can get it from here :

    www.zigbee.org/.../zigbee-light-link

    go to the bottom of the page : "Click Here to Download ZigBee Light Link Standard"

    just fill out some info and you should able to download it .

    Also, there is a sample project in the zstack 2.5.1 in "Texas Instruments\Z-Stack Lighting 1.0.2" that is doing exactly what you need.

    2) Have you try power cycling the hue? Sometime this might help. But if it persist - the hue is retaining it old short addr AND constantly is switching channel - then factory reset might the only way out.

  • I am too thinking both devices are not getting properly resetted. But what outcome i should get after resetting both hue and centralite i am getting that. Like if i reset hue then hue light flashes for severaltimes and finally it turns red as what is expected it should be. Similarly centralite led glows after 2sec while pressing and holding the switch provided in it while powering.
  • ya. i am trying to factory reset and hue behaviour is same what it should be while resetting like it flashes for sometimes and finally turns red.
  • When you successfully do factory reset to hue, it would turn red and your will see it sends beacon request on all 16 Zigbee channels in Ubiqua Packet Analyzer. It is similar to centralite smart plug. If I remember correct, you have to hold the button, plug it to power socket, and wait the LED turn ON which means factory reset successfully.
  • Let's say the hue is retaining an short addr in PAN 0x12345678. Is the coordinator that is hosting PAN 0x12345678 present and acitve?

  • I see a single beacon packet in sniffer after factory resetting hue and not for all 16 channels.
  • No. i had tried by keeping the same panid as used by the hue like if hue has panid 0xb129 and if i set the default panid of my zc to 0xb129 then zc assigns 0xb130 as its own panid due to panid conflict
  • sorry i misunderstood your question. i don't know whether panid of hue is assigned by itself or by remote. if its assigned by remote then even after switching off remote same outcome i get. there is no any other device active.
  • If you want to see beacon request on all 16 channels, you have to connect 16 CC2531 usb dongles which receive from 16 channels. Do you do that?
  • I think you better make sure there is no other coordinator around. I was thinking if the hue retains 0xb129, could it be that it really joined back to pan 0xb129 after reset?
  • after factory resetting hue, i receive a beacon packet with packet description as ZLL commisioning read attribute
  • sorry, i have only 1 cc2531 usb dongle but one thing i find is whatever channel i select in sniffer i get a single beacon packet in all these.
  • I suppose this means Hue is sending beacon requests on different channels. If you use 16 CC2531 USB dongle, you will see beacon requests on 16 different channels.
  • Can you please tell me which device assigns panid of hue, phillips hue itself or phillips remote? As i had told earlier i had switched off all other devices and only my zc,remote and hue are in on condition. I had tested by switching off remote and power recycling my zc and hue. Then also i don't see association and same panid used for the hue in the sniffer log
  • Phillips hue itself assigns panid.
  • I just did a reset to my hue bulb with permit join OFF on my zc.The hue doesn't assign panid, instead, it send out beacon with source pan and dest pan set to xffff, on all channels.
  • May i get sample picture of remote you are using? I want to know whether i am using correct remote. May i get network description of your nwk? I mean what devices are you using while testing hue?
  • I will read zll spec and see how to factory reset. If somehow i am able to factory reset centralite then how can i test it i mean if i connect a lamp to the outlet and send ZCL ON/OFF command from zc then will lamp toggle?I have another centralite router also which i want to test whether its working or not.
  • I am using kapparock's IoT router. The router is hosting a Zigbee HA network.

    When I reset a ZLL bulb with permit join OFF, the bulb should return to factory new condition and scan over all the channel with a beacon.

    When I reset a ZLL bulb with permit join ON, the bulb will join the IoT router after reset. Once it join a network, it should stay on one channel.

    Here is a video, where the black box is the IoT router,  sorry for the crappiness:

    www.youtube.com/watch

  • Thanks for providing these useful information. While resetting i am also getting the same light flashing and turning red as it is seen in video. I am keeping my zc in indefinite permit join mode but hue sends a single beacon to each channel and not repeated beacon after factory reset or power recycle until it associates as seen in your sniffer log. I don't have such kind of setup what you have and my zc hardware is designed by me only. Will look for some possibilities if i can reset hue properly.

    properly.
  • Hi Yikai,
    Currently i am working on data transmission through RF(not zigbee protocol) using CC2530. Every time i try to send data through hyper terminal then the uc gets resetted. I had tried to debug and getting such warning after which uc resets. "The stack pointer for stack 'XdataStack' (currently XData:0x1015) is outside the stack range (XData:0x0001 to XData:0x0101)". What may be possible cause for it?
  • Do you send bulk of data? It seems your program use memory out of X-rays boundary.
  • no i am sending just 8 bytes
  • I am sorry that I cannot help too much since I don't know any detail.
  • Its Ok. My problem is solved. It was iar "linker" version problem. I was using newer version of iar banked file in linker "lnk51ew_cc2530F256_banked" in older version of iar program.
    thanks.
  • Cool! It is good to know you solve the problem.
  • Earlier i had told that so many of my hardware are having problem in sending beacon request. Actually these devices were not sending beacon packets and i was thinking this as hardware problem. Finally i found reason(i may be wrong) for not sending beacon. Earlier was defining "HOLD_AUTO_START". I tried by disabling this and all my hardware are now sending beacon packets.
    Do you think this may be reason? If yes then why and what this parameter is used for?
  • Yes, I think this is the reason. HOLD_AUTO_START is for make device hold and not try to join any network. I always disable it in my project. However, it is for someone that don't want to try to join any network when device is power on.
  • 1)If this is defined and device doesn't want to associate to other nwk then what's its usefulness? i mean if device is idle and don't want to join with other nwk when powered then for what purpose it is used? Can you give some situation. is it for zed like enable/disable join at zc?
    2)Is there any way to factory reset devices either through hardware or software like its done in hue and centralite?
  • 1. In some application, people want user to press a button to start joining and HOLD_AUTO_START is for this.
    2. You can use API ZDApp_ResetTimerStart to do factory reset in application.
  • Thanks for providing these useful information. I will be implementing factory reset using interrupt(switch press) in my application.
  • You are welcome.
  • Hi Yikai,
    Is it possible to have port interrupt both at rising and falling edge? I want to sense interrupt at both conditions-either door is opened or it is closed?
  • CC2350 only supports rising or falling edge. If you need to check both, the alternative is connect it to two GPI, one check rising and another check falling.
  • Can you please explain the connection for connecting a single door sensor to two ports?
  • For example, you can connect door sensor circuit to both P0.2 and P1.2, in which P0.2 handles rising edge and P1.2 handle falling edge.
  • is it feasible doing this from hardware point of view? if sensor is connected to two pins then these pins may get shorted and drain voltage. I will try to change the interrupt edge configuration(rising to falling and vice versa)when interrupt occurs. With this way i think i can manage both interrupts for this case though first time
    it may create problem.
  • Why would these pins get short? I just suggest you wire the same signal to both P0.2 and P1.2.
  • Do you mean to have connection like this? if so then if either of the pin gets low there will be continuous drop in voltage and both pins will maintain same potential and hence no interrupt on the other pin.

  • Let's say if we have two door sensor like your circuit and connect to two separate pins. If both sensor go open or close together, do they have problem you mentioned? If not, why do we have problem when we use the same sensor?
  • Sorry. both rising and falling edge interrupts can be sensed with that circuit but more care has to be taken while configuring the pins as i/p. if by mistake any pin is configured as i/p and other as o/p then there will be continuous drop in voltage.