Community Hass.io Add-on: Homebridge

Installation Home Assistant OS
,
61

No worries.

Just to check if I’m understanding, you can actually select the homebridge version by specifying it as a plugin inside the hassio add-on installed, homebridge instance itself?

Regarding the version, you’re right that it hasn’t been released. But on the main repository code, the version number has already been bumped

https://github.com/nfarina/homebridge/commit/47a683a2f23b57aa85c09c475665b9fdcab9c478

and the homebridge-zp developer already requires it:

In any case, what you’ve told me should help me solve my problem, by just pointing to an older release of the homebridge-zp plugin. I didn’t know this was possible.

Thanks for the help!

62

Having problems with the homebridge-platform-wemo plug-in…

Error: Plugin /usr/lib/node_modules/homebridge-platform-wemo requires a HomeBridge version of >=0.4.29 which does not satisfy the current HomeBridge version of 0.4.28. You may need to upgrade your installation of HomeBridge.

I posted an issue for the plug-in as it seems to require 4.29 which is not yet released?

–fyi

63

There are a couple of plugins floating around GitHub that have this issue and there is nothing I can do to solve it. Since the release does not exist. Installing the master/development version of Homebridge is not something I am willing to do.

64

That is a good suggestion!

I’ve created an issue on the GitHub project to implement this change.

65

Sorry for confusion. I posted an issue to the owner of the homebridge plug-in. I posted above just for your and others awareness of the issue.

https://github.com/rudders/homebridge-platform-wemo/issues/118

1 Like
66

Owner of the homebridge-platform-wemo plugin says

While the releases tab is a good indication of the current release, it requires the developer to tag the release and push those tags to github…however, that can be easily overlooked.

The best source of truth is looking at the npmjs page as that is what has been deployed.

And points to the following, which does show 4.29 as most current release:

He won’t directly loosen the requirement as he is addressing other issues that require 4.29.

The latest version wemo-client requires node version 6 or higher. Prior to homebridge version 0.4.29, errors relating to incorrect node version weren’t displayed correctly. This is an attempt to prevent support requests as to why stuff is no longer working.

Maybe we’re stuck in between these releases until 4.29 is tagged properly?

67

The version of Homebridge was published on NPM, but not on GitHub. That is what went wrong in the communication. I will upgrade to 0.4.29.

Will be included in the next release of the add-on.

1 Like
68

:tada: Add-on: Homebridge v2.1.1

Full Changelog

Changed

  • Upgraded Homebridge to v0.4.29

This update is now available in your Hass.io panel.

1 Like
69

homebridge-platform-wemo loads and works perfectly again. Thanks for the update.

1 Like
70

You are welcome sir :sunny:

71

currently getting
2017-10-31 19:09:33.253637 INFO AppDaemon Version 2.1.11 starting
2017-10-31 19:09:33.254405 INFO Configuration read from: /config/appdaemon/appdaemon.yaml
2017-10-31 19:09:33.449256 INFO Starting Apps
2017-10-31 19:09:33.631057 INFO Got initial state
2017-10-31 19:09:33.633283 INFO Loading Module: /config/appdaemon/apps/hello.py
2017-10-31 19:09:33.636854 INFO Loading Object hello_world using class HelloWorld from module hello
2017-10-31 19:09:34.003538 INFO hello_world: Hello from AppDaemon
2017-10-31 19:09:34.008832 INFO hello_world: You are now ready to run Apps!
2017-10-31 19:09:34.009567 INFO App initialization complete
2017-10-31 19:09:34.011012 INFO Starting dashboard
2017-10-31 19:09:34.030363 INFO API is disabled
2017-10-31 19:09:34.045662 INFO Connected to Home Assistant 0.56.2
on start but as soon as I go to 10.0.1.44:5050 i get the same error

config is

AppDaemon:
  logfile: STDOUT
  errorfile: STDERR
  threads: 10
  app_dir: /config/appdaemon/apps
HASS:
  ha_key: !secret home_assistant_key
  ha_url: http://10.0.1.44:8123
HADashboard:
  dash_url: http://10.0.1.44:5050
  dash_dir: /config/appdaemon/dashboards
  dash_password: !secret home_assistant_key


# Apps
hello_world:
  module: hello
  class: HelloWorld
72

Hi,

I am having some trouble with the Homebridge after upgrading to DuckDNS/LetsEncrypt for Google home support. I have changed the “host” line from the 172.xxx.xxx.xx address to my new duckdns.org one; but it will not load and I end up with this message at the end of the addon start:

Registering new address record for fe80::42:6cff:fe91:6777 on hassio.*.
Registering new address record for 172.30.32.1 on hassio.*.
Registering new address record for fe80::ca0d:3da0:ff34:a5d3 on eth0.*.
Registering new address record for 192.168.86.113 on eth0.*.
Server startup complete. Host name is hassio.local. Local service cookie is 2457660850.
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>
[2017-11-5 10:24:42] Loaded plugin: homebridge-homeassistant
[2017-11-5 10:24:42] Registering platform 'homebridge-homeassistant.HomeAssistant'
[2017-11-5 10:24:42] ---
[2017-11-5 10:24:42] Loaded config.json with 0 accessories and 1 platforms.
[2017-11-5 10:24:42] ---
[2017-11-5 10:24:42] Loading 1 platforms...
[2017-11-5 10:24:42] [HomeAssistant] Initializing HomeAssistant platform...
[2017-11-5 10:24:42] [HomeAssistant] Fetching HomeAssistant devices.
[2017-11-5 10:24:42] Loading 0 accessories...

What would I have to change to get this working again?

Thanks,

73

Hi,

How did you get Homebridge and Letsencrypt/DuckDNS working exactly? I 'm trying to do the same thing after just installing the duckdns/letsencrypt plugin…

Thanks,

74

@derrick1985 Please follow this part of the manual:

You can instruct Homebridge to have a direct/internal connection with Home Assistant.

1 Like
75

Thanks as always. Did not see that at all the first time around configuring Homebridge. Made the chance; rebooted and is working flawlessly. Took a little longer than usual to start; but it works.

Thanks again!

1 Like
76

Trouble with Homebridge Add-on

I have run into an issue with the Homebridge add-on and I am at a loss to fix it now. Returned from a trip and every device in my Home app showed “No Response” on my iPhone restarted the add-on, cleared out the persist directory, etc. removed the bridge from Home and added it back. Works for a couple of hours and then it’s back to no response. Sometimes it will be working on my iPad and won’t be on my iPhone. but as soon as I restart the service, it is back to not working all over again on all devices. Only way to get the devices to respond again that I have found is to remove homebridge and then add it back. Below are the only errors I see but I have zero idea how to fix. This is a HASS.IO install with only SSH and homebridge add-ons. Any ideas?

No service file found in /etc/avahi/services.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Joining mDNS multicast group on interface hassio.IPv4 with address 172.30.32.1.
New relevant interface hassio.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.2.15.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for 172.30.32.1 on hassio.IPv4.
Registering new address record for 192.168.2.15 on eth0.IPv4.
77

:tada: Add-on: Homebridge v2.1.2

Full Changelog

Changed

  • Upgraded Homebridge to v0.4.33
  • Upgraded homebridge-homeassistant to v3.0.2

Removed

  • Removes repository.json to prevent user to install wrong repo
  • Removes Gratipay from README, since it is EOL

This update is now available in your Hass.io panel.

1 Like
78

Hey guys,

I am a total noob at this but am committed to figuring it out and making Homebridge work for my needs. I am having a problem understanding a full step by step of adding a plug in from the npm site. I really need to get my Harmony Hub activities into the HomeKit universe so that I can tie in my Wemo switches. I found this plug in: https://github.com/kraigm/homebridge-harmonyhub
According to their instructions I added this to the file in my home assistant add-on:

{
  "log_level": "info",
  "avahi_interfaces": "",
  "avahi_hostname": "",
  "avahi_domainname": "local",
  "enable_ipv6": true,
  "packages": [],
  "init_commands": [],
  "plugins": [
    "homebridge-harmonyhub"
  ]
}

Then I went in to the config.json file and added this:

{
  "bridge": {
"name": "Home Assistant",
"username": "B8:27:EB:11:98:36”,
"port": 51826,
"pin": "949-33-316"
  },
  "description": "Homebridge for Home Assistant",
  "accessories": [],
  "platforms": [
{
  "platform": "HomeAssistant",
  "name": "HomeAssistant",
  "host": "http://hassio/homeassistant",
  "password": "",
  "default_visibility": "visible",
  "supported_types": [
    "automation",
    "binary_sensor",
    "climate",
    "cover",
    "device_tracker",
    "fan",
    "group",
    "input_boolean",
    "light",
    "lock",
    "media_player",
    "remote",
    "scene",
    "script",
    "sensor",
    "switch",
    "vacuum"
  ],
  "logging": true,
  "verify_ssl": true
}
  ]
}
{
  "name": "homebridge-harmonyhub",
  "description": "Logitech Harmony Hub plugin for HomeBridge",
  "version": "0.2.1",
  "repository": {
"type": "git",
"url": "git://github.com/kraigm/homebridge-harmonyhub.git"
  },
  "license": "ISC",
  "preferGlobal": true,
  "keywords": [
"homebridge-plugin"
  ],
  "engines": {
"node": ">=0.12.0",
"homebridge": ">=0.3.1"
  },
  "dependencies": {
"bluebird": "^3.3.4",
"debug": "^2.2.0",
"harmonyhubjs-client": "^1.1.6",
"harmonyhubjs-discover": "^1.0.2",
"inherits": "^2.0.1",
"queue": "^3.1.0",
"lodash": "^4.6"
  }
}

