hassio-addons / addon-homebridge Goto Github PK

View Code? Open in Web Editor NEW

96.0 96.0 93.0 199 KB

 Homebridge - Community Hass.io Add-on for Home Assistant

Home Page: https://addons.community

License: MIT License

Shell 83.27% Dockerfile 16.73%

hass hassio hassio-addons home-assistant homeassistant homebridge homekit siri

addon-homebridge's People

Contributors

Stargazers

Watchers

Forkers

nokia197s 0xjohnx leeacc hequan997 alex950418 myenong steeve mxykyou radinsky edwinldy roy63258015 zelo007 czdeee thomastian googolmo mnoorenberghe ifallah sbyinin dragouf 2060yxz lcshine luodaojun 170348526 sllguy gercok iss 5929196 gzroc jianzichen thecellmc rtenklooster paochu2007 funnybutrandom gotodragon zhenxiwen mbmccormick lawesly stuartgiant cmaxim77 djmakoto jmartinezcdo joka90 svrcore recluse kevinsegal hoppingmonk qiusj cpayne14 scaramella drjeff softskillsunion mudaiheem techxbusiness indigos33k3r niklaswa frenck beosro desiredbean jonathanweinberg abuaijutie timpihl robertd502 itukin jeroenterheerdt wtfrules pacorain earnrising ghostbishop herbsens rayannouibet ajones1979 jasondreher pmiguelcruz andrewfblack lordfish murkumurdok quark999 ketchoutchou steamboy23 jpk32 msvinth bramdan mcinnes01 brickman7713 kirolous pommoq benepixx weihongloke zuohaot orenasher naphanz

addon-homebridge's Issues

no accessories in home app on ios 11

I am attempting to add my hassio homebridge instance to home kit on IOS 11. I am able to add the homebridge bridge, but none of my sensors show up. The home app tells me that I need to perform additional setup in order to add accessories.
When I try to access the accessories list, it is empty.

I have tried restarting homebridge as well as remove and re-adding homebridge in the home app on IOS. Homebridge is seeing my sensors, so I know it is connecting to homeassistant correctly.

Nest temperature changes not translating correctly between F and C

This might have been fixed upstream in Homebridge already since they're several versions ahead.

Changing Nest temperatures through the Hass.io UI works just fine but when using Homebridge (via Siri) I'm getting a failure. In checking the dev logs I saw the below traceback which would indicate that it's translating between temps and passing to the Nest API incorrectly. From what I can tell-- I asked for 68* F, it converted that to 20* C (so far so good) but then commanded Nest to set to 20* F, which is not a support temperature of course.

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.6/asyncio/tasks.py", line 182, in _step
    result = coro.throw(exc)
  File "/usr/lib/python3.6/site-packages/homeassistant/core.py", line 1031, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/climate/__init__.py", line 340, in async_temperature_set_service
    yield from climate.async_set_temperature(**kwargs)
  File "/usr/lib/python3.6/asyncio/futures.py", line 332, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
    future.result()
  File "/usr/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/lib/python3.6/site-packages/homeassistant/components/climate/nest.py", line 169, in set_temperature
    self.device.target = temp
  File "/usr/lib/python3.6/site-packages/nest/nest.py", line 510, in target
    self._set('devices/thermostats', data)
  File "/usr/lib/python3.6/site-packages/nest/nest.py", line 168, in _set
    response = self._nest_api._put(path=path, data=data)
  File "/usr/lib/python3.6/site-packages/nest/nest.py", line 1590, in _put
    return self._request('PUT', path, data=data)
  File "/usr/lib/python3.6/site-packages/nest/nest.py", line 1582, in _request
    raise APIError(response)
nest.nest.APIError: Temperature F value is too low: 20.0

Rewrite add-on onto the S6 process supervisor

Problem/Motivation

This account currently uses a large run.sh script that bootstraps the whole add-on.
Our new base images actually contain the S6 process supervisor, which allows us the split all kinds of different add-on responsibilities in an amazing way.

Additionally, the new base images are equipped with an extensive Bash function library full of tools towards Home Assistant add-ons on S6. This will greatly reduce the amount of code and improve stability overall.

Add CodeClimate

Problem/Motivation

Add CodeClimate.com to this repository in order to protect the code quality of this add-on.

How to control Nest temperature/away status?

I've added Homebridge to my Hass.io installation and it works fine. I have items default hidden because Hue already is in my HomeKit. But I want to add only Nest.

These are all Nest items:
binary_sensor.living_room_thermostat_fan
binary_sensor.living_room_thermostat_has_leaf
binary_sensor.living_room_thermostat_is_locked
binary_sensor.living_room_thermostat_is_using_emergency_heat
binary_sensor.living_room_thermostat_online
climate.living_room
sensor.living_room_thermostat_humidity
sensor.living_room_thermostat_hvac_state
sensor.living_room_thermostat_operation_mode
sensor.living_room_thermostat_target
sensor.living_room_thermostat_temperature

But which one will show up as a thermostat inside HomeKit? Which one of these do I have to make visible to show up in HomeKit?

Won't start; Something went wrong contacting the API

Fresh install of hassio on raspberry pi 3. Added homebridge add-on and when I start the add-on the log shows:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 10-homebridge: applying...
[fix-attrs.d] 10-homebridge: exited 0.
[fix-attrs.d] 20-dbus: applying...
[fix-attrs.d] 20-dbus: exited 0.
[fix-attrs.d] 30-avahi: applying...
[fix-attrs.d] 30-avahi: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
[03:13:35+0000] ERROR ----> Something went wrong contacting the API
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to DEBUG
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing...
ERROR: Something went wrong contacting the API
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 20-dbus.sh: executing...
[cont-init.d] 20-dbus.sh: exited 0.
[cont-init.d] 30-avahi.sh: executing...
DEBUG: Detected Avahi interfaces: eth0
ERROR: Something went wrong contacting the API
[cont-init.d] 30-avahi.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.
[s6-finish] sending all processes the KILL signal and exiting.

Not sure what do do to fix? Help!

(Why the issue was filed)

Expected the add-on to start.

(What you expected to happen)

Add-on won't start

(What actually happened)

Flashed fresh install to SD card for Raspberry Pi. Installed add-on. Tried to start add-on.

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

HomeAssistant not exposed on port 8123

Problem/Motivation

Homebridge does not work as it expects to connect to port 8123 and thus fails.

Expected behavior

An option to change the HomeAssitant URL would be splendid! A way to introspect the current Hassio URL even splenditer.

Home app can't connect to Home Assistant

Problem/Motivation

I have installed Homebridge 2.2.0 on Home Assistant 0.58.1 and Supervisor 0.75.

I can't connect the Home app to Home Assistant. I am able to enter the PIN but then I get the message that Home Assistant cant be added ("Home Assistant toevoegen mislukt").

I have tried all options in the https://github.com/hassio-addons/addon-homebridge#homebridge-cannot-connect-or-login-to-home-assistant page.

Also changed the host in config.json to http://192.168.1.131:8123 but that also gives the same issue.

Any ideas how to fix this?

These are my settings:

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

config.json

{
  "bridge": {
    "name": "Home Assistant",
    "username": "00:0C:29:69:88:A6",
    "port": 51826,
    "pin": "123-45-678"
  },
  "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",
        "fan",
        "group",
        "input_boolean",
        "light",
        "lock",
        "media_player",
        "remote",
        "scene",
        "script",
        "sensor",
        "switch",
        "vacuum"
      ],
      "logging": true,
      "verify_ssl": false
    }
  ]
}

This is the log (removed some of the devices and the "Received packet from invalid interface" message to shorten the log:

TRACE: hass.api.host.info.hostname
TRACE: hass.api.host.info .hostname
TRACE: hass.api.call GET /host/info false .hostname
DEBUG: Requested API resource: http://hassio/host/info
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {"type": "generic", "version": "0.3", "last_version": "0.3", "features": ["shutdown", "reboot", "update"], "hostname": "ubuntu-hass", "os": "GNU/Linux"}}

TRACE: hass.jq: {"result": "ok", "data": {"type": "generic", "version": "0.3", "last_version": "0.3", "features": ["shutdown", "reboot", "update"], "hostname": "ubuntu-hass", "os": "GNU/Linux"}}
 .result
TRACE: hass.jq: {"result": "ok", "data": {"type": "generic", "version": "0.3", "last_version": "0.3", "features": ["shutdown", "reboot", "update"], "hostname": "ubuntu-hass", "os": "GNU/Linux"}}
 if .data == {} then empty else .data end
