Community Hass.io Add-on: Homebridge

Maaniac · October 24, 2017, 8:13pm

Okay makes sense. Is there a reason why the plugin is not picking up the garage door? Garage door is controllable through HA.

frenck · October 24, 2017, 8:17pm

That is an HA/Homebridge specific questions I don’t have an answer to since I do not use any covers type of stuff myself.

apt · October 24, 2017, 9:19pm

thats fine, just as long as I know. Hoping HASSIO gets released as a docker in the near future.

frenck · October 24, 2017, 9:31pm

That is not a bad idea

Laith_Alsunni · October 24, 2017, 10:57pm

Homebridge stopped working

this is the loge I get running log as trace

[cont-init.d] 50-config.sh: executing... 
TRACE: hass.directory_exists: /config/homebridge
TRACE: hass.file_exists: /config/homebridge/config.json
[cont-init.d] 50-config.sh: exited 0.
[cont-init.d] 60-ipv6-hotfix.sh: executing... 
TRACE: hass.config.false: enable_ipv6
TRACE: hass.jq.is_boolean: /data/options.json .enable_ipv6
TRACE: hass.jq.is: /data/options.json .enable_ipv6 boolean
TRACE: hass.jq: /data/options.json .enable_ipv6 | if type=="boolean" then true else false end
TRACE: hass.config.get: enable_ipv6
TRACE: hass.config.exists: enable_ipv6
TRACE: hass.jq.exists: /data/options.json .enable_ipv6
TRACE: hass.jq: /data/options.json .enable_ipv6
TRACE: hass.jq.is_string: /data/options.json .enable_ipv6
TRACE: hass.jq.is: /data/options.json .enable_ipv6 string
TRACE: hass.jq: /data/options.json .enable_ipv6 | if type=="string" then true else false end
TRACE: hass.jq.is_boolean: /data/options.json .enable_ipv6
TRACE: hass.jq.is: /data/options.json .enable_ipv6 boolean
TRACE: hass.jq: /data/options.json .enable_ipv6 | if type=="boolean" then true else false end
TRACE: hass.jq: /data/options.json .enable_ipv6 // false
[cont-init.d] 60-ipv6-hotfix.sh: exited 0.
[cont-init.d] 80-user-packages.sh: executing... 
TRACE: hass.config.has_value: packages
TRACE: hass.jq.has_value: /data/options.json .packages
TRACE: hass.jq: /data/options.json .packages | if (. == {} or . == []) then empty else . end // empty
TRACE: hass.has_value: 
[cont-init.d] 80-user-packages.sh: exited 0.
[cont-init.d] 81-user-scripts.sh: executing... 
TRACE: hass.config.has_value: init_commands
TRACE: hass.jq.has_value: /data/options.json .init_commands
TRACE: hass.jq: /data/options.json .init_commands | if (. == {} or . == []) then empty else . end // empty
TRACE: hass.has_value: 
[cont-init.d] 81-user-scripts.sh: exited 0.
[cont-init.d] 82-user-plugins.sh: executing... 
TRACE: hass.config.has_value: plugins
TRACE: hass.jq.has_value: /data/options.json .plugins
TRACE: hass.jq: /data/options.json .plugins | if (. == {} or . == []) then empty else . end // empty
TRACE: hass.has_value: 
[cont-init.d] 82-user-plugins.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
starting version 3.2.2
[services.d] done.
Found user 'avahi' (UID 86) and group 'avahi' (GID 86).
Successfully dropped root privileges.
avahi-daemon 0.6.32 starting up.
chroot.c: chroot() helper started
WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Successfully called chroot().
Successfully dropped remaining capabilities.
chroot.c: chroot() helper got command 02
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:a1ff:fe96:eb82.
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::1256:ab7:5550:772c.
New relevant interface eth0.IPv6 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.29.203.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::42:a1ff:fe96:eb82 on hassio.*.
Registering new address record for 172.30.32.1 on hassio.*.
Registering new address record for fe80::1256:ab7:5550:772c on eth0.*.
Registering new address record for 192.168.29.203 on eth0.*.
Server startup complete. Host name is hassio.local. Local service cookie is 2858995729.
/usr/lib/node_modules/homebridge/node_modules/decimal.js/decimal.js:3442
     "// number with exponent >= 150000000000p100 (9e15 / 6 = .5e15)( so instead recall this
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Invalid or unexpected token
    at createScript (vm.js:53:10)
    at Object.runInThisContext (vm.js:95:10)
    at Module._compile (module.js:543:28)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Characteristic.js:6:15)
/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.
Leaving mDNS multicast group on interface hassio.IPv6 with address fe80::42:a1ff:fe96:eb82.
dbus[654]: [system] Reloaded configuration
Leaving mDNS multicast group on interface hassio.IPv4 with address 172.30.32.1.
Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::1256:ab7:5550:772c.
Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.29.203.
avahi-daemon 0.6.32 exiting.
[s6-finish] sending all processes the KILL signal and exiting.

my Options

{
  "log_level": "trace",
  "avahi_interfaces": "",
  "avahi_hostname": "hassio",
  "avahi_domainname": "local",
  "enable_ipv6": true,
  "packages": [],
  "init_commands": [],
  "plugins": []
}

My config.json

