Hi, I am trying to get binary_sensor to show up but it appears that NPM (https://www.npmjs.com/package/homebridge-homeassistant) is not updated?

How do I get the latest (from here) to show up in homebridge? I'm running it in a docker container on a Synology NAS.

Thank you!

Hello!

Would I be able to access this sensor information from HomeKit using this plugin? It seems I won't, but wanted to check wether it would be possible or if it was something you could add support to if you have time for that

Thanks for this plugin!

Home Assistant recently updated to use cover instead of rollershutter or garagedoor, both of which as being deprecated in the next few releases: https://github.com/home-assistant/home-assistant/pull/2891/commits

I was thinking of updating the rollershutter accessory accordingly, but this recent PR brings to light another issue. What HomeKit service type should cover be?

I initially wrote the rollershutter accessory to use the HomeKit garage door type, in large part as a workaround for this issue -- essentially, I had my garage door opener implemented as a switch named garage door, but it wouldn't work with Siri because when you ask Siri to "open the garage door," it looks for a device of type garage door, independent of what you've named the switch. With rollershutter implemented as the HK garage door type, I can happily ask Siri whether my garage is open and everything is peachy.

However, the PR above brings up #5 again -- if a hass cover were implemented as HK garage door type, others wouldn't be able to use their hass covers as HK windowcovers, since homebridge-homeassistant uses the hass type to determine the accessory type.

If there were some kind of metadata or alternate way to specify a non-default type, people could customize to have e.g. a homeassistant switch that homebridge interprets as a garagedoor, or perhaps 2 different homeassistant covers -- one of which ends up as a HK garage door and the other as a HK windowcover. Does that make sense?

So, in absence of that functionality currently, if I update the rollershutter accessory to use hass's new cover, I would selfishly prefer it to be a HK garage door on the homebridge side, but thought I should open it up to see if there are better ideas on how to work around this issue.

As the title claims i dont get any devices registering.
Output for homebridge below

*** 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/10/2016, 10:08:38 AM] Loaded plugin: homebridge-homeassistant
homebridge API version: 2
[10/10/2016, 10:08:38 AM] Registering platform 'homebridge-homeassistant.HomeAssistant'
[10/10/2016, 10:08:38 AM] ---
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:

┌────────────┐
│ 031-45-154 │
└────────────┘

[10/10/2016, 10:08:42 AM] Homebridge is running on port 51826.

Config as follow

{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},

"platforms": [
    {
        "platform": "HomeAssistant",
        "name": "HomeAssistant",
        "host": "http://10.0.1.3:8123",
        "password": "********",
        "supported_types": ["light", "switch", "media_player"]
    }
]

}

I run Homebridge in a Docker with my HA instance also in a Docker on the same machine. I do not know if this is contributing to this issue.

When I restart the containers my Hue Lights from HA return to the default homekit room.
It does not happen with any other devices or lights such as my wemo and LIFX.

I thought that maybe if the entity_id was passed through as the serial number it may retain it room. I haven't had time to modify the light.js file to see if this will help.
This might be a good change regardless. The new Apple Home app shows the serial number and it could be helpful.

Homebridge crashes on load everytime I add/replace the platforms statement in config.json, any ideas?

{"platforms": [
  {
    "platform": "HomeAssistant",
    "name": "HomeAssistant",
    "host": "http://192.168.1.109:8123",
    "password": "pi",
    "supported_types": ["binary_sensor", "cover", "fan", "input_boolean", "light", "lock", "media_player", "scene", "sensor", "switch"]
  }
]}