TRACE: hass.has_value: .hostname
DEBUG: Filtering response using: .hostname
TRACE: hass.jq: {
  "type": "generic",
  "version": "0.3",
  "last_version": "0.3",
  "features": [
    "shutdown",
    "reboot",
    "update"
  ],
  "hostname": "ubuntu-hass",
  "os": "GNU/Linux"
} .hostname
DEBUG: Detected Avahi hostname: ubuntu-hass
TRACE: hass.config.has_value: avahi_domainname
TRACE: hass.jq.has_value: /data/options.json .avahi_domainname
TRACE: hass.jq: /data/options.json .avahi_domainname | if (. == {} or . == []) then empty else . end // empty
TRACE: hass.has_value: local
TRACE: hass.config.get: avahi_domainname
TRACE: hass.config.exists: avahi_domainname
TRACE: hass.jq.exists: /data/options.json .avahi_domainname
TRACE: hass.jq: /data/options.json .avahi_domainname
TRACE: hass.jq.is_string: /data/options.json .avahi_domainname
TRACE: hass.jq.is: /data/options.json .avahi_domainname string
TRACE: hass.jq: /data/options.json .avahi_domainname | if type=="string" then true else false end
TRACE: hass.jq: /data/options.json .avahi_domainname // empty
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
DEBUG: Disabled IPV6 in the Avahi daemon
[cont-init.d] 30-avahi.sh: exited 0.
[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
patching file /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js
[cont-init.d] 60-ipv6-hotfix.sh: exited 0.
[cont-init.d] 80-user-packages.sh: executing... 
DEBUG: Applied HAP NodeJS IPv6 disable hotfix
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
[services.d] done.
starting version 3.2.4
[2017-12-5 23:25:58] [HomeAssistant] Initializing platform accessory 'SHIELD'...
[2017-12-5 23:25:58] [HomeAssistant] Initializing platform accessory 'yeelight_rgb_34ce008040c6'...
[2017-12-5 23:25:58] [HomeAssistant] Initializing platform accessory 'all lights'...
Setup Payload:
X-HM://0023OA63220CD
Scan this code with your HomeKit app on your iOS device to pair with Homebridge:

Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
                       
    ┌────────────┐     
    │ 123-45-678 │     
    └────────────┘     
                       
dbus-protocol.c: interface=org.freedesktop.Avahi.Server, path=/, member=GetAPIVersion
dbus-protocol.c: interface=org.freedesktop.Avahi.Server, path=/, member=GetState
dbus-protocol.c: interface=org.freedesktop.Avahi.Server, path=/, member=GetDomainName
dbus-protocol.c: interface=org.freedesktop.Avahi.Server, path=/, member=EntryGroupNew
dbus-entry-group.c: interface=org.freedesktop.Avahi.EntryGroup, path=/Client0/EntryGroup1, member=GetState
dbus-entry-group.c: interface=org.freedesktop.Avahi.EntryGroup, path=/Client0/EntryGroup1, member=AddService
dbus-entry-group.c: interface=org.freedesktop.Avahi.EntryGroup, path=/Client0/EntryGroup1, member=Commit
[2017-12-5 23:25:58] Homebridge is running on port 51826.
dbus-entry-group.c: interface=org.freedesktop.Avahi.EntryGroup, path=/Client0/EntryGroup1, member=UpdateServiceTxt
dbus-entry-group.c: interface=org.freedesktop.Avahi.EntryGroup, path=/Client0/EntryGroup1, member=UpdateServiceTxt
Received packet from invalid interface.
Received packet from invalid interface.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Host name conflict, retrying with hassio-xx

Problem/Motivation
Homebridge won't start up and get stuck in a loop with a Host name conflict.

Expected behavior
Expect homebridge to start and to produce a 'Key' for the Home.app

Actual behavior
Keeps trying to start service then fails and tries again with a new host name.

Steps to reproduce
Standard steps to add add-on

Proposed changes
No sure.

Example of log:
Host name conflict, retrying with hassio-19
Registering new address record for fe80::473e:1cc1:fccc:1af7 on vetha58f892..
Registering new address record for 169.254.70.152 on vetha58f892.IPv4.
Registering new address record for fe80::786e:31ff:fec6:1b78 on veth175236b..
Registering new address record for 169.254.104.131 on veth175236b.IPv4.
Registering new address record for fe80::a1db:7d77:9e6f:9e14 on docker0..
Registering new address record for 169.254.1.224 on docker0.IPv4.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::3802:117a:5c87:c173 on hassio..
Registering new address record for 169.254.52.243 on hassio.IPv4.
Registering new address record for 172.30.32.1 on hassio.IPv4.
Registering new address record for fe80::d435:ef2d:f54a:aaa2 on wlan0..
Registering new address record for 192.168.1.102 on wlan0.IPv4.
Registering new address record for fe80::a5e3:9aca:38b3:2173 on eth0..
Withdrawing address record for fe80::473e:1cc1:fccc:1af7 on vetha58f892.
Withdrawing address record for fe80::786e:31ff:fec6:1b78 on veth175236b.
Withdrawing address record for 169.254.104.131 on veth175236b.
Withdrawing address record for fe80::a1db:7d77:9e6f:9e14 on docker0.
Withdrawing address record for 169.254.1.224 on docker0.
Withdrawing address record for 172.17.0.1 on docker0.
Withdrawing address record for fe80::3802:117a:5c87:c173 on hassio.
Withdrawing address record for 169.254.52.243 on hassio.
Withdrawing address record for 172.30.32.1 on hassio.
Withdrawing address record for fe80::d435:ef2d:f54a:aaa2 on wlan0.
Withdrawing address record for 192.168.1.102 on wlan0.
Withdrawing address record for fe80::a5e3:9aca:38b3:2173 on eth0.
Host name conflict, retrying with hassio-20

This just keeps repeating, hassio-21, 22 etc and never starts.
I'm trying to run this on a raspberrry pi 2, raspbian.

Any ideas?

Thanks

Won't start; sed: unmatched '/'

Hi frenck, I have the following error while starting up homebridge 2.0. Could you help me with the issue please?

Raspberry pi 3
hostOS 1.1
Supervisor 0.72
HA 0.56.0

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 10-homebridge: applying... 
[fix-attrs.d] 10-homebridge: exited 0.
[fix-attrs.d] 20-dbus: applying... 
[fix-attrs.d] 20-dbus: exited 0.
[fix-attrs.d] 30-avahi: applying... 
[fix-attrs.d] 30-avahi: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Homebridge v2.0.0
 HomeKit support for your Home Assistant instance using Homebridge
 From: Community Hass.io Add-ons
 By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to DEBUG
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
DEBUG: Requested API resource: http://hassio/supervisor/ping
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {}}
DEBUG: Requested API resource: http://hassio/addons/a0d7b954_homebridge/info
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {"name": "Homebridge", "description": "HomeKit support for your Home Assistant instance using Homebridge", "version": "2.0.0", "auto_update": false, "repository": "a0d7b954", "last_version": "2.0.0", "state": "started", "boot": "auto", "options": {"log_level": "debug", "avahi_interfaces": "", "avahi_hostname": "", "avahi_domainname": "local", "enable_ipv6": true, "packages": [], "init_commands": [], "plugins": []}, "url": "https://github.com/hassio-addons/addon-homebridge", "detached": false, "build": false, "network": null, "host_network": true, "privileged": [], "devices": null, "logo": false, "webui": null, "stdin": false, "hassio_api": true, "homeassistant_api": true, "gpio": false, "audio": false, "audio_input": null, "audio_output": null}}
DEBUG: Filtering response using: .version
DEBUG: Requested API resource: http://hassio/addons/a0d7b954_homebridge/info
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {"result": "ok", "data": {"name": "Homebridge", "description": "HomeKit support for your Home Assistant instance using Homebridge", "version": "2.0.0", "auto_update": false, "repository": "a0d7b954", "last_version": "2.0.0", "state": "started", "boot": "auto", "options": {"log_level": "debug", "avahi_interfaces": "", "avahi_hostname": "", "avahi_domainname": "local", "enable_ipv6": true, "packages": [], "init_commands": [], "plugins": []}, "url": "https://github.com/hassio-addons/addon-homebridge", "detached": false, "build": false, "network": null, "host_network": true, "privileged": [], "devices": null, "logo": false, "webui": null, "stdin": false, "hassio_api": true, "homeassistant_api": true, "gpio": false, "audio": false, "audio_input": null, "audio_output": null}}
DEBUG: Filtering response using: .last_version
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 20-dbus.sh: executing... 
[cont-init.d] 20-dbus.sh: exited 0.
[cont-init.d] 30-avahi.sh: executing... 
DEBUG: Detected Avahi interfaces: eth0
wlan0
sed: unmatched '/'
[cont-init.d] 30-avahi.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.
[s6-finish] sending all processes the KILL signal and exiting.

Template cover commands

Problem/Motivation

Cover commands issue by the Home App does not work with template covers without current position sensor on HA. Also, optimistic mode is on. Example: "dumb" tubular motors controlled by RF 433 radio.

Expected behavior

When cover is set to open on Home App, the command set on configuration.yaml open_cover is fired. This applies to close as well.

Actual behavior

Nothing happens, the cover does not respond. I found workaround that is to set this config:

cover:
  - platform: template
    covers:
      persiana_suite:
        optimistic: true
        friendly_name: "Persiana da suíte"
        set_cover_position:
          service_template: >
            {% if is_state('cover.persiana_suite', 'open') %}
              script.persiana_suite_fechar
            {% elif is_state('cover.persiana_suite', 'closed') %}
              script.persiana_suite_abrir
            {% endif %}
        stop_cover:
          service: script.persiana_suite_parar
        open_cover:
          service: script.persiana_suite_abrir
        close_cover:
          service: sscript.persiana_suite_fechar

This works but scenes on Home App does not. Example: if I create a scene and set a cover to be closed and test it, if the cover is already closed the cover opens. It should send the close command, not the open command. I don't get it.

Steps to reproduce

Have a template cover set as the example config above and Homebridge installed. Pair with Home app and try to control it using the Home App.

Proposed changes

Not sure if this is problem on this addon or homebridge core. Not sure what to do, sorry. Optimistic mode has something to do with, since I don't have a sensor to get the cover position.

Thank you very much @frenck! Sorry to bother you.

Not auto restarting on HASSIO reboot

Problem/Motivation

Homebridge isn’t auto restarting if host is rebooted

Expected behavior

Homebridge should restart if Auto is selected.

Actual behavior

homebridge doesn’t start, have to manually start addon.

Steps to reproduce

Make sure homebridge is installed and started, reboot host (HASSIO) check homebridge add on once started up. Should show the start button.

Proposed changes

fix so auto restarts after host reboot.

Cannot pull home bridge add-on - 404 error

Problem/Motivation

I cannot pull the home bridge add-on via hass.io. Only the homebridge add-on is affected, the terminal and SSH addons work just fine.
The error is:

