node-red-nodes/hardware/makey
Sam Machin 2d28a2304f
Update package.jsons for mono-repo (#851)
Update the package.json for each node to point to the directory within the repo that hosts the code for the package in question.  as per https://docs.npmjs.com/cli/v7/configuring-npm/package-json#repository
2021-11-02 15:22:30 +00:00
..
42-makey.html Update licenses and packages for all nodes 2016-11-06 20:26:19 +00:00
42-makey.js Re-lint a load of nodes 2017-01-29 17:45:44 +00:00
42-makey.rules More tweaks to makey node - colours, jshint fixes, icons, readme etc. 2014-07-18 17:04:22 +01:00
LICENSE Update licenses and packages for all nodes 2016-11-06 20:26:19 +00:00
README.md update hardware nodes info style 2016-03-02 13:27:52 +00:00
package.json Update package.jsons for mono-repo (#851) 2021-11-02 15:22:30 +00:00

README.md

node-red-node-makeymakey

A Node-RED node to read from a MakeyMakey input device.

Install

Run the following command in your Node-RED user directory - typically ~/.node-red

npm install node-red-node-makeymakey

Pre-reqs

As this requires an underlying npm this also requires it's pre-reqs, see Node-hid npm for more details.

  • libudev-dev (Linux only)
  • libusb-1.0-0-dev (Ubuntu versions missing libusb.h only)

As this uses the raw HID strea mit often requires you to run Node-RED as root, unless you have correct priviliges.

Usage

Provides "keyboard" like input from a MakeyMakey device.

This uses the hidstream npm module that by default only supports the basic keyboard keys and NOT the mouse inputs, fn keys, keypad keys, cursor keys etc. This means that the extra mouse emulation jumpers won't work.

The MakeyMakey can of course be re-programmed to re-assign the keys - but this node doesn't know about that...

Known Issues

  1. Every now and then something causes the MakeyMakey HID to become detached (lose focus) from this app and re-attach to another (the in focus) app... whereupon the emulated keys will end up in the wrong window... - Any ideas on how to stop this would be greatly appreciated - but I suspect it's a fundamental issue with the MakeyMakey pretending to be a HID.

  2. Default usage is such that you have to run as root. On Debian based systems you can copy the file 42-makey.rules to the /etc/udev/rules.d/ folder - this should let anyone then access the MakeyMakey. To restart udev use

    sudo udevadm control --reload-rules