I have spent hours and tried everything, thanks (commas, adding to the EOF, replacing existing0

Hi

First off great work incorporating Rollershutter. I use Rollershutter via mqtt to control my Garage Rollerdoor. I do so because it on screen it's UI is more intuitive than the Garage Door component which is just a switch. I discovered when I first started playing with it that OPEN & CLOSED referred to to the state of the actual Rollershutter rather than the state of the space it left. An open door means an open space that you can walk through but with Rollershutter, OPEN Rollershutter = CLOSED space which you cannot drive through. I didn't understand the logic at first but it does make sense to speak of it based on the state of the actual Rollershutter I guess.

I just changed the logic in my automation and lived with it but now the state is reversed in Apple's Home app once again with the new Rollsershutter support. On the HA UI if the UP arrow is active it means the Rollershutter is OPEN or DOWN and vice versa. Considering the service to actuate the Rollershutter is rollershutter.move_up & down respectively, can the state of the door be reported back to Homekit as UP or DOWN rather than OPEN or CLOSED. This will make it universal and can be used and understood by anyone irrespective of how they use the component.

Thanks

It would be nice to be able to control input booleans as switches from homekit

I got homebridge and homebridge-homeassistant installed and running on my Raspberry Pi, and I was able to add it to my Home app on my iPhone, but none of my Home Assistant devices are appearing. I just see a "Default Room Homebridge" and there's nothing in it.

I looked through the docs but it says all the Home Assistant devices are just supposed to appear magically. I don't see any errors being logged in the terminal where I'm running Homebridge.

I have the following in my config file:

{
    "bridge": {
        "name": "Homebridge",
        "username": "CC:22:3D:E3:CE:30",
        "port": 51826,
        "pin": "xxx-xx-xxx"
    },


    "platforms": [
        {
                "platform": "HomeAssistant",
                "name": "HomeAssistant",
                "host": "http://192.168.1.117:8123",
                "password": "xxxxxxxxxx",
                "supported_types": ["light", "switch", "media_player", "scene"]
        }
    ]
}

Password x'd out for obvious reasons.

How can I debug this? Any suggestions?

How do you know there is a new version to install?

Does this plug in auto update on a reboot?

How to you check installed version?

I dont see a current version number for the latest available plug in here on this site...

So in short how do I keep this up to date?

Thanks

Consider something like this:

• a scene in HA named Good Night
• homebridge-homeassistant exposes this as a switch
• in the Home iOS app, create a Good Night scene to switch Good Night on
• tell siri "Good Night"

After telling Siri Good Night, that turns on the Good Night switch, which tells Home Assistant to activate the scene. That is all good. However, the next day you check Home, and it shows the Good Night switch as still on. I haven't confirmed this, but I think this will prevent using Good Night a second time.

Hallo, i have following issue:

Okt 07 12:19:33 raspberrypi homebridge[571]: [2016-10-07 12:19:33] [HomeAssistant] Fetching HomeAssistant devices.
Okt 07 12:19:33 raspberrypi homebridge[571]: [2016-10-07 12:19:33] [HomeAssistant] Failed getting devices: Error: certificate has expired. Retrying...

it just happens, when auto starting homebridge with systemd on raspberry.
I don't get the the error when starting Homebridge by typing: homebridge

my configuration looks like this

{
  "bridge": {
    "name": "Homebridge",
    "username": "CC:22:3D:E3:CE:30",
    "port": 51826,
    "pin": "031-45-154"
  },
  "platforms": [
    {
      "platform": "HomeAssistant",
      "name": "HomeAssistant",
      "host": "http://myhomeassistantip:8123",
      "password": "mypassword",
      "supported_types": ["fan", "garage_door", "input_boolean", "light", "lock", "media_player", "rollershutter", "scene", "switch"]
    }
  ]
}

When I want to turn something on or off (a switch mainly) it says updating first when I press it or just pull up the bottom bar on iOS 10. Updating with little circle next to it and after like 5 seconds the switch (the button) becomes "alive". So as with Siri, first when I tell her to turn off she says she didn't hear back and when I tell her again the same thing instantly, she can do it.

Everything works just fine with http after setting up SSL on HA with a self signed cert and changing config.json to point to https instead of http I cannot get HB to start. Can capture output if necessary.

Cover devices will show up some times and then randomly disappear. Removing and re-adding homebridge doesn't work with adding it back.

Hi,

I would love it if you could add support for device_tracker entities.
I found this plugin: https://github.com/PeteLawrence/homebridge-people
It checks for people at home by scanning the network and it adds them as an OccupancySensor.
Maybe we can do the same for device_tracker entities?

I have a Garage Door Opener(ESP8266 E12 + MQTT) in my Home Assistant server. I read about the Cover support but Im unable to add the Garage Door to homebridge.
In configuration.yaml i add this:
customize:
cover.garage:
homebridge_cover_type: garage_door

In homebirdge/config.json:
"platforms": [
{
"platform": "HomeAssistant",
"name": "HomeAssistant",
"host": "http://192.168.0.19:8123",
"password": "XXXXX",
"supported_types": ["input_boolean", "garage_door", "cover", "fan", "light", "lock", "media_player", "scene",$
}

When hombridge is running i can see my Home Asssistant devices but no the Garage Door. Im missing something?

Regards,

Ayn way to ignore devices? I have a lot of devices and some can be directly managed via homekit.

Just added SSL to my HomeAssistant install.

HomeBridge now gives me this error in the log.

[HomeAssistant] Failed getting devices: Error: unable to verify the first certificate. Retrying...

Is this a limitation in the current plugin?

Can we get somehow a color picker for the lights?

reverse? thx

Is it possible to change the color of the lights?
From the documentation I understood that it's not, so here's a welcoming addition..

I tried renaming a device with customize in HA, then bounced both HA and Homebridge, but my iPhone still shows the old name. The new name is reflected in the Homebridge log.

Has anyone seen this? If so how can I get the name to change?

I have a temperature sensor reporting °C values. During the last night I got a value below 0°C and it was correctly handled in HA. Unfortunately this did not work with homebridge.

I could fix this by adding the following lines to sensors.js getServices():

this.sensorService
      .getCharacteristic(this.characteristic)
      .setProps({minValue: -50});

With -50°C I should be on the save side.

I am not sure if this is a good fix but for me it is working.

When using Haska I can use the flag haaska_name: Livingroom Ceiling Fan
to override the Hass friendly_name: Ceiling Fan that exists in the room "Living Room" since I have one in every room.
Is there any way to have a homebridge_name: ? option so
This way I can avoid duplicated UUID problems with the homebridge.

Working on motion sensors now, see #3.

Decided to upgrade to the latest ver yesterday. Has been running flawless for 3 months and am now getting crashes ever so often. Homebridge ver has stayed the same. Only plugin ver has changed and I'm running nothing but the homeassistant plugin. Latest message on screen was :

Verify Fail!
Layer Decrypt Fail!

Any clues as to what may be causing this.? It's running on a rock solid Debian install.

Kman

Hi,

I have problems with last version of home bridge-homeassistant and rollershuters (Fibaro FGRM-222), when I run homebridge I get:

[10/29/2016, 3:19:12 AM] [HomeAssistant] Initializing HomeAssistant platform...
Booting Platform
[10/29/2016, 3:19:12 AM] [HomeAssistant] Fetching HomeAssistant devices.
Plugin - DidFinishLaunching
[10/29/2016, 3:19:12 AM] [HomeAssistant] Initializing platform accessory 'PWS_temp_f'...
[10/29/2016, 3:19:12 AM] [HomeAssistant] Initializing platform accessory 'Detectores de movimiento en camaras interiores para Alarma'...
[10/29/2016, 3:19:12 AM] [HomeAssistant] Initializing platform accessory 'Dark Sky Apparent Temperature'...
[10/29/2016, 3:19:12 AM] [HomeAssistant] Initializing platform accessory 'Luz por movimiento en Planta Primera'...
[10/29/2016, 3:19:12 AM] [HomeAssistant] Initializing platform accessory 'Acuario'...
[10/29/2016, 3:19:12 AM] [HomeAssistant] Initializing platform accessory 'Detectores de sonido en camaras interiores para Alarma'...
[10/29/2016, 3:19:12 AM] [HomeAssistant] Initializing platform accessory 'Luz Planta Baja'...
[10/29/2016, 3:19:12 AM] [HomeAssistant] Initializing platform accessory 'PWS_dewpoint_c'...
[10/29/2016, 3:19:12 AM] [HomeAssistant] Initializing platform accessory 'PWS_heat_index_f'...
[10/29/2016, 3:19:12 AM] [HomeAssistant] Initializing platform accessory 'Persiana Oeste'...
/root/.nvm/versions/node/v6.7.0/lib/node_modules/homebridge-homeassistant/accessories/cover.js:133
      .on("get", this.stateCharacteristicGetFunction.bind(this));
      ^

TypeError: Cannot read property 'on' of undefined
    at Object.getServices (/root/.nvm/versions/node/v6.7.0/lib/node_modules/homebridge-homeassistant/accessories/cover.js:133:7)
    at Server._createAccessory (/root/.nvm/versions/node/v6.7.0/lib/node_modules/homebridge/lib/server.js:375:36)
    at Server.<anonymous> (/root/.nvm/versions/node/v6.7.0/lib/node_modules/homebridge/lib/server.js:361:32)
    at /root/.nvm/versions/node/v6.7.0/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:15:19
    at /root/.nvm/versions/node/v6.7.0/lib/node_modules/homebridge-homeassistant/index.js:205:7
    at Request.onResponse [as _callback] (/root/.nvm/versions/node/v6.7.0/lib/node_modules/homebridge-homeassistant/index.js:111:7)
    at Request.self.callback (/root/.nvm/versions/node/v6.7.0/lib/node_modules/homebridge-homeassistant/node_modules/request/request.js:186:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:191:7)
    at Request.<anonymous> (/root/.nvm/versions/node/v6.7.0/lib/node_modules/homebridge-homeassistant/node_modules/request/request.js:1060:10)

This is part of my HA config:

cover.salon1_level_5_0:
  friendly_name: Persiana Este
  homebridge_cover_type: rollershutter

cover.salon2_level_6_0:
  friendly_name: Persiana Oeste
  homebridge_cover_type: roller shutter

What am i doing wrong?

Native support should be added for as many of these classes as possible (meaning all those that cleanly map to HAP-NodeJS services).

• cold: On means cold (or too cold)
• connectivity: On means connection present Off = no connection
• gas: CO CO2 etc.
• heat: On means hot (or too hot)
• light: Lightness threshold
• moisture: Specifically a wetness sensor
• motion: Motion sensor
• moving: On means moving Off means stopped
• occupancy: On means occupied Off means not occupied
• opening: Door window etc.
• power: Power over-current etc
• safety: Generic on=unsafe off=safe
• smoke: Smoke detector
• sound: On means sound detected Off means no sound
• vibration: On means vibration detected Off means no vibration

In the spirit of contribution, I created an image for setting up homebridge/homebridge-homeassistant. (props to @valentinalexeev who created this for RPi first).

This should clean up a lot better once NPM is updated with the recent commit addressing external config files. For now the configuration is pretty sketchy. .

On Docker Hub

If it's useful to fork/include and/or share in the README, go for it. If not, feel free to close the issue.

I'm trying out Apple's new Home app. It seems to want the brightness in addition to the state.

Setting it from the Home app works fine. It is only when fetching the brightness when refreshing/updating the status that it is returned as 0% when the light is on.

Is this because it incorrectly interprets toggle switches/lights as dimmers or because of the way they are exposed via the bridge? In Home Assistant they appear as simple toggle/binary switches.

Here is the last part of the log when opening the Home app and then using it to toggle a light.

Jul 20 07:33:48 raspberrypi homebridge[2297]: [7/20/2016, 7:33:48 AM] [HomeAssistant] fetching brightness for: Eetkamer Tafellig Jul 20 07:33:48 raspberrypi homebridge[2297]: [7/20/2016, 7:33:48 AM] [HomeAssistant] fetching power state for: Eetkamer Tafellig Jul 20 07:34:48 raspberrypi homebridge[2297]: [7/20/2016, 7:34:48 AM] [HomeAssistant] Setting power state on the 'Ganglig' to on Jul 20 07:34:48 raspberrypi homebridge[2297]: [7/20/2016, 7:34:48 AM] [HomeAssistant] Setting brightness on the 'Ganglig' to 100 Jul 20 07:34:48 raspberrypi homebridge[2297]: [7/20/2016, 7:34:48 AM] [HomeAssistant] Successfully set power state on the 'Ganglig' to on Jul 20 07:34:48 raspberrypi homebridge[2297]: [7/20/2016, 7:34:48 AM] [HomeAssistant] Successfully set brightness on the 'Ganglig' to 100 Jul 20 07:35:00 raspberrypi homebridge[2297]: [7/20/2016, 7:35:00 AM] [HomeAssistant] Setting power state on the 'Ganglig' to off Jul 20 07:35:01 raspberrypi homebridge[2297]: [7/20/2016, 7:35:01 AM] [HomeAssistant] Successfully set power state on the 'Ganglig' to off

Any plans to also support Home Assistant alarms or is the idea that the goodnight scene in the Home/Homekit apps simply actives a similar scene in Home Assistant.

Not sure what other use cases there are, but the ultimate goal is to only expose Home Assistant to the Internet via Home/Homekit in order to piggyback on Apple's security between devices.

Is it posible to add input slider? Could be used to control mini split AC units thru LIRC command line

Since we now have position in HomeAssistant for z-wave rollershutters, is it possible to switch the blinds "GarageDoor" implementation to a WindowCovering?

This would allow for positioning like: "close my shutter to 30%"

after much installation woes and setting up avahi..

it is working.. and importing lights and a couple scenes....

I have binary sensors setup in the home assistant son

in home assistant I defined a binary sensor for a smoke detector and set its class to smoke but its not showing up

I have tried deleting persists
i have restarted numerous times
I have delted the home in home app and re-imported home bridge... nothing working

what am I doing wrong

also my plex devices dont show up either

all working fine in home assistant

After installing homebridge and this plugin and changing the config.json. I started homebridge and it recognizes the plugin but it seems not to really search after Home Assistant, also no switches or lights appears in any Home Kit App.
Log of Homebridge.

Cover component reports closed when door is actually open. Cover Type is set to

'homebridge_cover_type: garage_door'

When I push Garage Door button on Home app when the door is Closed (state confirmed in HA) as the door begins to open the Home app changes from CLOSED to OPENING... When the door has opened (state confirmed in HA) Home App displays CLOSED.

Push button again and door starts to close (even though it displays CLOSED) but Home App displays Opening... (because it thinks it was closed) until it actually closes and then changes to Closed. So either condition is CLOSED.

All my automations are working correctly in HA so it's not a HA issue.

***** UPDATE *****

Further to this I have discovered that if you close Home App or control panel favorites, and re-open (forcing an update) it after the door is confirmed OPEN it reports the door correctly as OPEN. So effectively it changes from CLOSED to OPEN on update but not when you initially push the key so in effect you need to do it twice. Also the notification from Home App says Garage Door is Closed, when it opens. There is something wrong with the logic somewhere.

Thanks

Apparently some of my devices have the same name.

[4/29/2016, 7:59:59 PM] [HomeAssistant] Initializing platform accessory 'television'...
[4/29/2016, 7:59:59 PM] [HomeAssistant] Initializing platform accessory 'FIBARO System FGS222 Double Relay Switch 2x1.5kW Switch'...
[4/29/2016, 7:59:59 PM] [HomeAssistant] Initializing platform accessory 'Wenzhou TKB Control System TZ66D Dual Wall Switch Switch'...
[4/29/2016, 7:59:59 PM] [HomeAssistant] Initializing platform accessory 'FIBARO System FGS222 Double Relay Switch 2x1.5kW Switch'...
/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:219
      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: 819122ee-5ae0-4ddd-80ee-e6531dcee5c1
    at Bridge.Accessory.addBridgedAccessory (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:219:13)
    at Server.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/server.js:346:24)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:15:19
    at /usr/local/lib/node_modules/homebridge-homeassistant/index.js:146:7
    at Request.onResponse [as _callback] (/usr/local/lib/node_modules/homebridge-homeassistant/index.js:79:7)
    at Request.self.callback (/usr/local/lib/node_modules/homebridge-homeassistant/node_modules/request/request.js:200:22)
    at emitTwo (events.js:100:13)
    at Request.emit (events.js:185:7)
    at Request.<anonymous> (/usr/local/lib/node_modules/homebridge-homeassistant/node_modules/request/request.js:1067:10)
    at emitOne (events.js:95:20)

I can't really change this since those are z-wave devices which are named automatically - they actually don't really have the same name but maybe the name is too long? and therefore gets truncated?

switch.wenzhou_tkb_control_system_tz66d_dual_wall_switch_switch_66
switch.wenzhou_tkb_control_system_tz66d_dual_wall_switch_switch_71

and maybe

switch.fibaro_system_fgs221_double_relay_switch_2x15kw_switch_25
switch.fibaro_system_fgs221_double_relay_switch_2x15kw_switch_25_2
switch.fibaro_system_fgs221_double_relay_switch_2x15kw_switch_26
switch.fibaro_system_fgs221_double_relay_switch_2x15kw_switch_26_2
switch.fibaro_system_fgs221_double_relay_switch_2x15kw_switch_3
switch.fibaro_system_fgs221_double_relay_switch_2x15kw_switch_4
switch.fibaro_system_fgs221_double_relay_switch_2x15kw_switch_4_2
switch.fibaro_system_fgs222_double_relay_switch_2x15kw_switch_68
switch.fibaro_system_fgs222_double_relay_switch_2x15kw_switch_68_2

are somehow causing the problems?

I actually don't really need all of those in homekit but it seems there is no way to omit some. Can't homebridge-homeassistant just ignore the devices with same name or iterate them?

In Home Assistant i can see the Fibaro Shutters on the Dashboard as "Cover" and i can use it in the Browser without problems (arrows open / close).

Homebridge is installed (and well configurated) and things like some Switches (and some Hue Lamps) will be shown in Home App and i can use them with Siri.

My problem is that the Rollershutters (and the temperature sensors) will not be shown in Homebridge, because they are not included.

Is this normal that only Switches will be included into this Homebridge Plugin.

i have problem,

• after install everything
• pair phone with homebrige
• add home assistant plugin
  -add home assistant platform in config
  -add accessories with name "light"
  i have following error ..
  Please help me to set it, and run it.. I cant find more info about how to do it.. Thanks.

throw new Error("The requested accessory '" + name + "' was not registered by any plugin.");
Error: The requested accessory 'light' was not registered by any plugin.

In latest version, sensors are now showing (awesome!), but binary sensors are not. Here's my config.

{
  "bridge": {
    "name": "Homebridge",
    "username": "CC:22:3D:E3:CE:30",
    "port": 8128,
    "pin": "031-45-154"
  },
  "platforms": [
    {
      "platform": "HomeAssistant",
      "name": "HomeAssistant",
      "host": "http://192.168.1.242:8123",
      "password": "password",
      "supported_types": [
        "binary_sensor",
        "fan",
        "light",
        "lock",
        "scene",
        "sensor",
        "switch"
      ]
    },
    {
      "platform": "Nest",
      "token": "token",
      "clientId": "client",
      "clientSecret": "secret",
      "code": "code"
    },
    {
      "platform": "LiftMaster2",
      "username": "username",
      "password": "password"
    }
  ]
}

I have a RBP3 and get this message when starting homebridge.

TypeError: Cannot read property 'username' of undefined
at Server.loadConfig (/usr/local/lib/nodemodules/homebridge/lib/server.js:199:31)
at new Server (/usr/local/lib/node_modules/homebridge/lib/server.js:49:23)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:26:16)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:134:18)

This is what my config.json looks like.

{
"Bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"platforms": [
{
"platform": "HomeAssistant",
"name": "HomeAssistant",
"host": "http://_...__:8123",
"password": "_**",
"supported_types": ["light"]
}]
}

Unless I missed something in the configuration it seems that state changes (i.e. switching a light) are not reported to homebridge.

It would be nice if the two "views" would be consistent.

thats the json of one my thermostats:
thermostat.badezimmer_mode_9
{
"max_temp": 35,
"fan": "off",
"battery_level": 45,
"node_id": 9,
"min_temp": 7,
"current_temperature": 25,
"target_temp_low": 21,
"temperature": 21,
"unit_of_measurement": "°C",
"current_operation": "Comfort",
"target_temp_high": 21,
"friendly_name": "Bad Thermostat"
}
i would love to have the characteristics in bold avail. in homebridge.
i had them before with homebridge-zway.. but now i use openzwave to get it working with home-assistant.
battery_level and current_operationsare optional for me, because i just use temperature to set the target temperature and current_temperature to know the current temperature in the room

Running HomeAssistant 0.27 and just updated to latest Homebridge and Homebridge-homeassistant. Seeing this error which stops Homebridge. Also I am not seeing rollershutters or door locks either, I added rollershutters to the config.json.

http://pastebin.com/gPTAtWZ1