17-09-27 19:05:49 INFO (SyncWorker_7) [hassio.dock.interface] Pull image hassioaddons/homebridge-armhf tag 1.0.3.
17-09-27 19:05:52 ERROR (SyncWorker_7) [hassio.dock.interface] Can't install hassioaddons/homebridge-armhf:1.0.3 -> 404 Client Error: Not Found ("no such image: hassioaddons/homebridge-armhf:1.0.3: No such image: hassioaddons/homebridge-armhf:1.0.3").

I'm unable to determine exactly why it's happening - but I suspect it's due to:
https://github.com/hassio-addons/repository/blob/master/homebridge/config.json

Line 22 references "hassioaddons/homebridge-{arch}" and not what I suspect should be "hassio**-**addons/homebridge-{arch}" as referenced elsewhere.

(but that's just a best guess)

States not updating in Homekit if changed in HA

Problem/Motivation

If I turn on a switch (or similar) in the HA UI, the status did not change in home.app on my iOS device.
If I restart homebridge I get ONE single update to all stats
Nothing in the logs.

Expected behavior

Always update the status in homekit if changed in UI.

Actual behavior

Status did not change.

Steps to reproduce

(How can someone else make/see it happen)

Updated to 1.0.2, Accessories disappeared

Problem/Motivation

HomeBridge still in iOS but no accessories. Restart of HomeBridge gives "Please set default_visibility in config.json to "hidden" or "visible"."

Proposed changes

In a default cong.json, add where this default_visibility should be.

Failure on startup

Just tried to install and run the addon-homebridge (version 1.0.3) on hassio. Seem to be getting a 403 on an HTTP call. Running latest hassio v0.51.2.

I have added home assistant password to the /homebridge/config.json.

Any pointers?

Per

starting version 3.2.2
[ADD-ON] Ensuring old PID files are absent
[ADD-ON] Ensuring D-Bus unique ID exists
[ADD-ON] Starting D-Bus daemon
[ADD-ON] [DEBUG] Waiting until system bus socket is ready
[ADD-ON] Starting Avahi daemon
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
Loading service file /services/sftp-ssh.service.
Loading service file /services/ssh.service.
*** 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 docker0.IPv4 with address 172.17.0.1.
New relevant interface docker0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::a020:aaff:feb4:cc78 on veth3fa7af9.*.
Registering new address record for fe80::42:3cff:fefe:cf1c on hassio.*.
Registering new address record for 172.30.32.1 on hassio.IPv4.
Registering new address record for fe80::82f:b9ff:fe49:3a93 on veth924b4de.*.
Registering new address record for fe80::5069:2fff:fed2:c92d on vethfe884a7.*.
Registering new address record for fe80::709e:d8ff:fe08:3dd7 on vetha92f327.*.
Registering new address record for fe80::140a:33ff:fef7:74f7 on veth89604ce.*.
Registering new address record for fe80::42:7ff:fe77:16ff on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::d4bf:8b1e:714a:b7b2 on eth0.*.
Registering new address record for 192.168.1.2 on eth0.IPv4.
Server startup complete. Host name is hassio.local. Local service cookie is 1064142052.
[ADD-ON] Applying HAP NodeJS IPV6 HOTFIX
patching file /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js
[ADD-ON] Starting Homebridge
*** 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>
[8/25/2017, 1:00:16 PM] Loaded plugin: homebridge-homeassistant
[8/25/2017, 1:00:17 PM] Registering platform 'homebridge-homeassistant.HomeAssistant'
[8/25/2017, 1:00:17 PM] ---
[8/25/2017, 1:00:17 PM] Loaded config.json with 0 accessories and 1 platforms.
[8/25/2017, 1:00:17 PM] ---
[8/25/2017, 1:00:17 PM] Loading 1 platforms...
[8/25/2017, 1:00:17 PM] [HomeAssistant] Initializing HomeAssistant platform...
[8/25/2017, 1:00:17 PM] [HomeAssistant] Fetching HomeAssistant devices.
[8/25/2017, 1:00:17 PM] Loading 0 accessories...
undefined:1
403: Forbidden
   ^
SyntaxError: Unexpected token : in JSON at position 3
    at JSON.parse (<anonymous>)
    at Request.request [as _callback] (/usr/lib/node_modules/homebridge-homeassistant/index.js:100:38)
    at Request.self.callback (/usr/lib/node_modules/homebridge-homeassistant/node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:194:7)
    at Request.<anonymous> (/usr/lib/node_modules/homebridge-homeassistant/node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:191:7)
    at IncomingMessage.<anonymous> (/usr/lib/node_modules/homebridge-homeassistant/node_modules/request/request.js:1091:12)
    at Object.onceWrapper (events.js:293:19)

Homebridge DNS service error (log)

Problem/Motivation

Homebridge not starting

Expected behavior

Running homebridge addon

Actual behavior

Homebridge is completely loading , but at the End is an DNS error and Homebridge is stops running.

Steps to reproduce

I only restarted the addon

Proposed changes

A possible fix/workaround is the reinstall avahi daemon sudo apt-get install avahi-daemon avahi-discover libnss-mdns libavahi-compat-libdnssd-dev
But how is this possible on Hass.io?

LOG:

starting version 3.2.2
[ADD-ON] Ensuring old PID files are absent
[ADD-ON] Ensuring D-Bus unique ID exists
[ADD-ON] Starting D-Bus daemon
[ADD-ON] Starting Avahi daemon
Found user 'avahi' (UID 86) and group 'avahi' (GID 86).
Successfully dropped root privileges.
write(): No space left on device
Failed to create PID file: No space left on device
[ADD-ON] Applying HAP NodeJS IPV6 HOTFIX
patching file /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js
[ADD-ON] Starting Homebridge
*** 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>
[10/20/2017, 11:03:39 AM] Loaded plugin: homebridge-homeassistant
[10/20/2017, 11:03:39 AM] Registering platform 'homebridge-homeassistant.HomeAssistant'
[10/20/2017, 11:03:39 AM] ---
[10/20/2017, 11:03:39 AM] Loaded config.json with 0 accessories and 1 platforms.
[10/20/2017, 11:03:39 AM] ---
[10/20/2017, 11:03:39 AM] Loading 1 platforms...
[10/20/2017, 11:03:39 AM] [HomeAssistant] Initializing HomeAssistant platform...
[10/20/2017, 11:03:39 AM] [HomeAssistant] Fetching HomeAssistant devices.
[10/20/2017, 11:03:39 AM] Loading 0 accessories...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'deaktiviere Alarmanlage'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'aktiviere Alarmanlage'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Ad Blocker'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Jalousie_Wohnzimmer'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Weihnachtsstern'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Alarm ausgeloest'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Drucker'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Ambilight'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Jalousie_Esszimmer'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Lichterkette_draussen'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Lichterkette'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Venta'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Jalousie_Kueche'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Luftbefeuchter Schlafzimmer'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Luftbefeuchter Kira'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Mobil Sonos'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Wohnzimmer Sonos'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Stehlampe'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Flurlampe'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Jalousie HWR'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Küchen Lampe'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Temperatursensor_Kueche'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Helligskeitssensor_Kueche'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Wohnzimmerlampe'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Jalousie Schiebetür'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Brunnenpumpe'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Ladestation'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Kompressor'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Carport Steckdose'...
[10/20/2017, 11:03:41 AM] [HomeAssistant] Initializing platform accessory 'Temperatur Wohnzimmer'...
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
                       
    ┌────────────┐     
    │ 853-81-325 │     
    └────────────┘     
                       
/usr/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:56
  dns_sd.DNSServiceRegister(self.serviceRef, flags, ifaceIdx, name,
         ^
Error: dns service error: unknown
    at new Advertisement (/usr/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:56:10)
    at Object.create [as createAdvertisement] (/usr/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:64:10)
    at Advertiser.startAdvertising (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Advertiser.js:43:30)
    at Bridge.Accessory._onListening (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:575:20)
    at emitOne (events.js:96:13)
    at HAPServer.emit (events.js:191:7)
    at HAPServer._onListening (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:190:8)
    at emitOne (events.js:96:13)
    at EventedHTTPServer.emit (events.js:191:7)
    at EventedHTTPServer.<anonymous> (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js:65:10)

Error when installing homebridge-plugin

I'm running the latest hass.io release, and my config looks like this:

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

During startup, (in stage 82) the addon tries to install the homebridge-plugin "homebridge-harmonyhub", but that fails for some reason:

[cont-init.d] 82-user-plugins.sh: executing... 
npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EAI_AGAIN: request to https://registry.npmjs.org/debug failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org:443
npm WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
npm WARN deprecated [email protected]: use @xmpp/xml package <https://www.npmjs.com/package/@xmpp/xml>
npm WARN deprecated [email protected]: use @xmpp/jid package <https://www.npmjs.com/package/@xmpp/jid>
npm WARN tar ENOENT: no such file or directory, open '/usr/lib/node_modules/.staging/async-b84761f6/LICENSE'
npm WARN tar ENOENT: no such file or directory, open '/usr/lib/node_modules/.staging/jsbn-7cdb5a80/example.html'
npm WARN tar ENOENT: no such file or directory, open '/usr/lib/node_modules/.staging/async-b84761f6/CHANGELOG.md'
npm WARN tar ENOENT: no such file or directory, open '/usr/lib/node_modules/.staging/esprima-7c54439d/ChangeLog'
npm WARN tar ENOENT: no such file or directory, open '/usr/lib/node_modules/.staging/esprima-7c54439d/LICENSE.BSD'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/homebridge-harmonyhub/node_modules/handlebars/node_modules/source-map):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: request to https://registry.npmjs.org/source-map/-/source-map-0.4.4.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org:443
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/homebridge-harmonyhub/node_modules/has-flag):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: request to https://registry.npmjs.org/has-flag/-/has-flag-1.0.0.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org:443
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/homebridge-harmonyhub/node_modules/is-buffer):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: Cannot cd into '/usr/lib/node_modules/.staging/is-buffer-e71acd2c'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/homebridge-harmonyhub/node_modules/async):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: Cannot cd into '/usr/lib/node_modules/.staging/async-b84761f6'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/homebridge-harmonyhub/node_modules/esprima):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: Cannot cd into '/usr/lib/node_modules/.staging/esprima-7c54439d'
npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org:443
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2017-10-26T07_01_51_385Z-debug.log
FATAL: Failed installing plugin homebridge-harmonyhub
[cont-init.d] 82-user-plugins.sh: exited 1.

