Yes; probably worth checking all the settings against the screen shots of my config below and see how they look (except for the PAN ID they should match up). If you change a writeable field use the pencil icon next to it to enter it, then 'apply' the changes using the 'Profile... Apply Configuration Profile' icon dropdown and save it.
Note that the greyed out networking settings are what your stick is currently using (use the tail chasing arrow icon to refresh the field; when things are working you should see the long/short PAN ID's and operating channel there).
Finally!! Only about a week later than promised by eBay seller...but probably not his fault:
Luckily I'll have some time tomorrow AM while my wife is getting a massage. I need you guys to have this wrapped up by then so I can just do a bunch of copy/paste - capice!?
Not much chance of that I’m in a tent in the middle of Peterborough and it’s wife’s birthday and our wedding anniversary this weekend so further exploration of the mean green Zigbee machine has had to be halted till Tuesday.
It looks like it up to you bro.
I've removed and re-added the Xstick repeatedly per the error message, that doesn't seem to help. I never see anything on the Zigbee join screen on the hub.
I'm probably missing something obvious...but haven't figured it out yet.
I got the same message when trying to join the stick to a new PAN so your setup is probably fine. Because I was trying a bunch of things in addition to deleting/re-adding the radio module I didn't keep complete notes of everything I did at the time (at least ones I can now decipher). But I was able to repeat the process to swap it to another hub. I'll try going through the process again and see if I can get a repeatable step by step.
Only wrinkle is not knowing if we're starting from the same point, setup-wise. Since I'm starting with a 'known working' configuration there might be some setting that I won't be changing when I move it between PANs... hopefully if you make sure all the screenshot settings match up, that would only leave the security key (which is write only).
I've tried to keep track carefully and match up w/your screen shots.
The one item that is a little confusing is that the security key disappears from the field in the configuration after I save it. I presume that's intended behavior - keeping the key secure after it's entered, correct?
Thanks for going through this again to help us figure it out. I spent time tonight trying to see if I could track down the full XML file in case that was important, but my Google-Fu skills were insufficient...
Yes, the key can't be read out by design (at least on this stick).
So here's what I did to hopefully get us at a common starting point...
When I inserted my already joined stick, its yellow LED was blinking (it was on the mesh that I had previously joined it to) and near bottom of the 'change networking settings' section it showed a nonzero operating channel and the correct operating PAN ID. It was ready to scan the mesh; just needed to change mode to Network Working mode and choose scan.
Just to get it 'unjoined', I changed the last digit of the writeable PAN ID field and 'wrote' it to the stick with the little pencil icon; now the LED stopped blinking and refreshing the operating channel and operating PAN ID fields turned both of them to '0'. When I went to 'Working Modes > Network Working Mode and choose 'Scan' I got a single green 'R' node (representing the stick) on the map with the exact same popup (with the MAC address of my stick) that you posted.
Next I deleted it from the left pane (the tiny 'x' in the blue box representing the radio deletes it), re-discovered it, then did 'Working modes' > 'Configuration working mode', then on the right pane chose 'Profile' < 'Create configuration profile' and saved it to a file, using the correct PAN ID (this also makes swapping PANS easier since you can just load pre-configured files).
I assumed that at this point it would start working, but no; no blinking yellow and same error popup as before. I vaguely recall this was when I stopped taking notes last time I went through this and just started trying stuff... so I then did 'Profile' > 'Apply configuration profile' and when the file open dialog box came up, I picked the profile I had just created and loaded it. This wrote the settings to the radio and the light began blinking.. it had joined the mesh. I think if you do this with the hub in 'Add device' mode, it will then join.. you should also be able to refresh those operating channel and PAN ID fields and verify the settings it is using (the tiny tail chasing icons refresh the fields).
Going through this just now made me remember thinking 'why did I have to load the profile when I just wrote all those same settings with the pencil icons?' but maybe that step just sets them up in a buffer to be saved to a file and doesn't really set them in the radio (though it clearly did change my stick from blinking to non-blinking via the pencil icon edit of the PAN ID)... anyway, it got my stick working again (at least to a previously joined hub).
I'm starting to drag now since its late on the east coast; if these steps don't kick your Xstick into joining, tomorrow I'll try again with my C-7 (it's never been joined to that hub before... it's unplugged in the parrot's room and we know better than to wake him up in the middle of the night lol)
This isn't working the same way for me...one thing I should note is that I haven't seen the yellow blinking light on the stick since I first inserted it and did the updates to put it into router mode. I didn't track exactly when it stopped blinking. I get the normal "found device" windows bloops when I remove/re-insert it, the stick responds to FW updates in XCTU, is found when I remove/re-add it via the small x/mag glass discover modules, etc.
I tried applying a "bad" extended PAN ID, saving that to a profile, then applied the profile w/the good PAN ID while hub was in pairing mode. No blinking, no reaction from the hub.
I've unplugged and re-plugged the stick, also shut down/restarted XCTU. Going to restart my computer now as well...but I'm clearly missing someting given the lack of any blinky-blinky (that's the technical term ) on the stick.
@Mayhem - do you get any blinking on your stick since you updated it to router mode?
Hey Tony, I found the XML file here in this post from @andydvsn in the original Xbee thread. Luckily he had the foresight to save the XML.
Actually found it while I was out walking the dogs, and we're leaving to go on a bike ride in a few minutes, so I can't do anything about it at this point, but I'm hoping this will help us out.
Good... that might do it. Sent you a PM with another idea; googling turned up a post with the key format entered as 0x5A6967426565416C6C69616E63653039 (pre-pended '0x' indicating hex format). That might be the way the key needs to be entered in the KY field. Possibly that's whats in the XML file...
My dear frustrated fellows. The only time I get blinkyblight is if I change it to a coordinator. Logically I suppose. And have done so a couple of time to prove it’s still alive.
Still not got any further than you chaps and off to Coombe Abbey for the wife’s birthday and our anniversary so any dabbling in the dark arts of the Operational Working & Functions of Unified Communication of Zigbee Stick
Or OWFUCZS as it’s known in the trade, after another parameter is inserted and dose nothing
Keep banging the rocks together chaps I’ll catch up with it tomorrow.
The key fix was after getting everything set up and the proper config loaded/applied, was re-applying the FW to the stick, and putting the hub in pairing mode...after the FW update completed the hub found the stick (joined it as a contact sensor initially, I changed that to type "Device") and scanning works and it is finding my stuff.
Tony gets a big check in the WIN column.
Off for Mother's day stuff now...gotta earn the WAF!
