The easy way is to use this integration that allows you to share devices from Hubitat to HA via the Maker API. Then you create the virtual switch on Hubitat and expose it to HA.
(I installed it via HACS)
(HADB and the above integration each do one direction of device sharing -- just make sure you don't re-share devices back to the originating platform via the other integration. Doing so would be ... bad)
I was working recently on a limited media player support. I put it asside because there was too many discrepancies between HA and HE on top of countless disparities in the way different brands are implemented.
But if it is only to switch on or off, it might work for you.
Let me know if you want to try it?
I totally get 'media player' attributes could be a very thorny patch given all the various device types and features out there. For my personal needs, I just need triggers when my receiver, LG TV or AppleTV changes power state.
I did use the Github HA-HE integration that @jlv mentioned and got it working in HA. I already had a virtual 'state' switch in HE from Homekit usage, so that's now exposed to HA and simple automations trigger the on/off state of the virtual state switch.
If your project would capture power state for a Denon receiver, LG TV, and AppleTV, then I could take it for a spin and see how it works.
Some oddities: some device do not report back their state through the brige. Command are succesfull but no state change might be reported.
Here are the links:
Driver: https://raw.githubusercontent.com/ymerj/HE-HA-control/ymerj-patch-MP/HA%20parent.groovy
I have a question about an entity in HA that's appearing as a motion sensor in HE. I have the Ring integration in HA, and the 'button' on the doorbell is: binary_sensor.front_door_ding
However, this 'binary sensor' is coming over as motion, which is confusing in HA because Ring also has a separate motion sensor as well. Is there another type of HE device that would be more appropriate/less confusing? I tried to use a 'virtual switch' that has an auto-off feature, but it wasn't compatible.
As per instructions:
The built in Hubitat driver, while too limited overall, does do power fine. Also, there is a Denon Homebridge plugin (homebridge-denon-tv) that works too
Ya tried the HE Denon plugin, and it was trash. Would work for a few days, then die. Asked in the forums for that driver, and due to telnet issues and Denon, they acknowledged it does have issues. I currently have Denon connected through to HB, but then I need an Apple Home automation to flip a HE virtual switch. Apple Home automations can be quite unreliable, so my goal was to use HA to set HE state information and remove Apple Home/HB from the equation.
I've used this one in the past. It's got more features. Not sure if it has similar performance issues to the built in driver. The guy who wrote it is no longer a Hubitat user, so consider it unmaintained.
Hi there,
Just a quick questions regarding HADB. Has anyone set up Hubitat and HA in a bi-directional method? I.e using HADB to populate Home Assistant devices to Hubitat, and using the Home Assistant integration into Hubitat to feed Hubitat devices into Home Assistant.
The reason why I'm asking is because HA supports bluetooth devices, which I would like to utilize in Hubitat (easier to work with Rules for automations), but expose Hubitat to Home Assistant for dashboards.
I do this, for very specific reasons. The majority of devices I have on HA work with HA device bridge and do not require an HE to HA integration. However, some do not work completely, and so I share Hubitat virtual switches to HA, and then use HA automation to trigger the Hubitat virtual switch when HA device triggers.
[NOTE]
You can also do this with HA Toggle Helpers and HADB. Sometimes that's easier, depending on what you're trying to accomplish.
It works almost the same with the automation you create on HA, but Helpers are not devices, so in the Action on HA, you have to select Helpers > Input boolean
Then you have to select Input boolean: Turn off or Input boolean: Turn on, and because it's not a device, you instead select the HA entity.
I do as I mentioned above (but I only really do so to get some HE devices to appear in an HA dashboard):
Thank you! I figured this is the way - just wanted to make sure there's no other "hiccups" involved
This is how I'm doing it also with Apple TV and homepod state changes flipping switches to initiate routines.
Hey
So I just added a new smart blind to HA, I managed to discover it in the HADB app and tick the box to include it, all good.
But when I click 'Discover and select devices' it takes FOREVER - like 2-3 mins. Is this normal? I ask because occasionally it only takes 2-3 seconds which seems more reasonable.
I’ve never seen this not be immediate. It doesn’t take any longer than a regular webpage load. I have HA running on an I7 6700 with 16GB ram and 500GB ssd running Ubuntu and on ethernet, so it’s not exactly stressed.
My HA is also running on a very high spec NAS with 32GB ram and SSDs etc etc. I've not actually looked at the NAS CPU load when I click the button. Although I have seen Hubitat give the 'Hub load is elevated' alert whilst it is waiting for/processing the devices in discovery.
You might want to look at your logs on Hubitat. I don't use HA for very much, 5 devices on this instance, 4 tp link outlets and one Hue light:
The average processing time is not far from each other.
Notice that the default HA config is dumping on the event stream sun data every 4 minutes as well as both weather forecast and local conditions quite regularely. HADB has to process everything that comes through, whether you selected it or not
Note: These can be disabled in your HA configuration.
Download the Hubitat app
