npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

chickadee

v1.7.2

Published

Contextual associations store and API. We believe in an open Internet of Things.

Downloads

307

Readme

chickadee

A contextual associations store and API for the IoT

chickadee is a contextual associations store and a core module of Pareto Anywhere open source middleware for context-aware physical spaces.

Specifically, chickadee associates wireless device identifiers with metadata such as a URL, a tag, a directory, and/or a position. Additionally, it provides a contextual API when coupled with live data from a barnacles instance and optional chimps instance. And finally, it provides an API to store and retrieve GeoJSON features. chickadee can run standalone, although it is usually run together with its peer modules.

Installation

npm install chickadee

Hello chickadee!

npm start

Browse to localhost:3001/associations/001bc50940810000/1 to see if there are any associations for the device with EUI-64 identifier 00-1b-c5-09-40-81-00-00. By default, this should return Not Found. Interact with chickadee through the REST API described below.

REST API

chickadee's REST API includes the following two base routes:

  • /associations for retrieving/specifying metadata associations with devices
  • /context for retrieving the context of specific devices
  • /features for retrieving/specifying GeoJSON features

GET /associations/{id}/{type}

Retrieve the associations for the given device id and type.

Example request

| Method | Route | Content-Type | |:-------|:---------------------------------|:-----------------| | GET | /associations/001bc50940810000/1 | application/json |

Example response

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3001/associations/001bc50940810000/1"
    }
  },
  "associations": {
    "001bc50940810000/1": {
      "url": "https://www.reelyactive.com",
      "directory": "parc:office",
      "tags": [ "new", "improved" ],
      "position": [ 0.0, 0.0 ]
    }
  }
}

Single-property routes

The following routes are also supported:

  • GET /associations/{id}/{type}/url
  • GET /associations/{id}/{type}/directory
  • GET /associations/{id}/{type}/tags
  • GET /associations/{id}/{type}/position

In each case, the response is as above, but includes only the property specified by the route.

PUT /associations/{id}/{type}

Replace, or create, the associations for the given device id and type.

Example request

| Method | Route | Content-Type | |:-------|:---------------------------------|:-----------------| | PUT | /associations/001bc50940810000/1 | application/json |

{
  "url": "https://www.reelyactive.com",
  "directory": "parc:office",
  "tags": [ "new", "improved" ],
  "position": [ 0.0, 0.0 ]
}

Example response

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3001/associations/001bc50940810000/1"
    }
  },
  "associations": {
    "001bc50940810000/1": {
      "url": "https://www.reelyactive.com",
      "directory": "parc:office",
      "tags": [ "new", "improved" ],
      "position": [ 0.0, 0.0 ]
    }
  }
}

Single-property routes

The following routes are also supported:

  • PUT /associations/{id}/{type}/url
  • PUT /associations/{id}/{type}/directory
  • PUT /associations/{id}/{type}/tags
  • PUT /associations/{id}/{type}/position

In each case, the request and response are as above, however only the property specified by the route will be considered in the request.

DELETE /associations/{id}/{type}

Remove the associations for the given device id and type.

Example request

| Method | Route | Content-Type | |:-------|:---------------------------------|:-----------------| | DELETE | /associations/001bc50940810000/1 | application/json |

Example response

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3001/associations/001bc50940810000/1"
    }
  }

Single-property routes

The following routes are also supported:

  • DELETE /associations/{id}/{type}/url
  • DELETE /associations/{id}/{type}/directory
  • DELETE /associations/{id}/{type}/tags
  • DELETE /associations/{id}/{type}/position

In each case, the response is as above.

GET /context

Retrieve the context of all active devices.

Example request

| Method | Route | Content-Type | |:-------|:---------|:-----------------| | GET | /context | application/json |

Example response

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3001/context"
    }
  },
  "devices": {
    "fee150bada55/2": {
      "nearest": [
        {
          "device": "001bc50940810000/1",
          "rssi": -72
        },
        {
          "device": "001bc50940820000/1",
          "rssi": -85
        }
      ],
      "dynamb": {
        "timestamp": 1624714123456,
        "batteryPercentage": 67,
        "acceleration": [ -0.15625, -0.94921875, 0.109375 ]
      },
      "spatem": {
        "timestamp": 1624714123456,
        "type": "position",
        "data": {
          "type": "FeatureCollection",
          "features": [
            {
              "type": "Feature",
              "properties": {
                "isDevicePosition": true,
                "positioningEngine": "External"
              },
              "geometry": {
                "type": "Point",
                "coordinates": [ -73.57123, 45.50883 ]
              }
            }
          ]
        }
      },
      "statid": {
        "uuids": [ "feaa" ],
        "uri": "https://sniffypedia.org/Product/Google_Eddystone/",
        "deviceIds": [ "7265656c652055554944/000000000d09" ]
      },
      "url": "https://www.reelyactive.com/team/obelix/",
      "tags": [ "animal" ]
    },
    "001bc50940810000/1": {
      "directory": "parc:office",
      "tags": [ "reelceiver" ]
    },
    "001bc50940820000/1": {
      "directory": "parc:lounge",
      "tags": [ "OiO" ]
    }
  }
}

GET /context/device/{id}/{type}

Retrieve the context of the active device with the given id and type.

Example request

| Method | Route | Content-Type | |:-------|:-------------------------------|:-----------------| | GET | /context/device/fee150bada55/2 | application/json |

Example response

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3001/context/device/fee150bada55/2"
    }
  },
  "devices": {
    "fee150bada55/2": {
      "nearest": [
        {
          "device": "001bc50940810000/1",
          "rssi": -72
        },
        {
          "device": "001bc50940820000/1",
          "rssi": -85
        }
      ],
      "dynamb": {
        "timestamp": 1624714123456,
        "batteryPercentage": 67,
        "acceleration": [ -0.15625, -0.94921875, 0.109375 ]
      },
      "spatem": {
        "timestamp": 1624714123456,
        "type": "position",
        "data": {
          "type": "FeatureCollection",
          "features": [
            {
              "type": "Feature",
              "properties": {
                "isDevicePosition": true,
                "positioningEngine": "External"
              },
              "geometry": {
                "type": "Point",
                "coordinates": [ -73.57123, 45.50883 ]
              }
            }
          ]
        }
      },
      "statid": {
        "uuids": [ "feaa" ],
        "uri": "https://sniffypedia.org/Product/Google_Eddystone/",
        "deviceIds": [ "7265656c652055554944/000000000d09" ]
      },
      "url": "https://www.reelyactive.com/team/obelix/",
      "tags": [ "animal" ]
    },
    "001bc50940810000/1": {
      "directory": "parc:office",
      "tags": [ "reelceiver" ]
    },
    "001bc50940820000/1": {
      "directory": "parc:lounge",
      "tags": [ "OiO" ]
    }
  }
}

GET /context/directory/{directory}

Retrieve the context of all active devices with (and within) the given directory. As directories are hierarchical, specifying the directory parc would include all subdirectories such as parc:office and parc:lounge.

Example request

| Method | Route | Content-Type | |:-------|:------------------------|:-----------------| | GET | /context/directory/parc | application/json |

Example response

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3001/context/directory/parc"
    }
  },
  "devices": {
    "fee150bada55/2": {
      "nearest": [
        {
          "device": "001bc50940810000/1",
          "rssi": -72
        },
        {
          "device": "001bc50940820000/1",
          "rssi": -85
        }
      ],
      "dynamb": {
        "timestamp": 1624714123456,
        "batteryPercentage": 67,
        "acceleration": [ -0.15625, -0.94921875, 0.109375 ]
      },
      "spatem": {
        "timestamp": 1624714123456,
        "type": "position",
        "data": {
          "type": "FeatureCollection",
          "features": [
            {
              "type": "Feature",
              "properties": {
                "isDevicePosition": true,
                "positioningEngine": "External"
              },
              "geometry": {
                "type": "Point",
                "coordinates": [ -73.57123, 45.50883 ]
              }
            }
          ]
        }
      },
      "statid": {
        "uuids": [ "feaa" ],
        "uri": "https://sniffypedia.org/Product/Google_Eddystone/",
        "deviceIds": [ "7265656c652055554944/000000000d09" ]
      },
      "url": "https://www.reelyactive.com/team/obelix/",
      "tags": [ "animal" ]
    },
    "001bc50940810000/1": {
      "directory": "parc:office",
      "tags": [ "reelceiver" ]
    },
    "001bc50940820000/1": {
      "directory": "parc:lounge",
      "tags": [ "OiO" ]
    }
  }
}

GET /context/tag/{tag}

Retrieve the context of all active devices with the given tag.

Example request

| Method | Route | Content-Type | |:-------|:--------------------|:-----------------| | GET | /context/tag/animal | application/json |