But it isn’t working and now the Homebridge add-on requires me to start it every 5 minutes and isn’t discoverable in HomeKit.

I’m sorry but I just can’t figure out where a good tutorial is for this and I’ve been looking for like 20 straight hours!

Thanks in advance

79 
This is what I get in the Home Assistant add-on log:

  │   │ │   └── [email protected] 
  │   │ └─┬ [email protected] 
  │   │   ├── [email protected] 
  │   │   ├── [email protected] 
  │   │   ├── [email protected] 
  │   │   ├── [email protected] 
  │   │   ├── [email protected] 
  │   │   ├── [email protected] 
  │   │   └── [email protected] 
  │   ├── [email protected] 
  │   ├── [email protected] 
  │   ├── [email protected] 
  │   ├─┬ [email protected] 
  │   │ └── [email protected] 
  │   ├── [email protected] 
  │   ├── [email protected] 
  │   ├── [email protected] 
  │   ├── [email protected] 
  │   ├── [email protected] 
  │   ├─┬ [email protected] 
  │   │ └── [email protected] 
  │   ├── [email protected] 
  │   └── [email protected] 
  ├── [email protected] 
  ├── [email protected] 
  ├── [email protected] 
  └── [email protected] 
[cont-init.d] 82-user-plugins.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
starting version 3.2.2
Found user 'avahi' (UID 86) and group 'avahi' (GID 86).
Successfully dropped root privileges.
avahi-daemon 0.6.32 starting up.
WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Successfully called chroot().
Successfully dropped remaining capabilities.
No service file found in /etc/avahi/services.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
*** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Joining mDNS multicast group on interface hassio.IPv6 with address fe80::42:89ff:fec8:87a9.
New relevant interface hassio.IPv6 for mDNS.
Joining mDNS multicast group on interface hassio.IPv4 with address 172.30.32.1.
New relevant interface hassio.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv6 with address fe80::e54b:d36e:a7f1:ce26.
New relevant interface eth0.IPv6 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.0.41.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::42:89ff:fec8:87a9 on hassio.*.
Registering new address record for 172.30.32.1 on hassio.*.
Registering new address record for fe80::e54b:d36e:a7f1:ce26 on eth0.*.
Registering new address record for 10.0.0.41 on eth0.*.
Server startup complete. Host name is hassio.local. Local service cookie is 3200355512.
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>
[2017-11-16 08:52:57] Loaded plugin: homebridge-harmonyhub
[2017-11-16 08:52:59] Registering platform 'homebridge-harmonyhub.HarmonyHub'
[2017-11-16 08:52:59] ---
[2017-11-16 08:53:00] Loaded plugin: homebridge-homeassistant
[2017-11-16 08:53:00] Registering platform 'homebridge-homeassistant.HomeAssistant'
[2017-11-16 08:53:00] ---
[2017-11-16 08:53:00] There was a problem reading your config.json file.
[2017-11-16 08:53:00] Please try pasting your config.json file here to validate it: http://jsonlint.com
[2017-11-16 08:53:00] 
/usr/lib/node_modules/homebridge/lib/server.js:207
    throw err;
    ^
SyntaxError: Unexpected token { in JSON at position 822
    at JSON.parse (<anonymous>)
    at Server._loadConfig (/usr/lib/node_modules/homebridge/lib/server.js:201:19)
    at new Server (/usr/lib/node_modules/homebridge/lib/server.js:57:38)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:26:16)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:641:30)
    at Object.Module._extensions..js (module.js:652:10)
    at Module.load (module.js:560:32)
    at tryModuleLoad (module.js:503:12)
    at Function.Module._load (module.js:495:3)
    at Function.Module.runMain (module.js:682:10)
    at startup (bootstrap_node.js:191:16)
    at bootstrap_node.js:613:3
/usr/bin/run.sh exited 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
Got SIGHUP, reloading.
No service file found in /etc/avahi/services.
write() failed: Broken pipe
Failed to open /etc/resolv.conf: Broken pipe
Got SIGTERM, quitting.
80

actually I just deleted that plug in to see if it evens works at the beginning fresh and it does not. any help?