[RELEASE] Home Assistant Device Bridge (HADB)

[SmartHomePrimer]

Not sure it's what you thought it was.

Seems like a virtual button, such as we already have here in Hubitat. I might be wrong, but it doesn't sound like this is going to create entities when you add a button, but perhaps you could create an automation in HA for real button devices that would press the new button entity and that would give you a button press in Hubitat. Would avoid the need to install the Hubitat Integration for Home Assistant in order to get the virtual switch from Hubitat to do the same thing.

I'm not home right now and my remote access to HA is down, so I'll have to test it out later.

[bradford.clarke]

I run HA in docker. but the new image won't pull down when I tell Portainer to rebuild it.

Tried several times this evening.

[doogles]

Haven't played with this too much, yet, but I don't immediately see anything different happening with buttons. In Home Assistant, I still only see the _battery entities and not the buttons themselves.

[ymerj]

It looks like the button entity can only be obtain through integration that support it. For the moment only a handfull do. Supposedly more are comming.

[BrenenP]

I got Home Assistant for Christmas (an ODROID) and I'm trying to connect integrations that HA can do that HE can't, like August, Xbox, etc., but bring them into HE using this release.

So far I've got August working. I was wondering if there would be any support for "remote.xbox_one_remote" entity or is this better suited for a virtual switch?

[dylan.c]

FIrst off, I've been aware of (and intrigued by) this effort since @ymerj first posted his prototype driver almost a year ago. Thanks to @SmartHomePrimer for reminding me of it the other day and motivating me to give it a go over the holiday. All I can say is WOW! So much easier than the MQTT broker/client method that I am using for my Ecobee thermostat.

I know that this app/driver doesn't support climate devices (the actual thermostat), but the Ecobee Smart Sensors populate into HA as normal sensors. I'm trying to use this app to bring my Smart Sensors (motion & temp) into HE. The child devices are successfully created, and the motion sensor device (sensor_binary type) is showing active or inactive in the HE device page. However, the log entries for motion simply say 2021-12-25 07:25:25.303 pm [info] EcobeeSensor3 is updated. For a normal motion sensor, it says the actual state of active/inactive rather than just "updated." In use, this means that I'm unable to use the state change to active as a trigger. A test rule using this trigger never runs. Any ideas on what I can do to fix this? I suppose I could create a virtual device and write a rule to mirror the state of the actual device, but that seems like too much work.

[aaiyar]

@dylan.c

I know that this app/driver doesn't support climate devices

It does.

[RELEASE] Home Assistant Device Bridge (HADB)

Hi, Sure. My code base is 0.1.29. Please see below:

Summary

