Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Z zigbee-dongle-kw2x
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Gianmarco Garrisi
  • zigbee-dongle-kw2x
  • Wiki
  • Home

Home · Changes

Page history
ggarrisi created page: home authored Apr 10, 2017 by Gianmarco Garrisi's avatar Gianmarco Garrisi
Hide whitespace changes
Inline Side-by-side
home.md 0 → 100644
View page @ 53ec9132
Trying to connect the ZigBee Dongle Texas Instruments CC2531 to the smart plug FlexGrid FlexPlug there were problems.
All the tests were done with the zigbee-gateway-server console, version 3.1.0.
With permit join set to enable the smart plug join the network and is added to the device list.
The plug generates repeatedly a message of the IdentifyCluster containing an IdentifyQueryCommand and send it broadcast.
I found that the library does not explicitly manage broadcast messages, so the message is received to all endpoints (by default the program creates 3 endpoints for the dongle, with different clusters on each), but, because only endpoint 1 has the Identify Cluster, when the message reaches the other endpoints an exception is thrown. The exception let the console usable but the long message that prints on the screen is annoying, so see issue #4.
Also noticed that changing the permit join parameter generates an unknown package, then a warning. Analyzing the packages I think that the unknown one is only some form of notification that the status changed, in fact the unknown frame is not generated if the join command is used without changing the status (e.g. join enable when permit join is already enabled). I don't have the certainty because the command ID of the package is not on the "Z-Stack Monitor and Test API" document.
Trying to send any command through the dongle goes on time-out.
The messages I tried to send are:
* Write and read message
*on and off messages
* IdentifyCommand
* IdentifyQueryResponse
\ No newline at end of file
Clone repository
  • bug dongle ti
  • clusters and endpoins
  • differences nxp ti
  • Home
  • long term plan
  • setup
  • short term plan
  • start
  • state of impl