Thanks in advance for this killer plugin, and for updating it from legacy. It's a key link in my system, where I use Home Assistant as the central player but also use Siri and an Amazon Echo to run commands through Home Assistant (so it can keep track of states and be in charge of more advanced automation as things expand).

I've recently run into a minor issue -- after a modest amount of work, I've finally made a custom garage door opener, complete with state detection. It's working great with Home Assistant, and I can use my Echo to control it by voice, and it even works on HomeKit iOS apps. Its backend is a small script that is called by the command_line switch component.

The issue is that I'd like to be able to call the "friendly name" something like "garage" or "garage door," but when I try to tell Siri to "turn on the garage door" (using turn on / off because the component is a switch), Siri tells me she can't find any garage doors. I'm thinking this is because garage door is a defined type in HomeKit, and she is looking for a HMServiceTypeGarageDoorOpener.

I'm really hoping to get this working with Siri, so I've thought of a couple potential workarounds:

• Rename the device something that doesn't involve the word "garage" and continue to use as a switch
• Make a homebridge-homeassistant patch to allow a garage door accessory type

I think the second option seems more like the "right way" to do it, and while I hardly know any Javascript, there are already a few projects that implement HAP-NodeJS's Service.GarageDoorOpener that I could probably use to help me figure out how to make a new homebridge-homeassistant accessory type.

However, I'm not sure how to best determine whether or not a switch should be a GarageDoorOpener. Toying with the Hass REST API, there doesn't seem to be any additional metadata exposed with a switch where I could put some kind of flag -- really just the entity_type.friendly_name (e.g. switch.my_first_switch).

So in terms of ways to get homebridge-homeassistant to recognize that a switch should be given a special accessory type, I've thought of a few potential solutions:

• Perhaps add a config option -- off by default to avoid breaking any existing functionality -- to parse part of the friendly name as a "flag"
  • For example, entity_id: switch.garagedoor_garage
  • If the config var is set to "look for special accessory types", then look for the garagedoor_ prefix, strip it out (for the "friendly name"), and set this as a GarageDoorOpener accessory
  • While this solution seems a little sloppy to me, the big advantage would be that it would be very simple for users to implement the very flexible Home Assistant switch component as a number of different HomeKit service types
• I could try to write a new Home Assistant garage-door command_line component, then simply have homebridge-homeassistant look for the garage_door entity_type
• I could maybe adapt the existing Command Line Rollershutter component and have homebridge-homeassistant recognize a rollershutter entity_type as a GarageDoorOpener

Before I start chugging away at one of these, I thought I'd open up an issue for discussion. @maddox -- do any of these sound like reasonable solutions that you'd consider pulling in so others could also take advantage?