/* Home Assistant to Hubitat Integration Description: Allow control of HA devices. Required Information: Home Asisstant IP and Port number Home Assistant long term Access Token Features List: Licensing: Copyright 2021 Yves Mercier. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at: <a href="…

Here's a screenshot of a PM that I had sent someone recently after testing whether I could import an ecobee paired with HomeKit Controller to Hubitat via Home Assistant Device Bridge:

[dylan.c]

@aaiyar

It does

Is that a fork of the "original" app?

[aaiyar]

I think it’s a fork of the driver and the changes were never sent as a pull request to @ymerj .

[dylan.c]

@tomw @ogiewon Hopefully the fact that the two of you "liked" @aaiyar's post means you're already on top of this, but I wanted to ask just to be sure. Any chance someone could review the code posted by @gabriel_kpk and merge the parts for climate devices into the main release?

And any info on my motion sensor issue would be greatly appreciated as well.

[tomw]

@dylan.c

Any chance someone could review the code posted by @gabriel_kpk and merge the parts for climate devices into the main release?

Is this the code in question, @aaiyar and @dylan.c ?

[RELEASE] Home Assistant Device Bridge (HADB)

Hi, Sure. My code base is 0.1.29. Please see below:

Summary

/* Home Assistant to Hubitat Integration Description: Allow control of HA devices. Required Information: Home Asisstant IP and Port number Home Assistant long term Access Token Features List: Licensing: Copyright 2021 Yves Mercier. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at: <a href="…

I would be happy to review, but I would need a GitHub pull request as a starting point.

[tomw]

@dylan.c

And any info on my motion sensor issue would be greatly appreciated as well

Can you point us to the details on this issue?

[dylan.c]

Link to my post explaining the motion sensor issue...

[RELEASE] Home Assistant Device Bridge (HADB)

FIrst off, I've been aware of (and intrigued by) this effort since @ymerj first posted his prototype driver almost a year ago. Thanks to @SmartHomePrimer for reminding me of it the other day and motivating me to give it a go over the holiday. All I can say is WOW! So much easier than the MQTT broker/client method that I am using for my Ecobee thermostat. I know that this app/driver doesn't support climate devices (the actual thermostat), but the Ecobee Smart Sensors populate into HA as normal…

@tomw

Is this the code in question

It is. I'll see what I can do re: the pull request. I'm not clear what exactly was added to the driver and I'll need to create a github account,I suspect. Hopefully sometime today.

[tomw]

I think it would be easier for @gabriel_kpk if they wouldn't mind doing the PR. The main issues are formatting between the forum and the original code, plus a merging of the current version of the code back into the forked version. Both are easier if you have the original modified version from the Hubitat editor to start with.

[tomw]

@dylan.c

Link to my post explaining the motion sensor issue...

Ah, I missed that detail in your post.

Will you please turn on logging on the parent device and send a few logs with presence changing in HA from this device? This is the line I'm hoping to see on the Hubitat side:

parse(): description =

[dylan.c]

@tomw

easier if you have the original modified version from the Hubitat editor

I was able to get a copy of the modified driver from @aaiyar. You should see a pull request in github. I did my best to eliminate trivial differences between the current version and the modified one, but I'm no programmer. Let me know if there is anything else I can do.

I'll also get more info on the motion devices ASAP.

[dylan.c]

@tomw

send a few logs

Is this enough to go on? dev:742 is the parent device, and 744 is the child motion sensor.

dev:744		2021-12-26 02:21:48.421 pm info		EcobeeSensor2 is updated
dev:742		2021-12-26 02:21:48.405 pm debug	parse: domain: binary_sensor, device_class: motion, entity: binary_sensor.ecobeesensor2, newVals: [on], friendly: EcobeeSensor2
dev:742		2021-12-26 02:21:48.403 pm debug	parse(): description = {"id": 1, "type": "event", "event": {"event_type": "state_changed", "data": {"entity_id": "binary_sensor.ecobeesensor2", "old_state": {"entity_id": "binary_sensor.ecobeesensor2", "state": "off", "attributes": {"friendly_name": "EcobeeSensor2", "device_class": "motion"}, "last_changed": "2021-12-26T19:57:50.197543+00:00", "last_updated": "2021-12-26T19:57:50.197543+00:00", "context": {"id": "2a872b01f8c1131baf85b2254ed57d7d", "parent_id": null, "user_id": null}}, "new_state": {"entity_id": "binary_sensor.ecobeesensor2", "state": "on", "attributes": {"friendly_name": "EcobeeSensor2", "device_class": "motion"}, "last_changed": "2021-12-26T20:21:43.860745+00:00", "last_updated": "2021-12-26T20:21:43.860745+00:00", "context": {"id": "096b1e0d329b9f49ca240b86500380ad", "parent_id": null, "user_id": null}}}, "origin": "LOCAL", "time_fired": "2021-12-26T20:21:43.860745+00:00", "context": {"id": "096b1e0d329b9f49ca240b86500380ad", "parent_id": null, "user_id": null}}}

[ymerj]

About the PR: The differences in formatting between this forum and github introduces changes in the code where in fact there is none, making it practicaly impossible to review properly. As @tomw said, it would be better if @gabriel_kpk make a new PR integrating the changes done to the driver since version 1.29 (we are at 1.36).

[tomw]

@dylan.c

Is this enough to go on?

Everything looks like it's working correctly, but I have a hunch on what may be going wrong. I'll message you with some modified code to try.

[dylan.c]

@ymerj

make a new PR

I'll see if I can manage this...