Problems with Panasonic Viera with Hass.io/Homebridge combination

I have problems with the Panasonic Viera component. I have it also in Home Assistant. So I know it isn't HomeBridge, I think, but... When I was running NodeJS/HomeBridge on my Pi I used this plugin (https://www.npmjs.com/package/homebridge-panasonictv). I was wondering, is there a way to get this inside HomeBridge?! So I don't have to use the Hass.io component Viera?

Can't install add-on

Problem/Motivation

Can't install the add-on.

Expected behavior

When I click 'INSTALL' I expect the add-on to be installed.

Actual behavior

After a while the connection to the inferface is lost and Home Assistant restarts.

Steps to reproduce

Click 'INSTALL', wait for about 30 seconds, then the connection is lost, Home Assistant restarts and the add-on is not installed. I can click INSTALL again, then the same thing happens.

Home Assistant 0.52.1

Osram Lightify Tunable Bulbs : Temperature cannot be controlled via Home app

Osram lightify bulbs ( tunable bulbs) do not respond to changes in color temperature settings made through the Home app (iOS) but do so through the Hassio frontend.

The bulbs support several colors throughout the white spectrum (color temperature) but default to white when controlled through homebridge.

I have used this setup directly through Homebridge (run directly on Rasbian) with the Osram-lightify platform and this feature worked as expected before. This does not work when using the homebridge addon (2.0.0) on the Hassio build (0.56.1). Unfortunately, I didnt test this with earlier versions, so I dont know if the new upgrades broke some support or if this issue was preexisting

Can't use curl with this addon

I'm trying to use the homebridge-cmdswitch2 plugin as suggested in https://community.home-assistant.io/t/homekit-location-to-trigger-automations-in-home-assistant-using-a-software-switch-requires-no-homekit-hardware/17235/8

Unfortunately the scripts don't work because curl can't be found:

[8/26/2017, 9:29:39 AM] [CMD switch] Initializing cmdSwitch2 platform...
[8/26/2017, 9:29:39 AM] Loading 0 accessories...
[8/26/2017, 9:29:39 AM] [CMD switch] Initializing platform accessory 'Mauricio is Home'...
[8/26/2017, 9:29:39 AM] [CMD switch] Failed to determine Mauricio is Home state.
[8/26/2017, 9:29:39 AM] [CMD switch] /config/homebridge/mbonani_status.sh: line 1: /usr/bin/curl: not found

But curl is there in the host:

root@hassio:~# which curl
/usr/bin/curl

And the script run normally in the shell:

core-ssh:/config/homebridge# ./mbonani_status.sh 
{"attributes": {"friendly_name": "Mauricio at home"}, "entity_id": "input_boolean.mbonani_home", "last_changed": "2017-08-26T11:57:19.829657+00:00", "last_updated": "2017-08-26T11:57:19.829657+00:00", "state": "on"}

Can you help me on that?

cachedAccessories causing duplicate UUID with homebridge-cmdswitch2

I'm not sure if this is a cmdswitch2 or homebridge issue, so I've posted the problem on both projects, with the other one being here: luisiam/homebridge-cmdswitch2#8 (comment)

Using the cmdswitch2 plugin, if I restart the homebridge service the duplicate UUID error occurs. If I delete the /config/homebridge/accessories/cachedAccessories file and restart, it works ok. Restart the service again and it fails.

Multiple people on this thread have experienced the same problem: https://community.home-assistant.io/t/homekit-location-to-trigger-automations-in-home-assistant-using-a-software-switch-requires-no-homekit-hardware/17235

The latest version of hassio (using ResinOS image) with the homebridge add-on is being used.

Within Options I have the following:

 {
  "debug": false,
  "plugins": [
    "homebridge-cmdswitch2"
  ]
}

After accessing hassio via SSH, /config/homebridge/config.json is modified with the following:

{
  "bridge": {
    "name": "Home Assistant",
    "username": "00:00:00:00:00:00",  #removed values
    "port": 51826,
    "pin": "000-00-000"  #removed values
  },
  "description": "Homebridge for Home Assistant",
  "accessories": [],
  "platforms": [
    {
      "platform": "HomeAssistant",
       
       .... Shortened for this comment
       
        "sensor",
        "switch"
      ],
      "logging": true
    }, {
      "platform": "cmdSwitch2",
      "name": "CMD switch",
      "switches": [{
        "name": "User isHome",
        "on_cmd": "/config/homebridge/userhome.sh",
        "off_cmd": "/config/homebridge/useraway.sh",
        "state_cmd": "/config/homebridge/userstatus.sh",
        "polling": "true"
      }]
    }]
}

The logs show the following error:

[9/4/2017, 5:42:17 PM] Loaded plugin: homebridge-cmdswitch2
[9/4/2017, 5:42:17 PM] Registering platform 'homebridge-cmdswitch2.cmdSwitch2'
[9/4/2017, 5:42:17 PM] ---
[9/4/2017, 5:42:18 PM] Loaded plugin: homebridge-homeassistant
[9/4/2017, 5:42:18 PM] Registering platform 'homebridge-homeassistant.HomeAssistant'
[9/4/2017, 5:42:18 PM] ---
[9/4/2017, 5:42:18 PM] Loaded config.json with 0 accessories and 2 platforms.
[9/4/2017, 5:42:18 PM] ---
[9/4/2017, 5:42:18 PM] Loading 2 platforms...
[9/4/2017, 5:42:18 PM] [HomeAssistant] Initializing HomeAssistant platform...
[9/4/2017, 5:42:18 PM] [HomeAssistant] Fetching HomeAssistant devices.
[9/4/2017, 5:42:18 PM] [CMD switch] Initializing cmdSwitch2 platform...
[9/4/2017, 5:42:18 PM] Loading 0 accessories...
[9/4/2017, 5:42:18 PM] [CMD switch] Initializing platform accessory 'User isHome'...
/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:256
      throw new Error("Cannot add a bridged Accessory with the same UUID as another bridged Accessory: " + existing.UUID);
      ^
Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: 3dd34efe-097b-4b8b-a688-352f08cd38d6
    at Bridge.Accessory.addBridgedAccessory (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:256:13)
    at Bridge.Accessory.addBridgedAccessories (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:282:10)
    at Server._handleRegisterPlatformAccessories (/usr/lib/node_modules/homebridge/lib/server.js:437:16)
    at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:36:10)

Homebridge don't see Wireless Switch

Problem/Motivation

Wireless switch from Xiaomi Aqara is avaliable on HA, but not visible in iOS home app. It works fine when using Homebridge without hassio, but not avaliable with that plugin. Any suggestions how to fix it? Thanks!

Nest temperature incorrect on homekit

The Nest temperature from Nest that is in F is being threaded as C and then being converted to F.

For example Nest is set to 76 F while on the homekit app it shows as 169. Could this be an issue with Homebridge or Hassio?

Is there a fix already for this?

i am using Hass.io 0.55.2 and Homebridge 1.0.3

Envisalink/Security System Not Updating Status Until Opened

Problem/Motivation

I use Home Assistant in partnership with an Envisalink and homebridge plugin to carry out security functions. Right now, the status of the alarm doesn't update unless the Home app is opened on my iPhone. (This is a problem, as it is supposed to send a notification when the alarm is armed or disarmed.)

Expected behavior

Whenever there is a state change, Home Assistant and Homebridge should pass the data to HomeKit to send an alert that there has been a change in the arm/disarm status.

Actual behavior

The system only updates whenever the Home App is opened.

Steps to reproduce

Set alarm manually or via the home assistant, or through automation, and then you are not alerted. You must then open the Home app to let it connect to Home Assistant/Homebridge to update. Then an alert comes up that says what happened.

Proposed changes

I am unsure of how to fix this. I know that in the past there was a similar issue with homebridge itself before I started using Home Assistant, however, I do not know how this was fixed.

Migrate to the new Hass.io build system

Problem/Motivation

Recently the Hass.io build system was introduced.
This requires modifications to the add-on in order to be compatible.

More information on the change:
https://home-assistant.io/blog/2017/09/26/new-hassio-build-system/

Migrate add-on onto the new base images

Problem/Motivation

We’ve build new base images for our add-ons.
In order to support future development, this add-on needs to be moved onto these new base images.

Base images:https://github.com/hassio-addons/addon-base

Home app says can't connect to Home Assistant

Problem/Motivation

When I try to connect Home Assistant to Home App at first start it says error username. I set a random username in config.json file (A-f 0-9), no more errors appear. Here is the log

