A NodeJS plugin to enable the LaCrosse protocol using a JeeLink USB adapter in Homebridge. The plugin checks the JeeLink device for
options.interval seconds and will then suspend for the same interval. The history is saved using the FakeGato module and can be accessed using the Elegato Eve app.
StateThis plugin is in early development. But it does work as of v0.2.0. Also: it should save a history of entries for the Elegato Eve app.
InstallationThe plugin can be installed using the
homebridge-ui-x plugin or by running the following command in the homebridge home folder:
npm install homebridge-jeelink
AlpineIf you're (like me) running Homebridge in the Alpine docker container you'll probably have to add some additional packages as followed (you may skip the sudo if not applicable). See the
serialport package for details:
# If you don't have node/npm already, add that first
sudo apk add --no-cache nodejs
# Add the necessary build and runtime dependencies
sudo apk add --no-cache make gcc g++ linux-headers udev
Homebridge Platform Plugin TemplateThis is a template Homebridge platform plugin and can be used as a base to help you get started developing your own plugin.
This template should be use in conjunction with the developer documentation. A full list of all supported service types, and their characteristics is available on this site.
Clone As TemplateClick the link below to create a new GitHub Repository using this template, or click the Use This Template button above.
Setup Development EnvironmentTo develop Homebridge plugins you must have Node.js 12 or later installed, and a modern code editor such as VS Code. This plugin template uses TypeScript to make development easier and comes with pre-configured settings for VS Code and ESLint. If you are using VS Code install these extensions:
Install Development DependenciesUsing a terminal, navigate to the project folder and run this command to install the development dependencies:
Update package.jsonOpen the
package.json and change the following attributes:
name- this should be prefixed with
@username/homebridge-and contain no spaces or special characters apart from a dashes
displayName- this is the "nice" name displayed in the Homebridge UI
repository.url- Link to your GitHub repo
bugs.url- Link to your GitHub repo issues page
When you are ready to publish the plugin you should set
private to false, or remove the attribute entirely.
Update Plugin DefaultsOpen the
src/settings.ts file and change the default values:
PLATFORM_NAME- Set this to be the name of your platform. This is the name of the platform that users will use to register the plugin in the Homebridge
PLUGIN_NAME- Set this to be the same name you set in the
config.schema.json file and change the following attribute:
pluginAlias- set this to match the
PLATFORM_NAMEyou defined in the previous step.
src directory and put the resulting code into the
npm run build
Link To HomebridgeRun this command so your global install of Homebridge can discover the plugin in your development environment:
You can now start Homebridge, use the
-D flag so you can see debug log messages in your plugin:
Watch For Changes and Build AutomaticallyIf you want to have your code compile automatically as you make changes, and restart Homebridge automatically between changes you can run:
npm run watch
This will launch an instance of Homebridge in debug mode which will restart every time you make a change to the source code. It will load the config stored in the default location under
~/.homebridge. You may need to stop other running instances of Homebridge while using this command to prevent conflicts. You can adjust the Homebridge startup command in the
Customise PluginYou can now start customising the plugin template to suit your requirements.
src/platform.ts- this is where your device setup and discovery should go.
src/platformAccessory.ts- this is where your accessory control logic should go, you can rename or create multiple instances of this file for each accessory type you need to implement as part of your platform plugin. You can refer to the developer documentation to see what characteristics you need to implement for each service type.
config.schema.json- update the config schema to match the config you expect from the user. See the Plugin Config Schema Documentation.
Versioning Your PluginGiven a version number
PATCH, such as
1.4.3, increment the:
- MAJOR version when you make breaking changes to your plugin,
- MINOR version when you add functionality in a backwards compatible manner, and
- PATCH version when you make backwards compatible bug fixes.
You can use the
npm version command to help you with this:
# major update / breaking changes
npm version major
# minor update / new features
npm version update
# patch / bugfixes
npm version patch
Publish PackageWhen you are ready to publish your plugin to npm, make sure you have removed the
private attribute from the
package.json file then run:
If you are publishing a scoped plugin, i.e.
@username/homebridge-xxx you will need to add
--access=public to command the first time you publish.
Publishing Beta VersionsYou can publish beta versions of your plugin for other users to test before you release it to everyone.
# create a new pre-release version (eg. 2.1.0-beta.1)
npm version prepatch --preid beta
# publsh to @beta
npm publish --tag=beta
Users can then install the beta version by appending
@beta to the install command, for example:
sudo npm install -g homebridge-example-plugin@beta