[RELEASE] Home Assistant Device Bridge (HADB)

⚙️ Custom Apps and Drivers Custom Drivers
, ,
1

HADB 2.20

With this driver and app combination, Hubitat Elevation owners can take advantage of devices and integrations running on Home Assistant for use in automations on Hubitat Elevation

HADB
HADB854×466 39.8 KB

Table of contents

  1. Features
  2. Compatible Devices
  3. Requirements
  4. Installation
  5. Setup
    a. Create an HA Long-Lived Access Token
    b. Filter by Type or Search
  6. Advanced options
  7. Troubleshooting
  8. Submitting new device support requests

Acknowledgments

  • @ymerj for the initial build and ongoing dedication to support the community
  • @ogiewon, @tomw, @stephack, @enishoca and many others that have contributed to Home Assistant Device Bridge

Features

:white_check_mark: Devices from Home Assistant appear in Hubitat Elevation, fully functional and ready for use in Hubitat apps such as Rule Machine
:white_check_mark: Virtual devices are not required
:white_check_mark: Keep your automations on Hubitat
:white_check_mark: No MQTT broker needed
:white_check_mark: No additioinal device setup required
:white_check_mark: No custom firmware flashing

Compatible Device Types

Device types that can be imported by Home Assistant Device Bridge

Cover

    Device Type Generic Component Driver
    Blind Generic Component Window Blind
    Curtain Generic Component Window Shade
    Door Control Generic Component Door Control
    Garage Door Generic Component Garage Door Control
    Shade Generic Component Window Shade

Actuators

    Device Type Generic Component Driver
    Button Generic Component Pushable Button
    Climate Generic Component Thermostat
    Device Tracker Generic Component Contact Sensor
    Event Generic Component Event
    Fan Generic Component Fan Control
    Humidifier Generic Component Humidifier
    Input Boolean Generic Component Switch
    Light Generic Component Dimmer
    Lock Generic Component Lock
    Media Player Generic Component Media Player
    Select Generic Component Select
    Siren Generic Component Siren
    Switch Generic Component Switch
    Text Generic Component Text
    Vacuum Generic Component Vacuum
    Valve Generic Component Valve

Sensors

    Device Type Generic Component Driver
    Battery Generic Component Battery
    Energy Generic Component Energy Meter
    Environment Generic Component Carbon Dioxide Sensor
    Environment Generic Component Gas Detector
    Environment Generic Component Radon Sensor
    Environment Generic Component Volatile Organic Compounds Sensor
    Environment Generic Component PM25
    Humidity Generic Component Humidity Sensor
    Illuminance Generic Component Illuminance Sensor
    Number Generic Component Number
    Power Generic Component Power Meter
    Pressure Generic Component Pressure Sensor
    Temperature Generic Component Temperature Sensor
    Time Generic Component TimeStamp Sensor
    Voltage Generic Component Voltage Sensor

Binary Sensors

    Device Type Generic Component Driver
    Door Generic Component Contact Sensor
    Garage Door Generic Component Contact Sensor
    Lock Generic Component Contact Sensor
    Moisture Generic Component Water Sensor
    Motion Generic Component Motion Sensor
    Moving Generic Component Acceleration Sensor
    Occupancy Generic Component Occupancy Sensor
    Opening Generic Component Contact Sensor
    Presence Generic Component Presence Sensor
    Smoke Generic Component Smoke Detector
    Vibration Generic Component Acceleration Sensor
    Window Generic Component Contact Sensor
    After import, devices joined to Home Assistant will be available for control from Hubitat Elevation, and can be used in Hubitat apps and Rule Machine rules, just as you would any other locally joined device.

Requirements

  1. Hubitat Elevation hub :grin:

  2. Home Assistant (This isn't difficult to get setup for our goal of simply importing devices)

  3. Recommended installation method is to use the community built Hubitat Package Manager

If you prefer, you can manually install Home Assistant Device Bridge driver and app on your Hubitat Elevation hub

NOTE: This driver uses the Generic Component Drivers built into Hubitat Elevation. If the Generic Component Drivers do not exist on Hubitat, you may request a custom driver, but there are no guarantees this will be possible. We therefor must emphasize that specialized or complicated devices may require a more direct solution than this integration was ever intended for.

  • IMPORTANT: This integration adds devices from Home Assistant using their Entity ID. If you want Hubitat devices shared with Home Assistant, you should check out the Hubitat Integration from @jason0x43. It does the opposite of this integration and imports Hubitat devices into Home Assistant.

Installation

If you've never installed an app or driver on your hub, it is highly recommended to use Hubitat Package Manager. You can either learn to do that first, or you can simply install the Home Assistant Device Bridge App and Driver.

How to install a custom driver in Hubitat Elevation

How to install a custom app in Hubitat Elevation

Setup

Enter the IP address of Home Assistant and the Long-Lived Access Token (see instruction below)

HADB 2.0 app
HADB 2.0 app2344×1639 243 KB

How to create a Long-Lived Access Token on Home Assistant

  1. Press on your user account in Home Assistant
    Screen Shot 2021-03-03 at 6.51.37 PM

  2. Select the Security tab at the top

    HA security tab
    HA security tab1846×506 36.4 KB

  3. Scroll down to the bottom and select CREATE TOKEN
    Screen Shot 2021-03-03 at 6.52.15 PM

  4. Name your token (This can be any name you want.) and then press OK.
    Screen Shot 2021-03-03 at 7.48.13 PM

  5. Copy the token. It isn't accessible after creating it, so if you forget to record it somewhere and need it again later, just delete the old one and create a new token for use in Home Assistant Device Bridge.
    Screen Shot 2021-03-03 at 7.48.49 PM

  1. Paste the Long-Lived Access Token in the HADB app where indicated, then press Discover and select devices to poll Home Assistant for a list of compatible entities.

  2. Press Done when finished selecting the devices to ensure the Long-Lived Access Token and the devices selected for import are saved

HADB 2.0 app select devices
HADB 2.0 app select devices2344×1639 230 KB

Filter by Type or Search by Entity Name or ID

Starting with HADB 2.20, you can now filter by Entity Type, or use the search field to narrow the results by Name or Entity ID

HADB search by type
HADB search by type950×1234 72.5 KB
|
HADB search by name
HADB search by name972×617 18.9 KB

  1. Confirm and adjust which devices should be imported. You can adjust this later if you make a mistake or change your mind.

HADB select devices
HADB select devices2247×1207 223 KB

  1. Press Done

In your list of Hubitat drivers, you will see the Home Assistant Device Bridge parent device (or the custom name you set in the app). When the device state updates on Home Assistant, each compatible entity will create a child device on your Hubitat Elevation hub.

Done selecting HADB devices
Done selecting HADB devices2352×932 122 KB

  • IMPORTANT: Devices will appear automatically only after a change has occurred to the device you have selected for import to Hubitat.

A device will not be added to the list of child devices under the Home Assistant Device Bridge parent driver, until a change occurs on the device.

  • Example: A motion sensor will not appear in the list of devices on Hubitat until it is triggered for the first time after selecting it in the list of available entities from Home Assistant.
  • Example of imported child devices (each will appear on first activity after selecting them for Import to Hubitat)

Screen Shot 2021-03-03 at 8.41.35 PM

  • NOTE: Only devices that currently have the appropriate Generic Component device driver and are also listed as compatible devices will be imported to Hubitat Elevation.

Administration Option

Remove all child devices that are not currently selected (use carefully)

This is a cleanup method. Please use it carefully, as it will remove all of the HADB specific child devices from your Hubitat Elevation hub that are not selected in the list of devices to include.

Troubleshooting

IMPORTANT: Devices will appear automatically when a change occurs the first time after selecting them for import to Hubitat. A device will not be added to the list of child devices under the Home Assistant Device Bridge parent driver, until a change occurs on the device.

Example: A motion sensor will not appear in the list of devices on Hubitat until it is triggered for the first time after selecting it in the list of available entities from Home Assistant.

Submitting new device support requests

IMPORTANT: Home Assistant Device Bridge is intended to support very simple devices and sensors. We therefor must emphasize that specialized or complicated devices may require a more direct solution than this integration was intended for.

  1. Please enable logging on the parent virtual device
  2. Actuate your device (i.e. Open and Close, or Turn ON and Turn OFF, etc.).
  3. Include these debug logs with your request so we can analyze the information sent by Home Assistant through the Home Assistant Device Bridge driver (This information is essential in determining if your requested device can be added to Home Assistant Device Bridge).
59 Likes
2

Very nice write-up! Thank you for doing this!!

6 Likes
3

This is an awesome write up and app and set of drivers.

I had started using this (just) then I had the unfortunate happen, it was fast once all devices I wanted were added, and nice and smooth.

The ConBee on my deCONZ went some sort of mental :crazy_face: (lost its channel and all my lights, maybe I just overworked it), so I have had to ditch it :cry:

So I've had to move all lights to my C7 (I got so fed up with the Hue bridge). Once I replace the dead stick, I'll be back here to try it again. :+1:

2 Likes
4

So I've had to move all lights to my C7 (I got so fed up with the Hue bridge)

I thought this was not recommended as HUE does not conform fully to Zigbee and causes issue on the mesh. If it works it would be nice to lose the hub.

1 Like
5

If you have only Hue lights, no problem. They repeat for themselves just fine. So with a second controller that has all your other Zigbee devices, and this driver bringing them back into HE, you'd have no conflicts.

6

I didn't want to mess with having to run deCONZ on a Pi or PC, so I went with the built in ZHA integration that @stephack is also using and that works great. I've no need to import devices to anywhere but an HE hub, and I can do that on multiple hubs by either installing the driver on each hub, or using Hub Mesh.

2 Likes
7

You can run it from within HA, no need for another PI :smiley:
Its in the Add on store, and then you add Integration as per normal.
You can browse to Phoscon, and also VNC to deCONZ.

This is how I had it set up, and was working really well. Until said Conbee took a nose dive :cry:
It was also much easier to deal with Groups rather than that bloody yaml!!

8

I didn't have much choice, as I needed lights and wasn't reinstalling the Hue if I could get away with it.

I have all my ZHA devices on Hub 1, and ZLL on my C7, even a few Xiaomi wireless switches, all working quite well.

That said, I haven't migrated all my Z-wave to the C7 yet, so anything could (and probably) will happen. I'm holding off pulling the trigger on a Conbee II for now, I'll see how this continues. The only downside is, my Osram bulbs will have nothing of the C7, they aren't picked up at all. Luckily, I had some spare INNR bulbs, and they connected with zero issues.

1 Like
9

Yes, I read that, but also read advice that it's not as stable as having it on a separate computer. :man_shrugging:

Are you sure it's the ConBee that is pooched or is it deCONZ?
Groups on HA mean nothing to me personally and YAML can bite me. I'm literally using this as a Zigbee coordinator and not much else. I do have a few simple HA automations so I can sync my Lutron Connected Bulb Remotes back to HE using @jason0x43 's integration, and I've moved my Sonos over because my Symfonisk knob kept dropping off HE and doesn't drop off the ConBee 2. Other than that, I'm not using HA for anything else at this time.

I tried my hand a YAML and it SUCKS. No bloody way I'm dealing with maintaining that. So far, nothing I've done needs it.

1 Like
10

I'm not finding the YAML too bad, and hopefully a one time thing (unless they break things).

I'm fairly sure it was the stick at fault, it changed channel all on its own, and wouldn't be changed either, even after a full reset. I did consider using one of my HE sticks, but it recommended flashing it first. At that point I went back to the C7 to add the bulbs lol.

My Bruv has a Conbee 2, and that's working great in the manner mine was, that said he only has a handful of devices, as he's just started.

And no one needs any knob to be dropping off!! :smiley:

1 Like
11

Hang on to your knobs, for sure.

1 Like
12

Ouch. I just migrated all my devices from my Nortek stick to Conbee2 during the Christmas break. Very happy with it (using ZHA btw). However, if I was starting over I would have definitely considered one of the 2 coordinators that Tube is offering:

I did buy the Tube router and it's working very well and allowed me to remove 3 of my Iris outlets that were there only to stabilize my mesh. I plan to remove a few more Irus devices but I'm doing it slowly so I don't destabilize my existing mesh.

The Tube coordinators connect directly to the network (z2m) so it can be placed in a prime location away from other noisy devices. Worth a look if you might be starting over.

Edit: I edited the line to remove "connect via USB option" I mentioned above as I believe that was inaccurate.

3 Likes
13

Oh wow now that's a gorgeous little box!! Wonder if he ships to UK :slight_smile: (if and when he gets more!).

I considered taking one of my Xbee 3's off HE and sticking that on HA, still might yet as I've been more than happy with them repeating on HE. They don't look as nice as those, but they aren't too bad, if I say so myself :smiley:

1 Like
14

He does..someone asked just the other day.

1 Like
15

@ogiewon (accidentally :joy:) pointed me to this. Not that he was holding out or anything. :wink:
Only thing that stopped me from returning my ConBee 2 and switching to it (other than being out of stock and under high demand) there's no real benefit for me personally. Small house, so range issues are easily overcome with Trådfri outlets or repeaters. Already using my Xbee for the distant devices in my backyard. And there's only anecdotal evidence that the Tube coordinator works with Xiaomi, which is the primary value of any of this for me.

But the router does sound great. I'm torn between recommending this vs @iharyadi 's devices for repeating. His devices do indeed work great with Xiaomi. An antenna added to them would give as much or more value than the Tube router in my opinion (although I don't know how many devices are supported off hand). Iman's devices are also proven with HE and although there's technically no reason the Tube router wouldn't work well on HE, it's unproven. For sure anything other than a coordinator specifically to work with HA for using this driver needs to be compatible with HE and Xiaomi for me personally.

Having said all that, for HA repeating, that looks like a great option if you're in the US. If you're outside the US like I am, the cost and possible duty make that too close in cost to an Xbee to really benefit from a purchase of the router. The coordinator and people's results I'll be watching closely though. :wink:

1 Like
16

:joy: Put an Xbee in a round 3D printed container and close the lid. You'll never be able to tell.

2 Likes
17

I need it in a bigger box :joy:

image
image2268×4032 1.83 MB

1 Like
18

That looks like the same size (distance from antenna to micro USB. Just not round.

1 Like
19

Lol...yeah he replied to the wrong PM. The post was meant for me.

It works perfectly with my Aqara leak sensors.

Can't say that but I know someone that might be able to test the theory at some point down the line :wink:

I definitely will be watching. If I ever decide to move from my Conbee2 (which is unlikely any time soon...like I said, I'm very happy with it atm) that's likely my next move. Mainly because I'm interested in zigbee2mqtt...I like the concept of decoupling zigbee radio from a hub. Opens up so many options.

1 Like
20

Now accepting orders locally in the UK? :rofl:
Royski router

2 Likes