Rhasspy Wake Mycroft Precise Hermes
Implements hermes/hotword functionality from Hermes protocol using Mycroft Precise.
Requirements
- Python 3.7
- Mycroft Precise
- Expects
precise-enginein$PATH
- Expects
Installation
$ git clone https://github.com/rhasspy/rhasspy-wake-precise-hermes
$ cd rhasspy-wake-precise-hermes
$ ./configure
$ make
$ make install
Running
$ bin/rhasspy-wake-precise-hermes <ARGS>
Command-Line Options
usage: rhasspy-wake-precise-hermes [-h] [--model MODEL] [--engine ENGINE]
[--model-dir MODEL_DIR]
[--sensitivity SENSITIVITY]
[--trigger-level TRIGGER_LEVEL]
[--wakeword-id WAKEWORD_ID]
[--log-predictions]
[--udp-audio UDP_AUDIO UDP_AUDIO UDP_AUDIO]
[--host HOST] [--port PORT]
[--username USERNAME] [--password PASSWORD]
[--tls] [--tls-ca-certs TLS_CA_CERTS]
[--tls-certfile TLS_CERTFILE]
[--tls-keyfile TLS_KEYFILE]
[--tls-cert-reqs {CERT_REQUIRED,CERT_OPTIONAL,CERT_NONE}]
[--tls-version TLS_VERSION]
[--tls-ciphers TLS_CIPHERS]
[--site-id SITE_ID] [--debug]
[--log-format LOG_FORMAT]
optional arguments:
-h, --help show this help message and exit
--model MODEL Precise model file to use (.pb)
--engine ENGINE Path to precise-engine executable
--model-dir MODEL_DIR
Directories with Precise models
--sensitivity SENSITIVITY
Model sensitivity (default: 0.5)
--trigger-level TRIGGER_LEVEL
Activation threshold before prediction (default: 3)
--wakeword-id WAKEWORD_ID
Wakeword ID for model (default: use file name)
--log-predictions Log prediction probabilities for each audio chunk
(very verbose)
--udp-audio UDP_AUDIO UDP_AUDIO UDP_AUDIO
Host/port/siteId for UDP audio input
--host HOST MQTT host (default: localhost)
--port PORT MQTT port (default: 1883)
--username USERNAME MQTT username
--password PASSWORD MQTT password
--tls Enable MQTT TLS
--tls-ca-certs TLS_CA_CERTS
MQTT TLS Certificate Authority certificate files
--tls-certfile TLS_CERTFILE
MQTT TLS certificate file (PEM)
--tls-keyfile TLS_KEYFILE
MQTT TLS key file (PEM)
--tls-cert-reqs {CERT_REQUIRED,CERT_OPTIONAL,CERT_NONE}
MQTT TLS certificate requirements (default:
CERT_REQUIRED)
--tls-version TLS_VERSION
MQTT TLS version (default: highest)
--tls-ciphers TLS_CIPHERS
MQTT TLS ciphers to use
--site-id SITE_ID Hermes site id(s) to listen for (default: all)
--debug Print DEBUG messages to the console
--log-format LOG_FORMAT
Python logger format
Metadata
Release files for rhasspy-wake-precise-hermes 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rhasspy-wake-precise-hermes-0.3.0.tar.gz | 92.1 kB | Without provenance | Details for rhasspy-wake-precise-hermes-0.3.0.tar.gz |
Release files / rhasspy-wake-precise-hermes-0.3.0.tar.gz
| Download URL | rhasspy-wake-precise-hermes-0.3.0.tar.gz |
|---|---|
| Size | 92.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e777fc477c828362df07dfe3b3e4326fb1c54229a500f36d52e06af1b80a865
|
|
BLAKE2b-256 checksum How to use checksums |
2c61ea17bf9f2b4a7aa5517a5f333f29df8f0bec53222427c021e393ce7ed872
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.6.9
|
Security for rhasspy-wake-precise-hermes 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.