starting version 3.2.2
[ADD-ON] Ensuring old PID files are absent
[ADD-ON] Ensuring D-Bus unique ID exists
[ADD-ON] Starting D-Bus daemon
[ADD-ON] Starting Avahi daemon
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.
Loading service file /services/sftp-ssh.service.
Loading service file /services/ssh.service.
*** 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 docker0.IPv4 with address 172.17.0.1.
New relevant interface docker0.IPv4 for mDNS.
Joining mDNS multicast group on interface wlan0.IPv4 with address 10.0.0.2.
New relevant interface wlan0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.0.9.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::9c9b:a0ff:fe5c:308f on veth7d5e4a8.*.
Registering new address record for fe80::4494:6cff:fe79:ca94 on vethab56e06.*.
Registering new address record for fe80::42:77ff:fe9e:f570 on hassio.*.
Registering new address record for 172.30.32.1 on hassio.IPv4.
Registering new address record for fe80::42:57ff:fe72:15af on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::c8c7:cfcb:a47:3a3e on wlan0.*.
Registering new address record for 10.0.0.2 on wlan0.IPv4.
Registering new address record for fe80::1c03:af6e:76ec:3d4a on eth0.*.
Registering new address record for 10.0.0.9 on eth0.IPv4.
Server startup complete. Host name is hassio.local. Local service cookie is 1796144574.
[ADD-ON] Applying HAP NodeJS IPV6 HOTFIX
patching file /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js
[ADD-ON] Starting Homebridge
*** 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>
[9/26/2017, 9:25:07 PM] Loaded plugin: homebridge-homeassistant
[9/26/2017, 9:25:07 PM] Registering platform 'homebridge-homeassistant.HomeAssistant'
[9/26/2017, 9:25:07 PM] ---
[9/26/2017, 9:25:07 PM] Loaded config.json with 0 accessories and 1 platforms.
[9/26/2017, 9:25:07 PM] ---
[9/26/2017, 9:25:07 PM] Loading 1 platforms...
[9/26/2017, 9:25:07 PM] [HomeAssistant] Initializing HomeAssistant platform...
[9/26/2017, 9:25:07 PM] [HomeAssistant] Fetching HomeAssistant devices.
[9/26/2017, 9:25:07 PM] Loading 0 accessories...
[9/26/2017, 9:25:07 PM] [HomeAssistant] Received event: ping
[9/26/2017, 9:25:07 PM] [HomeAssistant] Initializing platform accessory 'TRADFRI bulb E27 WS opal 980lm 2'...
[9/26/2017, 9:25:07 PM] [HomeAssistant] Initializing platform accessory 'TRADFRI bulb E27 WS opal 980lm'...
[9/26/2017, 9:25:07 PM] [HomeAssistant] Initializing platform accessory 'camera Filippo'...
[9/26/2017, 9:25:07 PM] [HomeAssistant] Initializing platform accessory 'all lights'...
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
                       
    ┌────────────┐     
    │ 150-52-236 │     
    └────────────┘     
                       
[9/26/2017, 9:25:07 PM] Homebridge is running on port 51826.
[9/26/2017, 9:25:30 PM] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-09-27T04:37:15+00:00", "next_dusk": "2017-09-27T17:32:51+00:00", "next_midnight": "2017-09-26T23:04:54+00:00", "next_noon": "2017-09-27T11:05:03+00:00", "next_rising": "2017-09-27T05:06:57+00:00", "next_setting": "2017-09-27T17:03:09+00:00", "elevation": -24.92, "azimuth": 295.33, "friendly_name": "Sun"}, "last_changed": "2017-09-26T18:46:14.178697+00:00", "last_updated": "2017-09-26T19:24:30.151238+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-09-27T04:37:15+00:00", "next_dusk": "2017-09-27T17:32:51+00:00", "next_midnight": "2017-09-26T23:04:54+00:00", "next_noon": "2017-09-27T11:05:03+00:00", "next_rising": "2017-09-27T05:06:57+00:00", "next_setting": "2017-09-27T17:03:09+00:00", "elevation": -25.08, "azimuth": 295.55, "friendly_name": "Sun"}, "last_changed": "2017-09-26T18:46:14.178697+00:00", "last_updated": "2017-09-26T19:25:30.151399+00:00"}}, "origin": "LOCAL", "time_fired": "2017-09-26T19:25:30.151551+00:00"}
[9/26/2017, 9:26:20 PM] [HomeAssistant] Received event: ping
[9/26/2017, 9:26:30 PM] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-09-27T04:37:15+00:00", "next_dusk": "2017-09-27T17:32:51+00:00", "next_midnight": "2017-09-26T23:04:54+00:00", "next_noon": "2017-09-27T11:05:03+00:00", "next_rising": "2017-09-27T05:06:57+00:00", "next_setting": "2017-09-27T17:03:09+00:00", "elevation": -25.08, "azimuth": 295.55, "friendly_name": "Sun"}, "last_changed": "2017-09-26T18:46:14.178697+00:00", "last_updated": "2017-09-26T19:25:30.151399+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-09-27T04:37:15+00:00", "next_dusk": "2017-09-27T17:32:51+00:00", "next_midnight": "2017-09-26T23:04:54+00:00", "next_noon": "2017-09-27T11:05:03+00:00", "next_rising": "2017-09-27T05:06:57+00:00", "next_setting": "2017-09-27T17:03:09+00:00", "elevation": -25.24, "azimuth": 295.76, "friendly_name": "Sun"}, "last_changed": "2017-09-26T18:46:14.178697+00:00", "last_updated": "2017-09-26T19:26:30.153223+00:00"}}, "origin": "LOCAL", "time_fired": "2017-09-26T19:26:30.153378+00:00"}
[9/26/2017, 9:27:20 PM] [HomeAssistant] Received event: ping
[9/26/2017, 9:27:30 PM] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-09-27T04:37:15+00:00", "next_dusk": "2017-09-27T17:32:51+00:00", "next_midnight": "2017-09-26T23:04:54+00:00", "next_noon": "2017-09-27T11:05:03+00:00", "next_rising": "2017-09-27T05:06:57+00:00", "next_setting": "2017-09-27T17:03:09+00:00", "elevation": -25.24, "azimuth": 295.76, "friendly_name": "Sun"}, "last_changed": "2017-09-26T18:46:14.178697+00:00", "last_updated": "2017-09-26T19:26:30.153223+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-09-27T04:37:15+00:00", "next_dusk": "2017-09-27T17:32:51+00:00", "next_midnight": "2017-09-26T23:04:54+00:00", "next_noon": "2017-09-27T11:05:03+00:00", "next_rising": "2017-09-27T05:06:57+00:00", "next_setting": "2017-09-27T17:03:09+00:00", "elevation": -25.39, "azimuth": 295.98, "friendly_name": "Sun"}, "last_changed": "2017-09-26T18:46:14.178697+00:00", "last_updated": "2017-09-26T19:27:30.151830+00:00"}}, "origin": "LOCAL", "time_fired": "2017-09-26T19:27:30.151984+00:00"}
[9/26/2017, 9:28:20 PM] [HomeAssistant] Received event: ping
[9/26/2017, 9:28:30 PM] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-09-27T04:37:15+00:00", "next_dusk": "2017-09-27T17:32:51+00:00", "next_midnight": "2017-09-26T23:04:54+00:00", "next_noon": "2017-09-27T11:05:03+00:00", "next_rising": "2017-09-27T05:06:57+00:00", "next_setting": "2017-09-27T17:03:09+00:00", "elevation": -25.39, "azimuth": 295.98, "friendly_name": "Sun"}, "last_changed": "2017-09-26T18:46:14.178697+00:00", "last_updated": "2017-09-26T19:27:30.151830+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-09-27T04:37:15+00:00", "next_dusk": "2017-09-27T17:32:51+00:00", "next_midnight": "2017-09-26T23:04:54+00:00", "next_noon": "2017-09-27T11:05:03+00:00", "next_rising": "2017-09-27T05:06:57+00:00", "next_setting": "2017-09-27T17:03:09+00:00", "elevation": -25.55, "azimuth": 296.19, "friendly_name": "Sun"}, "last_changed": "2017-09-26T18:46:14.178697+00:00", "last_updated": "2017-09-26T19:28:30.152432+00:00"}}, "origin": "LOCAL", "time_fired": "2017-09-26T19:28:30.152586+00:00"}
[9/26/2017, 9:29:20 PM] [HomeAssistant] Received event: ping
[9/26/2017, 9:29:30 PM] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-09-27T04:37:15+00:00", "next_dusk": "2017-09-27T17:32:51+00:00", "next_midnight": "2017-09-26T23:04:54+00:00", "next_noon": "2017-09-27T11:05:03+00:00", "next_rising": "2017-09-27T05:06:57+00:00", "next_setting": "2017-09-27T17:03:09+00:00", "elevation": -25.55, "azimuth": 296.19, "friendly_name": "Sun"}, "last_changed": "2017-09-26T18:46:14.178697+00:00", "last_updated": "2017-09-26T19:28:30.152432+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-09-27T04:37:15+00:00", "next_dusk": "2017-09-27T17:32:51+00:00", "next_midnight": "2017-09-26T23:04:54+00:00", "next_noon": "2017-09-27T11:05:03+00:00", "next_rising": "2017-09-27T05:06:57+00:00", "next_setting": "2017-09-27T17:03:09+00:00", "elevation": -25.71, "azimuth": 296.41, "friendly_name": "Sun"}, "last_changed": "2017-09-26T18:46:14.178697+00:00", "last_updated": "2017-09-26T19:29:30.151952+00:00"}}, "origin": "LOCAL", "time_fired": "2017-09-26T19:29:30.152103+00:00"}
[9/26/2017, 9:30:20 PM] [HomeAssistant] Received event: ping
[9/26/2017, 9:30:30 PM] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-09-27T04:37:15+00:00", "next_dusk": "2017-09-27T17:32:51+00:00", "next_midnight": "2017-09-26T23:04:54+00:00", "next_noon": "2017-09-27T11:05:03+00:00", "next_rising": "2017-09-27T05:06:57+00:00", "next_setting": "2017-09-27T17:03:09+00:00", "elevation": -25.71, "azimuth": 296.41, "friendly_name": "Sun"}, "last_changed": "2017-09-26T18:46:14.178697+00:00", "last_updated": "2017-09-26T19:29:30.151952+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-09-27T04:37:15+00:00", "next_dusk": "2017-09-27T17:32:51+00:00", "next_midnight": "2017-09-26T23:04:54+00:00", "next_noon": "2017-09-27T11:05:03+00:00", "next_rising": "2017-09-27T05:06:57+00:00", "next_setting": "2017-09-27T17:03:09+00:00", "elevation": -25.86, "azimuth": 296.63, "friendly_name": "Sun"}, "last_changed": "2017-09-26T18:46:14.178697+00:00", "last_updated": "2017-09-26T19:30:30.153080+00:00"}}, "origin": "LOCAL", "time_fired": "2017-09-26T19:30:30.153225+00:00"}
[9/26/2017, 9:31:21 PM] [HomeAssistant] Received event: ping

Now, when I use the app I see Home Assistant, I insert the password but it can't connect! I don't know why, seems fine to me..
I did insert the pin that appeared.

Expected behavior

I expect a connection with Home iOS App.

Actual behavior

Appears error "Is not possible to add Home Assistant. Home App is not capable of connecting to accessory"

Steps to reproduce

This is the default procedure

EDIT: I create a new Home from settings and it works!!

Colors Not Being Set Correctly in iOS 11

Problem/Motivation

I have a Aeotec z-wave led bulb and in iOS 10, when I would ask Siri to set a particular color, it would be done. After updating to iOS 11, it doesn’t work anymore. Works normally through Home Assistant.

Expected behavior

I try to set the color (let’s say red), the bulb is set to the asked color (Home assistant says “rgb(255,0,0)”)

Actual behavior

I try to set the color (let’s say red), the bulb is set to on but no color (Home assistant says “rgb(0,0,0)”). This happens when asking Siri or attempting to set with HomeKit’s color wheel.

Proposed changes

I’m not sure if this is an issue with Home Bridge (I don’t have other bulbs to test) or an issue with HomeKit in iOS 11 (os is has several bugs as is, but since this is t an officially supported platform, I doubt I’ll get far with Apple)

Upgrade Homebridge to v0.4.29

Problem/Motivation

A new version of Homebridge is released via NPM; v0.4.29

hombridge does not restart after exception

I'm running hass.io on a rpi3 with everything updated to the latest versions. My homebridge-addon configuration looks like this:

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

homebridge has been running happily for a long time, but today homebridge-harmonyhub (a plugin for communicating with the Logitech Harmony Hub remote control) generated an exception which caused homebridge to crash.

I though that with version 2.x, homebridge would automatically restart, but that didn't happen. Here's the last part of the logfile:

events.js:199
      throw err;
      ^
Error [ERR_UNHANDLED_ERROR]: Unhandled error. (XMPP authentication failure)
    at Client.emit (events.js:197:19)
    at Client._handleAuthState (/usr/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-client/lib/Client.js:298:10)
    at Client._handleStanza (/usr/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-client/lib/Client.js:234:12)
    at Client.onStanza (/usr/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-client/lib/Client.js:222:8)
    at emitOne (events.js:125:13)
    at Connection.emit (events.js:221:7)
    at Connection.onStanza (/usr/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/Connection.js:369:10)
    at StreamParser.<anonymous> (/usr/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/Connection.js:226:10)
    at emitOne (events.js:125:13)
    at StreamParser.emit (events.js:221:7)
    at SaxLtx.<anonymous> (/usr/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/StreamParser.js:58:14)
    at emitOne (events.js:125:13)
    at SaxLtx.emit (events.js:221:7)
    at SaxLtx._handleTagOpening (/usr/lib/node_modules/homebridge-harmonyhub/node_modules/ltx/lib/parsers/ltx.js:28:22)
    at SaxLtx.write (/usr/lib/node_modules/homebridge-harmonyhub/node_modules/ltx/lib/parsers/ltx.js:105:26)
    at StreamParser.write (/usr/lib/node_modules/homebridge-harmonyhub/node_modules/node-xmpp-core/lib/StreamParser.js:123:17)
/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.

Unable to access Homebridge devices when not home

Problem/Motivation

When I'm not at home I can no longer get status or control my HomeBridge devices in the Home app on the iPhone. All my non-HomeBridge devices still works just as they should so it's only the devices that I run via HomeBridge that is the problem.

It all worked before but since some time back it stopped working.

My setup is:
Raspberry Pi 3b running Hass.io 0.59.2
Homebridge 2.2.0 (auto update enabled)
Apple TV with latest OS
iPhones and iPad with latest OS

Homebridge and Apple TV is connected to the same Switch

Fibaro, Elgato, IKEA and Philips Hue devices still work to control over 3G/4G.

See screenshots for behaviour over Wi-Fi vs 4G:

Expected behavior

Possible to get status and control devices also over 4G/3G connection

Actual behavior

All HomeBridge devices are shown as "No Response"

Steps to reproduce

Disconnect wifi on the iPhone and try to access the Homebridge devices.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Homebridge will not show up in ios using version 2.0

Problem/Motivation

I had homebridge working on my Rapi3 but after updating to homebridge 2.0 I can no longer get it to show up on HomeKit on my ios devices. The HomeKit scan will also not recognize the HomeKit Code

Expected behavior

I would expect that when the ios scanner is used on the displayed code it would recognize it and then the accessories would appear in the Home app

Actual behavior

The HomeKit scanner does not detect the displayed code and no accessories appear in the app when the code is manually entered

Steps to reproduce

Using this configuration:
{
"log_level": "info",
"avahi_interfaces": "eth0,wlan0",
"avahi_hostname": "",
"avahi_domainname": "local",
"enable_ipv6": false,
"packages": [],
"init_commands": [],
"plugins": [
"homebridge-mqtt-temperature",
"homebridge-mqtt-switch-tasmota",
"homebridge-radiothermostat",
"homebridge-chamberlain"
]
}

Produces these logs:

Logs
[cont-init.d] 50-config.sh: executing...
[cont-init.d] 50-config.sh: exited 0.
[cont-init.d] 60-ipv6-hotfix.sh: executing...
patching file /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js
[cont-init.d] 60-ipv6-hotfix.sh: exited 0.
[cont-init.d] 80-user-packages.sh: executing...
[cont-init.d] 80-user-packages.sh: exited 0.
[cont-init.d] 81-user-scripts.sh: executing...
[cont-init.d] 81-user-scripts.sh: exited 0.
[cont-init.d] 82-user-plugins.sh: executing...

