Highly configurable MQTT map interface
It is still possible to define types as functions (Buffer => string for state topics, string => Buffer for command topics). Otherwise types have from and to properties. (Fixes #101) |
||
|---|---|---|
| config | ||
| css | ||
| src | ||
| types | ||
| .babelrc | ||
| .eslintrc.js | ||
| .flowconfig | ||
| .gitignore | ||
| .travis.yml | ||
| index.ejs | ||
| package.json | ||
| README.md | ||
| shell.nix | ||
| travis-upload-artifacts.sh | ||
| travis.sh | ||
| webpack.config.js | ||
| yarn.lock | ||
MQTT Control Map
Development / Configuration
- run
yarnto install all dependencies. - run
yarn watch CONFIGto run a local build server that automatically builds your the mqtt control map for the given CONFIG everytime something changes. - run
yarn dev CONFIGto create just a single build of the mqtt control map for the given config. - run
yarn build CONFIGto generate all files for production use.
Documentation
The documentation can be found in our mqtt-control-map wiki.