Am I missing an obvious simple alternative to get Siri to find my switch named "garage"?

Hi! Since I updated homebridge to it latest version, I'm getting a lot of errors (well, the same all the time), and now when I tell Siri to turn off all the lights, some of them stay on.
This is the error from homebridge log:

TypeError: Cannot read property 'length' of undefined
    at /usr/local/lib/node_modules/homebridge-homeassistant/index.js:115:31
    at Request.onResponse [as _callback] (/usr/local/lib/node_modules/homebridge-homeassistant/index.js:69:9)
    at self.callback (/usr/local/lib/node_modules/homebridge-homeassistant/node_modules/request/request.js:199:22)
    at emitOne (events.js:77:13)
    at Request.emit (events.js:169:7)
    at Request.onRequestError (/usr/local/lib/node_modules/homebridge-homeassistant/node_modules/request/request.js:821:8)
    at emitOne (events.js:77:13)
    at ClientRequest.emit (events.js:169:7)
    at Socket.socketErrorListener (_http_client.js:256:9)
    at emitOne (events.js:77:13)
/usr/local/lib/node_modules/homebridge-homeassistant/index.js:115
      for (var i = 0; i < data.length; i++) {

This is going to be an interesting one because there are many different kinds of sensors in Home Assistant. It would be best if at a minimum the state and possibly unit of measurement was used.

Also seeing this in latest version. Probably related to all of my sensors? I am running 0.31.1 in HA.

http://pastebin.com/RkDW0Gy9