[email protected]
added 73 packages in 26.125s
[email protected]
added 73 packages in 10.864s
[email protected]
added 54 packages in 19.116s
[email protected]
added 6 packages in 4.435s
[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.
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. ***
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 wlan0.IPv4 with address 192.168.1.32.
New relevant interface wlan0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.38.
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.1.32 on wlan0.IPv4.
Registering new address record for 192.168.1.38 on eth0.IPv4.
Server startup complete. Host name is hassio.local. Local service cookie is 1316513680.
*** 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
[10/23/2017, 6:44:21 PM] Loaded plugin: homebridge-chamberlain
[10/23/2017, 6:44:22 PM] Registering accessory 'homebridge-chamberlain.Chamberlain'
[10/23/2017, 6:44:22 PM] ---
[10/23/2017, 6:44:22 PM] Loaded plugin: homebridge-homeassistant
[10/23/2017, 6:44:23 PM] Registering platform 'homebridge-homeassistant.HomeAssistant'
[10/23/2017, 6:44:23 PM] ---
[10/23/2017, 6:44:26 PM] Loaded plugin: homebridge-mqtt-switch-tasmota
[10/23/2017, 6:44:26 PM] Registering accessory 'homebridge-mqtt-switch-tasmota.mqtt-switch-tasmota'
[10/23/2017, 6:44:26 PM] ---
[10/23/2017, 6:44:26 PM] Loaded plugin: homebridge-mqtt-temperature
[10/23/2017, 6:44:26 PM] Registering accessory 'homebridge-mqtt-temperature.mqtt-temperature'
[10/23/2017, 6:44:26 PM] ---
[10/23/2017, 6:44:27 PM] Loaded plugin: homebridge-radiothermostat
[10/23/2017, 6:44:27 PM] Registering accessory 'homebridge-radiothermostat.RadioThermostat'
[10/23/2017, 6:44:27 PM] ---
[10/23/2017, 6:44:27 PM] Loaded config.json with 4 accessories and 1 platforms.
[10/23/2017, 6:44:27 PM] ---
[10/23/2017, 6:44:27 PM] Loading 1 platforms...
[10/23/2017, 6:44:27 PM] [HomeAssistant] Initializing HomeAssistant platform...
[10/23/2017, 6:44:27 PM] [HomeAssistant] Please set default_visibility in config.json to "hidden" or "visible".
[10/23/2017, 6:44:27 PM] [HomeAssistant] Fetching HomeAssistant devices.
[10/23/2017, 6:44:28 PM] Loading 4 accessories...
[10/23/2017, 6:44:28 PM] [Thermostat] Initializing RadioThermostat accessory...
[10/23/2017, 6:44:28 PM] [Thermostat] Thermostat http://192.168.1.118
[10/23/2017, 6:44:28 PM] [Kims lamp] Initializing mqtt-switch-tasmota accessory...
[10/23/2017, 6:44:28 PM] [Kims lamp] Nazwa do RESULT POWER
[10/23/2017, 6:44:28 PM] [Second] Initializing mqtt-switch-tasmota accessory...
[10/23/2017, 6:44:28 PM] [Second] Nazwa do RESULT POWER
[10/23/2017, 6:44:28 PM] [Third] Initializing mqtt-switch-tasmota accessory...
[10/23/2017, 6:44:28 PM] [Third] Nazwa do RESULT POWER
[10/23/2017, 6:44:28 PM] [HomeAssistant] Received event: ping
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'CPU Temperature'...
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'Garage Ambient'...
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'Freezer'...
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'Second'...
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'Kim's Lamp'...
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'Third'...
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'all lights'...
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'Living Room'...
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'all devices'...
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'iPhone'...
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'Kim's iPad'...
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'Kim's iPad 4'...
[10/23/2017, 6:44:29 PM] [HomeAssistant] Initializing platform accessory 'Family Room Home'...
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:

┌────────────┐
│ 841-81-145 │
└────────────┘

[10/23/2017, 6:44:30 PM] Homebridge is running on port 51826.
[10/23/2017, 6:44:30 PM] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-10-24T11:25:56+00:00", "next_dusk": "2017-10-23T23:06:06+00:00", "next_midnight": "2017-10-24T05:15:13+00:00", "next_noon": "2017-10-24T17:15:18+00:00", "next_rising": "2017-10-24T11:54:47+00:00", "next_setting": "2017-10-24T22:35:50+00:00", "elevation": -2.29, "azimuth": 255.81, "friendly_name": "Sun"}, "last_changed": "2017-10-23T22:37:20.575769+00:00", "last_updated": "2017-10-23T22:43:30.554935+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-10-24T11:25:56+00:00", "next_dusk": "2017-10-23T23:06:06+00:00", "next_midnight": "2017-10-24T05:15:13+00:00", "next_noon": "2017-10-24T17:15:18+00:00", "next_rising": "2017-10-24T11:54:47+00:00", "next_setting": "2017-10-24T22:35:50+00:00", "elevation": -2.48, "azimuth": 255.98, "friendly_name": "Sun"}, "last_changed": "2017-10-23T22:37:20.575769+00:00", "last_updated": "2017-10-23T22:44:30.555779+00:00"}}, "origin": "LOCAL", "time_fired": "2017-10-23T22:44:30.555925+00:00"}

Proposed changes

Add CircleCI

Problem/Motivation

In order to keep up the quality of the repository/add-on, we need to have some continuous integration in place.

Expected behavior

To trigger a CircleCI job on each push & PR to assure everything is still in working order.
PR's SHOULD NOT be mergeable when the build fails.

Actual behavior

Currently, there is no CI present.

Cameras missing from config.json

Problem/Motivation

Looking at generated config.json. Should “cameras” be added to the “supported types” array to expose camera feeds ( FFMpeg ) components registered to HASSIO to Homebridge?

Feel free to point to docs for the format. Happy to contribute to documentation if that helps!

Expected behavior

If a camera ( Netatmo Welcome, Ring Doorbell Pro ) component is registered with the FFMpeg and is displaying images on the HASSIO homepage properly, I would expect that the cameras should be automatically exposed through homebridge to Apple Homekit apps as well.

Actual behavior

No cameras are exposed. Other devices are registered and available as Homekit accessories as expected.

Can't install addon

I'm receiving the following messages when trying to install this addon on a new Hass.io box I'm building:

17-10-09 22:40:57 INFO (SyncWorker_5) [hassio.dock.addon] Start build d89827df/amd64-addon-homebridge:1.0.3
17-10-09 22:40:57 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 422, in start
    resp = yield from self._request_handler(request)
  File "/usr/lib/python3.6/site-packages/aiohttp/web.py", line 306, in _handle
    resp = yield from handler(request)
  File "/usr/lib/python3.6/site-packages/hassio/api/util.py", line 31, in wrap_api
    answer = await method(api, *args, **kwargs)
  File "/usr/lib/python3.6/site-packages/hassio/addons/addon.py", line 466, in install
    if not await self.docker.install(self.last_version):
  File "/usr/lib/python3.6/site-packages/hassio/dock/util.py", line 18, in wrap_api
    return await method(api, *args, **kwargs)
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/lib/python3.6/site-packages/hassio/dock/addon.py", line 198, in _install
    return self._build(tag)
  File "/usr/lib/python3.6/site-packages/hassio/dock/addon.py", line 211, in _build
    image = self.docker.images.build(**build_env.get_docker_args(tag))
  File "/usr/lib/python3.6/site-packages/docker/models/images.py", line 175, in build
    raise BuildError(chunk['error'])
docker.errors.BuildError: invalid reference format: repository name must be lowercase

What am I doing wrong?

I cant pick colors on the color picker in from siri or the home app

Problem/Motivation

I need to be able to change colors from the home app but they don't change

Expected behavior

When i pick a color over homekit it will change the color of the lamp

Actual behavior

Only the first time i try to change the color from my iphone after i have changed the color from home assistant does it update. It doesnt update the color on the Hassio web interface so it is something to do with the plugin, not the lights.

Steps to reproduce

try changing colors of an rgb device

After the upgrade of version 2.0, the data obtained from the temperature and humidity sensors of the xiao mi is 0

After the upgrade of version 2.0, the data obtained from the temperature and humidity sensors of the xiao mi is 0. T T

Automatic restart needed

Problem/Motivation

Homebridge seems to die from time to time (don't know where to find the log, so I don't know the reason). But this is not deteced, so the hassio add-on is justed "stopped" and must be "started" again manually.

Expected behavior

Since I have selected Boot -> Auto, I expect the process to be automatically restarted if it dies. As I would from any other system daemon.

Actual behavior

The Homebridge add-on does not automatically start homebridge again if it dies.

Steps to reproduce

Just keep the add-on running for some days, and it will eventually die. I am using the homebridge-harmonyhub in addition to the standard configuration.

Proposed changes

Make the Homebridge add-on automatically start homebridge again if it dies.

Homegridge plugins often crash and stop services

Problem/Motivation

Homebridge services often crash after adding Xiaomi sockets(Both version WiFi version and Zigbee version )

Homebridge version 2.0.0 , Home Assistant version 0.56.2 ,

Expected behavior

Hoping to fix this bug ,homebridge service can be restarted automatically after service failure

Steps to reproduce

[10/25/2017, 6:48:56 PM] [HomeAssistant] Received event: {"event_type": "platform_discovered", "data": {"service": "load_platform.light", "platform": "yeelight", "discovered": {"host": "192.168.199.247", "port": 54321, "hostname": "yeelink-light-color1_miio57602464.local.", "properties": {"epoch": "1", "mac": "34ce008cfded"}, "mac_address": "34ce008cfded", "device_type": "rgb"}}, "origin": "LOCAL", "time_fired": "2017-10-25T10:48:56.806069+00:00"}
[10/25/2017, 6:48:56 PM] [HomeAssistant] Received event: {"event_type": "platform_discovered", "data": {"service": "load_platform.light", "platform": "yeelight", "discovered": {"host": "192.168.199.247", "port": 54321, "hostname": "yeelink-light-color1_miio57602464.local.", "properties": {"epoch": "1", "mac": "34ce008cfded"}, "mac_address": "34ce008cfded", "device_type": "rgb"}}, "origin": "LOCAL", "time_fired": "2017-10-25T10:48:56.806069+00:00"}
[10/25/2017, 6:48:56 PM] [HomeAssistant] Received event: {"event_type": "platform_discovered", "data": {"service": "load_platform.light", "platform": "yeelight", "discovered": {"host": "192.168.199.247", "port": 54321, "hostname": "yeelink-light-color1_miio57602464.local.", "properties": {"epoch": "1", "mac": "34ce008cfded"}, "mac_address": "34ce008cfded", "device_type": "rgb"}}, "origin": "LOCAL", "time_fired": "2017-10-25T10:48:56.806069+00:00"}
[10/25/2017, 6:48:56 PM] [HomeAssistant] Received event: {"event_type": "platform_discovered", "data": {"service": "load_platform.light", "platform": "yeelight", "discovered": {"host": "192.168.199.247", "port": 54321, "hostname": "yeelink-light-color1_miio57602464.local.", "properties": {"epoch": "1", "mac": "34ce008cfded"}, "mac_address": "34ce008cfded", "device_type": "rgb"}}, "origin": "LOCAL", "time_fired": "2017-10-25T10:48:56.806069+00:00"}
[10/25/2017, 6:48:56 PM] [HomeAssistant] Received event: {"event_type": "call_service", "data": {"domain": "group", "service": "set", "service_data": {"object_id": "all_lights", "name": "all lights", "entities": ["light.gateway_light_34ce008d52b4", "light.living_room"], "visible": false}, "service_call_id": "1965506896-8"}, "origin": "LOCAL", "time_fired": "2017-10-25T10:48:56.857105+00:00"}
[10/25/2017, 6:48:56 PM] [HomeAssistant] Received event: {"event_type": "call_service", "data": {"domain": "group", "service": "set", "service_data": {"object_id": "all_lights", "name": "all lights", "entities": ["light.gateway_light_34ce008d52b4", "light.living_room"], "visible": false}, "service_call_id": "1965506896-8"}, "origin": "LOCAL", "time_fired": "2017-10-25T10:48:56.857105+00:00"}
[10/25/2017, 6:48:56 PM] [HomeAssistant] Received event: {"event_type": "call_service", "data": {"domain": "group", "service": "set", "service_data": {"object_id": "all_lights", "name": "all lights", "entities": ["light.gateway_light_34ce008d52b4", "light.living_room"], "visible": false}, "service_call_id": "1965506896-8"}, "origin": "LOCAL", "time_fired": "2017-10-25T10:48:56.857105+00:00"}
[10/25/2017, 6:48:56 PM] [HomeAssistant] Received event: {"event_type": "call_service", "data": {"domain": "group", "service": "set", "service_data": {"object_id": "all_lights", "name": "all lights", "entities": ["light.gateway_light_34ce008d52b4", "light.living_room"], "visible": false}, "service_call_id": "1965506896-8"}, "origin": "LOCAL", "time_fired": "2017-10-25T10:48:56.857105+00:00"}
[10/25/2017, 6:48:56 PM] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "group.all_lights", "old_state": {"entity_id": "group.all_lights", "state": "on", "attributes": {"entity_id": ["light.gateway_light_34ce008d52b4", "light.living_room"], "order": 1, "auto": true, "friendly_name": "all lights", "hidden": true, "assumed_state": false}, "last_changed": "2017-10-25T10:44:56.921489+00:00", "last_updated": "2017-10-25T10:44:56.921489+00:00"}, "new_state": null}, "origin": "LOCAL", "time_fired": "2017-10-25T10:48:56.877066+00:00"}
/usr/lib/node_modules/homebridge-homeassistant/accessories/switch.js:35
        .setValue(newState.state === 'on', null, 'internal');
                          ^