{
  "bridge": {
    "name": "Home Assistant",
    "username": "B8:27:EB:9B:CC:58",
    "port": 51826,
    "pin": "717-89-596"
  },
  "description": "Homebridge for Home Assistant",
  "accessories": [],
  "platforms": [
    {
      "platform": "HomeAssistant",
      "name": "HomeAssistant",
      "host": "http://homeassistant:8123",
      "password": "XXXXXXXX",
      "default_visibility": "visible",
      "supported_types": [
        "automation",
        "binary_sensor",
        "climate",
        "cover",
        "device_tracker",
        "fan",
        "group",
        "input_boolean",
        "light",
        "lock",
        "media_player",
        "remote",
        "scene",
        "sensor",
        "switch"
      ],
      "logging": true,
      "verify_ssl": true
    }
  ]
}

scheeko · October 24, 2017, 11:41pm

@frenck Thanks for the updates!

But now homebridge-zp requires Homebridge 0.4.29. So, my question is: can one prevent the add-on from looking for the latest plugin version? Is it possible to point to/install locally an older version?

Maaniac · October 25, 2017, 2:03am

i tried adding both Chamberlain and lift master but am getting the below error. I’m not 100% sure where i should be putting the plugin in he config?

/usr/lib/node_modules/homebridge/lib/api.js:122
      throw new Error("The requested platform '" + name + "' was not registered by any plugin.");
      ^
Error: The requested platform 'LiftMaster2' was not registered by any plugin.
    at API.platform (/usr/lib/node_modules/homebridge/lib/api.js:122:13)
    at Server._loadPlatforms (/usr/lib/node_modules/homebridge/lib/server.js:284:45)
    at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:80:36)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:40:10)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439: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.
dbus[661]: [system] Reloaded configuration
Leaving mDNS multicast group on interface hassio.IPv6 with address fe80::42:6eff:fe13:3b60.
Leaving mDNS multicast group on interface hassio.IPv4 with address 172.30.32.1.
Leaving mDNS multicast group on interface eth0.IPv6 with address 2607:fea8:919f:f40a:c7:2d81:2cb8:cd2b.
Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.27.
avahi-daemon 0.6.32 exiting.

frenck · October 25, 2017, 7:13am

@scheeko You cloud try adding [email protected] to the plugins list.

frenck · October 25, 2017, 7:14am

Please be sure to install the plugin as well. See the documentation for more information: https://github.com/hassio-addons/addon-homebridge#option-plugins

Maaniac · October 25, 2017, 12:10pm

Ya i read the documentation but when I try to add the plugin in the config I get json erros. Maybe an example will help me understand.

frenck · October 25, 2017, 12:41pm

@Maaniac I absolutely want to help, but your question does not make sense to me. If you need help with how JSON must be formatted and/or works, I suggest you’d use the power of the Google force. An example of how to install plugins is listed in the documentation as well.

Maaniac · October 25, 2017, 1:03pm

Frenck,

Okay I think I finally figured it out. I was trying to add the plugin information for the chamberlain package within the config.json and that is why I was getting errors. After reading the main documentation for homebridge-homeassistant and checking your hass.io package again I realized that I should have been adding the additional packages in the options panel within your plugin and not in the json file. Not sure how I missed that

Anyway I was able to add the garage door by changing the customize.yaml to include “homebridge_cover_type: garage_door”.

Thanks again for trying to help and for the great plugin.

frenck · October 25, 2017, 9:43pm

Add-on: Homebridge v2.0.1

This release fixes some minor issues reported by you guys!
Thank you all for the feedback!

Full Changelog

Added

Made git available by default #44

Fixed

Won’t start; sed: unmatched ‘/’ #45

Changed

Use the Hass.io to Home Assistant proxy by default
Upgraded addon-base image to v1.0.1

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

Note: Please be sure you are running the latest Supervisor (0.73 or higher).

scheeko · October 26, 2017, 4:18pm

Thanks @frenck. I’m not entirely sure if I’m understanding your suggestion, as the homebridge-homeassistant is not homebridge itself. Or does your add-on pull the version from there?

In any case, I did try what you suggested, but when restarting homebridge at hassio, the log files says:

npm ERR! code ETARGET
npm ERR! notarget No matching version found for [email protected]
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2017-10-26T16_12_06_660Z-debug.log
FATAL: Failed installing plugin [email protected]

Thanks for any clarifications!

frenck · October 26, 2017, 6:36pm

Sorry, my bad @scheeko, the example I gave was the Home Assistant plugin.

I meant try adding [email protected] to the plugins list of the add-on configuration.
Nevertheless, you where stating 0.4.29, but it does not exist, so… dunno, your info was impossible, to begin with.

See the list of available Homebridge releases on their GitHub page: https://github.com/nfarina/homebridge/releases

frenck · October 26, 2017, 7:37pm

Add-on: Homebridge v2.1.0

Full Changelog

Changed

Upgraded NodeJS to 8.x #47
Upgraded homebridge-homeassistant to v3.0.1

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

Note: Please be sure you are running the latest Supervisor (0.73 or higher).

shred · October 27, 2017, 12:29am

I’m not seeing the last two updates to Homebridge on Hass.io. I’m currently on version 2.0.0 and there’s no option to update it. I have updated Homebridge in the past but just these two latest releases I haven’t seen. I’m running the latest version of Home Assistant (0.56.2), Supervisor (0.73) and Host OS (1.1).

VdkaShaker · October 27, 2017, 12:46am

I didn’t see it either, but found out I needed to go to the Hass.io panel, click the add-ons shopping bag (or whatever that icon is), then click the update curl in the top right corner. Then it showed up as an update on the Homebridge line.

Hope that helps.

shred · October 27, 2017, 12:51am

Thanks, that worked.

VdkaShaker · October 27, 2017, 12:56am

There’s an “Auto Update” toggle near the top of all these add-ons. What is that supposed to do?