Example response

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3001/context/tag/animal"
    }
  },
  "devices": {
    "fee150bada55/2": {
      "nearest": [
        {
          "device": "001bc50940810000/1",
          "rssi": -72
        },
        {
          "device": "001bc50940820000/1",
          "rssi": -85
        }
      ],
      "dynamb": {
        "timestamp": 1624714123456,
        "batteryPercentage": 67,
        "acceleration": [ -0.15625, -0.94921875, 0.109375 ]
      },
      "spatem": {
        "timestamp": 1624714123456,
        "type": "position",
        "data": {
          "type": "FeatureCollection",
          "features": [
            {
              "type": "Feature",
              "properties": {
                "isDevicePosition": true,
                "positioningEngine": "External"
              },
              "geometry": {
                "type": "Point",
                "coordinates": [ -73.57123, 45.50883 ]
              }
            }
          ]
        }
      },
      "statid": {
        "uuids": [ "feaa" ],
        "uri": "https://sniffypedia.org/Product/Google_Eddystone/",
        "deviceIds": [ "7265656c652055554944/000000000d09" ]
      },
      "url": "https://www.reelyactive.com/team/obelix/",
      "tags": [ "animal" ]
    },
    "001bc50940810000/1": {
      "directory": "parc:office",
      "tags": [ "reelceiver" ]
    },
    "001bc50940820000/1": {
      "directory": "parc:lounge",
      "tags": [ "OiO" ]
    }
  }
}

POST /features

Create the GeoJSON feature, which will return a unique id, which is a random RFC 4122 version 4 UUID, without dashes.

Example request

| Method | Route | Content-Type | |:-------|:-----------------------------------------------|:-----------------| | POST | /features | application/json |

{
  "type": "Feature",
  "properties": { "name": "triangle" },
  "geometry": {
    "type": "Polygon",
    "coordinates": [ [ [ 0, 1 ], [ 1, 0 ], [ 0, 0 ], [ 0, 1 ] ] ]
  }
}

Example response

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3001/features/"
    }
  },
  "features": {
    "df52b802f4054bdb815102be1d76f8ab": {
      "type": "Feature",
      "id": "df52b802f4054bdb815102be1d76f8ab",
      "properties": { "name": "triangle" },
      "geometry": {
        "type": "Polygon",
        "coordinates": [ [ [ 0, 1 ], [ 1, 0 ], [ 0, 0 ], [ 0, 1 ] ] ]
      }
    }
  }
}

GET /features/{id}

Retrieve the GeoJSON feature with for the given id.

Example request

| Method | Route | Content-Type | |:-------|:-----------------------------------------------|:-----------------| | GET | /features/df52b802f4054bdb815102be1d76f8ab | application/json |

Example response

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3001/features/df52b802f4054bdb815102be1d76f8ab"
    }
  },
  "features": {
    "df52b802f4054bdb815102be1d76f8ab": {
      "type": "Feature",
      "id": "df52b802f4054bdb815102be1d76f8ab",
      "properties": { "name": "triangle" },
      "geometry": {
        "type": "Polygon",
        "coordinates": [ [ [ 0, 1 ], [ 1, 0 ], [ 0, 0 ], [ 0, 1 ] ] ]
      }
    }
  }
}

DELETE /features/{id}

Remove the GeoJSON feature with the given id.

Example request

| Method | Route | Content-Type | |:-------|:-----------------------------------------------|:-----------------| | DELETE | /features/df52b802f4054bdb815102be1d76f8ab | application/json |

Example response

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3001/features/df52b802f4054bdb815102be1d76f8ab"
    }
  }

Socket.IO

When initialised with a Socket.IO server as an option, chickadee supports the following namespace:

  • /context/device/{id}/{type}

When a change in context for the given device is detected, a devices event is emitted. For an example of the devices JSON structure, see the sample response of the /context REST API above.

chickadee logo

What's in a name?

The Cornell Lab of Ornithology explains: "The Black-Capped Chickadee hides seeds and other food items to eat later. Each item is placed in a different spot and the chickadee can remember thousands of hiding places." Not only does it have an outstanding associative memory, it is also "almost universally considered cute thanks to its oversized round head, tiny body, and curiosity about everything, including humans."

If you were entrusting a bird to associate your wireless device with your online stories you'd want it to be cute and friendly enough to eat out of your hand, right? We could have named this package Clark's Nutcracker, the bird with arguably the best associative memory, but the whole nut-cracking thing doesn't inspire the same level of friendliness now does it?

One more fun fact that we feel compelled to pass along: "Every autumn Black-capped Chickadees allow brain neurons containing old information to die, replacing them with new neurons so they can adapt to changes in their social flocks and environment even with their tiny brains." Wow, that's database efficiency that we can aspire to!

Project History

chickadee v1.0.0 was released in July 2019, superseding all earlier versions, the latest of which remains available in the release-0.4 branch and as [email protected] on npm.

chickadee v1.4.0 migrates to ESMapDB from NeDB. If upgrading from a previous version, any stored associations will need to be recreated.

Contributing

Discover how to contribute to this open source project which upholds a standard code of conduct.

Security

Consult our security policy for best practices using this open source software and to report vulnerabilities.

License

MIT License

Copyright (c) 2015-2024 reelyActive

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.