TypeError: Cannot read property 'state' of null
    at HomeAssistantSwitch.onEvent (/usr/lib/node_modules/homebridge-homeassistant/accessories/switch.js:35:27)
    at EventSource.HomeAssistantPlatform.es.addEventListener (/usr/lib/node_modules/homebridge-homeassistant/index.js:63:19)
    at emitOne (events.js:96:13)
    at EventSource.emit (events.js:191:7)
    at _emit (/usr/lib/node_modules/homebridge-homeassistant/node_modules/eventsource/lib/eventsource.js:186:17)
    at parseEventStreamLine (/usr/lib/node_modules/homebridge-homeassistant/node_modules/eventsource/lib/eventsource.js:201:9)
    at IncomingMessage.<anonymous> (/usr/lib/node_modules/homebridge-homeassistant/node_modules/eventsource/lib/eventsource.js:164:11)
    at emitOne (events.js:96:13)
    at IncomingMessage.emit (events.js:191:7)
    at readableAddChunk (_stream_readable.js:178:18)
dbus-protocol.c: client :1.1 vanished.
/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 SIGTERM, quitting.
Leaving mDNS multicast group on interface hassio.IPv6 with address fe80::42:56ff:fe04:783c.
Leaving mDNS multicast group on interface hassio.IPv4 with address 172.30.32.1.
dbus[531]: [system] Reloaded configuration
Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::5dae:1777:ebe0:3897.
Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.199.185.
avahi-daemon 0.6.32 exiting.
[s6-finish] sending all processes the KILL signal and exiting.

Thank you for your help ：）

Git not found in $PATH (error installing plugin)

I'm running the latest hass.io installation on a Raspberry pi 3, with hostOS 1.1, Supervisor 0.72 and HA 0.56.

With the following config (avahi_hostname specified as instructed in another thread),

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

I get the following error(s):

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 10-homebridge: applying... 
[fix-attrs.d] 10-homebridge: exited 0.
[fix-attrs.d] 20-dbus: applying... 
[fix-attrs.d] 20-dbus: exited 0.
[fix-attrs.d] 30-avahi: applying... 
[fix-attrs.d] 30-avahi: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
**[17:30:02+0000] ERROR ----> Something went wrong contacting the API**
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to DEBUG
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
ERROR: Something went wrong contacting the API
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 20-dbus.sh: executing... 
[cont-init.d] 20-dbus.sh: exited 0.
[cont-init.d] 30-avahi.sh: executing... 
DEBUG: Detected Avahi interfaces: eth0
[cont-init.d] 30-avahi.sh: exited 0.
[cont-init.d] 50-config.sh: executing... 
[cont-init.d] 50-config.sh: exited 0.
[cont-init.d] 60-ipv6-hotfix.sh: executing... 
[cont-init.d] 60-ipv6-hotfix.sh: exited 0.
[cont-init.d] 80-user-packages.sh: executing... 
[cont-init.d] 80-user-packages.sh: exited 0.
[cont-init.d] 81-user-scripts.sh: executing... 
[cont-init.d] 81-user-scripts.sh: exited 0.
[cont-init.d] 82-user-plugins.sh: executing... 
npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EAI_AGAIN: request to https://registry.npmjs.org/inherits failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org:443
npm WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
npm ERR! code ENOGIT
**npm ERR! No git binary found in $PATH**
npm ERR! 
npm ERR! Failed using git.
npm ERR! Please check if you have git installed and in your PATH.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2017-10-22T17_30_15_812Z-debug.log
**FATAL: Failed installing plugin homebridge-harmonyhub**
[cont-init.d] 82-user-plugins.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.
[s6-finish] sending all processes the KILL signal and exiting.

Temperature incorrectly passing to HomeKit

The temperature being passed from the nest add on through the homebridge is incorrect. It's set to 72°F but shows 169°F in the Home app...any ideas it shows up correctly in Home Assistant.

install failed after upgrade HA to 0.55.0

Problem/Motivation

start failed

Expected behavior

start success

Actual behavior

starting version 3.2.2
[ADD-ON] Installing Homebridge plugin homebridge-harmonyhub
path.js:1138
if (i >} 0)
^
SyntaxError: Unexpected token }
at runInThisContext (bootstrap_node.js:437:20)
at NativeModule.compile (bootstrap_node.js:525:18)
at Function.NativeModule.require (bootstrap_node.js:471:18)
at startup (bootstrap_node.js:128:35)
at bootstrap_node.js:542:3
[ADD-ON][ERROR] An error occured!
!!! ERROR: Failed installing Homebridge plugin homebridge-harmonyhub

Steps to reproduce

start homebridge

Proposed changes

(If you have a proposed change, workaround or fix, describe the rationale behind it)

Siri will not lock or unlock a door. Home app will do this just fine.

Problem/Motivation

When requesting Siri lock a door, it reports back that it was locked but logging shows it was unlocked.

"Siri, lock the front door":

[8/25/2017, 7:13:04 PM] [Wink] Sending update: Front Door (lock/170874) { locked: false }
[8/25/2017, 7:13:04 PM] [Wink] Update sent successfully: Front Door (lock/170874)
Home app > unlock the front door:

[8/25/2017, 7:14:41 PM] [Wink] Sending update: Front Door (lock/170874) { locked: true }
[8/25/2017, 7:14:41 PM] [Wink] Update sent successfully: Front Door (lock/170874)

Expected behavior

Lock the door

Actual behavior

Door remains unlocked

Steps to reproduce

Request Siri to unlock or lock a door. It will report back that the command worked, but nothing happens.

Proposed changes

This was addressed in nfarina's homebridge instance by uplifting happ-nodejs:

homebridge/homebridge#1466
homebridge/homebridge@e874061

Cover command broken

Problem/Motivation

Wrong command is sent to open/close cover. This problem was solved on version 2.1.0 and now broken again with version 2.1.1. I’m using a template cover with open and close commands and optimistic mode on.

Expected behavior

When a cover is closed on Home app, the close cover service should be sent to HA. Like this log:
[2017-10-31 13:57:02] [HomeAssistant] Calling service open_cover on Casa

Actual behavior

According to the log, the command [2017-10-31 13:22:19] [HomeAssistant] Setting the state of the Sala to 0 is sent to HA. Nothing happens. The position is set to 0 but the close cover service is not started.

Steps to reproduce

Have a template cover with optimistic mode on on HA and configured with the Home App.

Proposed changes

As seen on previous version logs, it should send the close_cover service.

Ver 1.0.3 HomeAssistant Error adding xiao mi socket

/usr/lib/node_modules/homebridge-homeassistant/accessories/switch.js:35
.setValue(newState.state === 'on', null, 'internal');
^
TypeError: Cannot read property 'state' of null

node old version

Problem/Motivation

integration with telldus stopped working in hass.io see : johnlemonse/homebridge-telldus#55

Expected behavior

telldus plugin was upgraded, to support node 8, expected hass.io to also work

Actual behavior

didnt work

Steps to reproduce

reproducable in hass.io

Proposed changes

upgrade node

Homebridge will not show in iOS app / Possible mDNS conflict

This issue originated from hassio-addons/repository#5 by @marcelveldt

This issue originated from hassio-addons/repository#2 by @mihalski

Problem/Motivation

Homebridge won't show up in the Home app on my iOS device.
I've also checked with Bonjour Browser from my Mac and I don't see any references there to Homebridge.

Expected behavior

Homebridge/Homeassistant should show up in my Home app on iOS as accessory so I can connect with the PIN and have it discovering my devices.

Actual behavior

Homebridge doesn't show up at all.
I do notice some related error in the log:
Host name conflict, retrying with hassio-15

It should be noted that I changed the default hassio hostname to "home assistant" instead of "hassio".

Steps to reproduce

Not sure, just followed the default configuration steps.

Proposed changes

I did not yet test it, but I suppose it's related to the hostname change.

Full log attached
homebridge_log.txt

Version 2.0.0 won't start

After upgrading to version 2.0.0, the add-on won't start. Do I need to refresh or reset something? Have tried to uninstall/install and to reboot the host.

The log contains the following:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 10-homebridge: applying...
[fix-attrs.d] 10-homebridge: exited 0.
[fix-attrs.d] 20-dbus: applying...
[fix-attrs.d] 20-dbus: exited 0.
[fix-attrs.d] 30-avahi: applying...
[fix-attrs.d] 30-avahi: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
[06:59:33+0000] ERROR ----> Something went wrong contacting the API
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing...
ERROR: Something went wrong contacting the API
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 20-dbus.sh: executing...
[cont-init.d] 20-dbus.sh: exited 0.
[cont-init.d] 30-avahi.sh: executing...
ERROR: Something went wrong contacting the API
[cont-init.d] 30-avahi.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.
[s6-finish] sending all processes the KILL signal and exiting.