You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using an XBee connected via USB, and I'm having a hard time getting it to connect. There are a lot of settings that I can configure in XCTU, some of which seem to be reflected in ZigBeeNet and some that aren't. Are there any specific settings to get it to work?
At the very least, I need to switch it to API Mode in order to get Initialize() to work at all. After that, I'm able to attach DiscoveryExtension, but PermitJoin doesn't seem to have any effect, even though it returns SUCCESS. I'm also unable to connect anything, whether it's a Tradfri or another XBee.
Also, sometimes PanID is reset to 0x00, and other times it isn't.
The text was updated successfully, but these errors were encountered:
I have no experience with XBee, because I only own a Texas Instrument CC2531 USB dongle. But with that I have the same problems, that sometimes startup and pairing works and sometimes not. For me there are some problems at manufactures side, because they don't implement ZigBee standard correctly at all.
Because of that it is more than difficult to handle all problems are reported here. I am sorry that I can't help you, but maybe anyone else could help. Because of that I added question and help wanted tags
I'm using an XBee connected via USB, and I'm having a hard time getting it to connect. There are a lot of settings that I can configure in XCTU, some of which seem to be reflected in ZigBeeNet and some that aren't. Are there any specific settings to get it to work?
At the very least, I need to switch it to API Mode in order to get
Initialize()
to work at all. After that, I'm able to attachDiscoveryExtension
, butPermitJoin
doesn't seem to have any effect, even though it returns SUCCESS. I'm also unable to connect anything, whether it's a Tradfri or another XBee.Also, sometimes PanID is reset to 0x00, and other times it isn't.
The text was updated successfully, but these errors were encountered: