[RELEASE] Home Assistant Device Bridge (HADB)

We're getting a little off-topic now... but I'll try to answer...

When you say 'move over to HA', what exactly do you mean? Are you planning on removing these devices from Hubitat completely - and then adding them only to Home Assistant? Or, and you wondering if they can also be mirrored from HE to HA using the other integration that I linked above?

In general, the Custom Component: Hubitat integration will allow pretty much any HE devices to be mirrored over to HA as long as they follow normal standard Hubitat Capabilities, that also have corresponding counterparts over in the HA world. Not all functionality may be available for the device, unless the device is paired directly to HA, though. For example, I am fairly confident that a door lock mirrored from HE to HA, would be able to be locked and unlocked. However, changing door lock codes may not be possible unless the lock is paired directly to HA (and even then, I don't know for sure if changing lock codes is supported!)

That would be a good question for me to think about. Basically, I wanted to have the full functionally of a door lock including changing the pin numbers and it looking like a door on Homekit rather than a switch. Same with garage door opener which I would like it look like a garage door than a switch.

To do that, I would have to use Homebridge and leave door lock and also garage door functionally on it which I am doing right now. I moved over all other devices to HE Homekit app.

I was chatting in Discord about HA features etc and someone mentioned that HA supported Homekit internally and they do have a kick ■■■ dashboard too so I was thinking maybe I could eliminate the Homebridge off my Raspberry PI and install HA on it then either somehow access the lock and garage door on HE and use the internal Homekit off HA since I am sure it will be supported because I doubt they are trying to get "Apple certified" and will function as a door lock and garage door instead of a virtual switch.

I could be wrong about all this but it what my understanding how HA works and I was in discord chat the other day where someone mentioned about it. I just don't want to install another Raspberry PI for it dashboard and camera functionally instead I would like to use the one I have running Homebridge and swap it out with HA OS.

Get what I am thinking about doing?

Sure, I understand. For me, I decided a long time ago that when I buy devices, I try to buy ones that are best in class, and that natively support Apple HomeKit, Google Home, Amazon Alexa, Hubitat, Home Assistant, Logitech Harmony Hub, etc... In this way, I am hedging my investment by knowing that if my home automation platform of choice today goes under, or pivots drastically (e.g. SmartThings), these devices will still work with other systems.

So, for me, that means using a Philips Hue bridge and Hue bulbs for all table/floor lamps in the house. I use Lutron Caseta for all wall switches, dimmers, fan controllers, and pico remotes. I use Zigbee devices tied to Hubitat for sensors, like door/window contact sensors, leak sensors, and motion sensors. Hubitat is the glue that ties all of this together and provides speedy, easy to configure automations. I have a Home Assistant Yellow running for 'fun' and to handle a few devices that are not supported on Hubitat, like my new Aqara FP2 occupancy sensor. I use HADB to bring that device back into Hubitat from HA to allow its 'presence' sensors to be used in my home automations. I also have HomeBridge (for HE devices) running on my dedicated home server, along with InfluxDB, Grafana, and Plex Media Server. For me, I gave up the notion that less hubs is better a long time ago. I enjoy the hobby and have decided that using the best in class hubs and bridges results in an extremely flexible and robust system.

Good luck with your setup! I hope you find a solution that achieves your goals.

Good luck

6 Likes

I understand where you're at.

I did have thought about just getting one of those bigger processor board that could handle both a Homebridge and HA in a docker container like a mini PC form or something.

One thing, it would mean I will be paying a little more on electric bill if I get something that require more wattage over Pi boards .. My life will always be on a budget.

I currently only share 7 HA devices via HADB. However, two of the devices generated a lot of traffic because of the nature of the devices (The current produced by solar panels and the load on the solar inverter. These values change constantly.) Although this was not an issue with the C7 and things were running fine for months, for some or other reason, the exact setup caused a serious overload on the C8. (As I've mentioned, the Z-wave network and devices were e.g. a mess as a result, with devices often being unresponsive).
The regular overload of the hub (which was even worse after a reboot) was the reason why I disabled HADB before a reboot, but as discussed earlier, this unknowingly made things worse.
I have also managed to calm the traffic generated by the two offending devices by creating virtual devices on the HA side, which update less frequently. I now share these virtual devices with HE instead of the actual devices. I have a few webCoRE pistons that use these devices, and because the virtual devices update less often, the pistons fire less often, further reducing the load on the hub. But even with these measures, I still get overload errors after a startup.
Once again, thank you @Ken_Fraleigh and @tomw for your input.

1 Like

I don’t know how much that will help since all of the HA info will still be sent to the eventstream shared to HE and the resources needed to filter it out will still be provided by HE. I would put the HADB back on the C-7 and use hub mesh to bring the devices over to your C-8 if you need to reduce the load further.

1 Like

I was considering that, but does hubmesh use less resources than an app like HADB? (My setup is getting out of control because af all the hubs. I still have a Smartthings hub in the mix as well. I use the Smartthings hub to integrate my alarm system via an Envisalink card. And to control Aeotec garage door controllers for which I couldn't find HE drivers .)

I’ve been using hub mesh since its launch and have not seen any problems. I currently have 3 HE hubs using it. I would just advise that you turn off the radios on the older hub if you’re not using them to avoid any interference with your new hub.

1 Like

As far as the app is concerned, this will NOT reduce the traffic in any way. It will in fact increase it slightly. It may shorten the processing time in the driver but only from a few milliseconds.

2 Likes

Not sure why I am getting the error below:
dev:17512023-05-22 03:19:25.509 PMerrorParsing error: com.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Generic Component TimeStamp Sensor' in namespace 'community' not found
Please advise, thanks.

You get this error because the TimeStamp child device is not installed on your system.

Some child driver types are optional components in the HPM listing, so you can use the Modify option in HPM to add any that you need.

If you installed manually, you need to install any of the needed child devices manually from the repo.

3 Likes

Great, thanks!
I have added a few more components (okay 5 remaining components!).

@ymerj

Here is the debug log entry for my IKEA Vindstryka sensor.

It is paired to my Dirigera hub, which is fed through the Home Assistant HomeKit Controller.

The Temperature and Humidty values are being successfully passed through with this setup.

Here's the Debug log for the PM2.5 sensor;

dev:560 2023-05-27 08:05:10.920 PM debug parse: domain: sensor, device_class: pm25, entity: sensor.sensor_3_pm2_5_density, newVals: [2], friendly: Air Sensor PM2.5 Density
dev:560 2023-05-27 08:05:10.911 PM debug parse(): description = {"id":1,"type":"event","event":{"event_type":"state_changed","data":{"entity_id":"sensor.sensor_3_pm2_5_density","old_state":{"entity_id":"sensor.sensor_3_pm2_5_density","state":"1","attributes":{"state_class":"measurement","unit_of_measurement":"µg/m³","device_class":"pm25","friendly_name":"Air Sensor PM2.5 Density"},"last_changed":"2023-05-28T00:04:51.412225+00:00","last_updated":"2023-05-28T00:04:51.412225+00:00","context":{"id":"01H1FTR3JM1XJ08STHM8K7K1CB","parent_id":null,"user_id":null}},"new_state":{"entity_id":"sensor.sensor_3_pm2_5_density","state":"2","attributes":{"state_class":"measurement","unit_of_measurement":"µg/m³","device_class":"pm25","friendly_name":"Air Sensor PM2.5 Density"},"last_changed":"2023-05-28T00:05:06.347401+00:00","last_updated":"2023-05-28T00:05:06.347401+00:00","context":{"id":"01H1FTRJ5BHZ4AVA3HEVESEKMJ","parent_id":null,"user_id":null}}},"origin":"LOCAL","time_fired":"2023-05-28T00:05:06.347401+00:00","context":{"id":"01H1FTRJ5BHZ4AVA3HEVESEKMJ","parent_id":null,"user_id":null}}}

Not sure if that's enough to compare against the Z2M data to see what's different.
Let me know if you need anything else.

The PM2.5 is ok. It is the TVOC I would like to see.

On my setup, even though PM2.5 is showing up in the log, it's not resulting in a device being created within HADB for it.

TVOC = Air Quality? That's not showing in the log.

This is all that's coming into HA for me.

PM2.5 will be taken care of in the upcoming update. TVOC is air quality in your case. Mine reports every 2 minutes. Maybe yours is on another schedule. As a sensor it should produce an event at least when the value changes.

Note: Air Quality entity has been deprecated 2 years ago in HA.

I turned debugging back on and forced and air quality change, but nothing is showing up in the logs.

Air Quality changes are registering in the Ikea Smart Home App.

Odd that Air Quality was deprecated, yet the HA HomeKit controller app registered it with that name.

Sadly, if nothing is coming through the bridge, we cannot do anything about it. It works fine with Z2M. Using @kkossev driver to integrate it directly into Hubitat would probably be a cleaner solution.

I seem to be having issues with certain sensors passing through on my Everything Presence One, and not others.

The ones that include binary are not created in Hubitat. Also the true device name doesn't come across either.

I'll play with it more later and turn on debugging.

Seems most people sync devices the other direction and just do all the automation work in HASS. I haven't really played with that, but I really like WebCore. Can't make up my mind.

Edit: Stand slightly corrected. After about 5-10 minutes and various refreshes, one of the binary sensors came through.

image

Device are only created when there is a change occuring. Try triggering your mmWave and occupancy sensor.