aifreedom / balena-homebridge Goto Github PK

balenaCloud app for HomeBridge

License: Apache License 2.0

Shell 100.00%

balena-homebridge's Introduction

balena-homebridge

⚠️ I have switched to using the Official Homebridge Raspberry Pi Image ⚠️ As of 2020-07-03, I likely will not be updating this project any more. Please submit an issue if you want to take over maintaining this project.

balenaCloud application for HomeBridge

Setup

You can setup a balena-homebridge computer either remotely or locally. We recommend the remote method since it provides an ability to manage multiple IoT devices from a single dashboard.

Remote Setup

Create an account at balenaCloud.
Create an application at balenaCloud that is correct for your hardware.
Add a device to your application following the instructions provided by balena.
Clone or download this repo (or a fork of this repo) from GitHub.
Add the repo for your application to your working copy of this repo.
Once your device shows in the dashboard at balena, configure it:
1. Optionally create an environment variable HOMEKIT_PIN set to the value of your choosing in the form ###-##-### where # is the digits 0-9 or accept the default of 000-00-000
2. Optionally create an environment variable HOMEKIT_USER set to the value of your choosing in the form ##:##:##:##:##:## where # is the hexadecimal digits 0-9 or A-F or accept the default of 00:11:22:33:44:55
3. Optionally create an environment variable KEEP_CONFIG set to yes or no; if set to yes (the default if not specified), the config.json will be persisted across application restarts; if set to no, the config.json will be overwritten on your device everytime the application is restarted.
4. Optionally create an environment variable CONFIG_URL set to a URL that the desired config.json file can be downloaded from or accept the default value of an empty string which prevents the download from being attempted.
Push the contents of your repo towards balenaCloud to complete the installation and initial configuration of your Homebridge device.

Local Setup

TBD

balena-homebridge's People

Contributors

Stargazers

Watchers

Forkers

linusjun lucyan90 crashfrog

balena-homebridge's Issues

Allow config.json to be stored in Github

Other balena/Homebridge integrations in GitHub require that the Homebridge config.json file be stored in the repository and, barring a configuration change in the balena application will persistently replace config.json every time the application is (re)started.

This integration does not, but both models have benefits (this model can be reused without forking, the other model retains all configuration in GitHub).

To support retaining configuration in GitHub, this project needs to be able to retrieve, at application start, an updated config.json from a GitHub project.

Maintaining the package

Hi @rhwood , thank you for starting this project! I learned from your README that you are not going to maintain this package going forward. I've forked it at https://github.com/aifreedom/balena-homebridge/, made some changes and keep the packages (mostly homebridge and homebridge-config-ui-x) up-to-date. I'll continue to maintain this package.

An in-range update of homebridge is breaking the build 🚨

The dependency homebridge was updated from `0.4.48` to `0.4.49`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

homebridge is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ Travis CI - Branch: The build errored.

Commits

The new version differs by 5 commits.

724125d 0.4.49
50d9f38 Node.js 12 support (#2205)
eb66a55 Merge pull request #2164 from afharo/Resolve-custom-dir
87c8a7f Remove clashing vars names
29c59ea Resolve custom config path so plugins extracting it can work with it

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Willing to maintain the project

Hello Song,

Kudos to you for this great project. I am currently using it and would love to help with the upkeep!

Thanks,
Jacob

Any particular reason for switching away?

I just looked through the repo.
Do you have any particular reason for switching away from balena?

An in-range update of homebridge-lutron-caseta-smockle is breaking the build 🚨

The dependency homebridge-lutron-caseta-smockle was updated from `2.0.17` to `2.0.18`.