
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
node-red-contrib-precise-wakeword
Advanced tools
a node-red integration of the precise wakeword listener
A node-red integration of the mycroft precise wake word engine for Linux.
To install this node either search for it in the Node-RED pallete manager or install it from the Node-RED folder (in most cases ~/.node-red
)
using either:
npm install node-red-contrib-precise-wakeword
to install the module from npm or use:
npm install johanneskropf/node-red-contrib-precise-wakeword
to install it directly from the repository (requires git to be installed).
This node needs the precise-engine binary installed for it to work. There is two ways to install this:
Which option you choose largely depends on which wake-word model you want to run. The engine can only run models that were trained on the same or older version as the engine itself. If you want to train your own models you will most likely have to opt for the source install as this way you can choose the same branch that was used for training.
To use the node in a first step you will have to create a new configuration. This configuration represents the precise-engine and you will have to enter the
absolut path to the engine binary in it. If you choose the binary install this will be .../precise-engine/precise-engine
relative to the path that you unpacked
the binary in. If you choose the source install it will be .../mycroft-precise/.venv/bin/precise-engine
relative to your choosen cloning destination.
After adding the configuration you now have to enter the path to a model file in the nodes config ui (this file will have the ending .pb).
To start you can download the official hey-mycroft-2 wake-word model .pb and .pb.params file from here.
For each model you want to use the precise-engine will always need both the .pb and the .pb.params file in the same path/folder.
Once you have both the engine and model files set up you need to feed raw audio buffer chunks to the precise-wake nodes input.
To do this use for example one of the multiple microphone nodes available for Node-RED:
This stream of audio needs to be in the following format:
Once the input has started the precise-engine will take anywhere from 10-30 seconds to start up and than listen for the wake-word. When it detects the wake-word it will send a message to its first output that has several usefull properties:
{
"keyword":"hey-mycroft-2",
"timestamp":1612953501615,
"score":0.6189599310573979,
"threshold":0.5
}
To stop the node stop the stream of raw audio buffers and the node will automatically stop.
msg
property the node listen on for the audio stream.msg
property the node sends the message on a positive match onmsg
property the node listens on for control messagesThe node supports several control messages to control its behaviour at runtime. These messages need to be sent as a string in the configured control
property of a input msg
object:
You can train your own model with a precise source install. be warned this process is quite involved. Here are some links that might help you:
If you are looking for an alternative to quickly use personal wake-words without the training process have a look at node-red-contrib-personal-wake-word. This will give you an easy start but will of course not work as a universal wake-word for differnt speakers and will be less noise resistant as it uses a much more simplistic approach.
Precise right now only runs on Linux distributions and on hardware thats at least as fast as the Raspberry Pi 3a+.
FAQs
a node-red integration of the precise wakeword listener
The npm package node-red-contrib-precise-wakeword receives a total of 6 weekly downloads. As such, node-red-contrib-precise-wakeword popularity was classified as not popular.
We found that node-red-contrib-precise-wakeword demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.