[RELEASE] Home Assistant Device Bridge (HADB)

[jshimota]

Even with two factor auth?

[SmartHomePrimer]

I don’t have the skill to audit the code. The login method to me gives perpetual access to my Amazon account. I prefer to error on the side of caution.

If this were an integration that could interface locally and just give me whatever the device is reporting, that’s a different story than handing over access to my Amazon account. I’m not comfortable with that.

[raidflex]

@ritchierich

This can be automated in Rule Machine via the Run Custom Action:

• Set the "Select capability of action device" to Actuator and then select the Home Assistant Device Bridge device
• Select the callService command
• You will then need to set 3 String type parameters and the order is important based on the order of the command within the HADB parent device (see screenshot above)

Once set within a Rule action you can then invoke this automatically and the mode will be set to whatever value you set within the third string parameter.

So I attempted to setup a rule with the "callService" command but receive an error and the T-stat does not change the mode. I can change it HA fine though.

callService Command:

select.basement_current_mode', 'select_option', 'option:home

Error:

groovy.lang.MissingMethodException: No signature of method: user_driver_ymerj_HomeAssistant_Hub_Parent_2971.callService() is applicable for argument types: (java.lang.String) values: [select.Basement_current_mode', 'select_option', 'option:home] Possible solutions: callService(java.lang.Object, java.lang.Object), callService(java.lang.Object, java.lang.Object, java.lang.Object) on line 6424 (method callService)

[ritchierich]

@raidflex

callService Command

Are you passing a single parameter or 3? You need to pass 3 in this order:

Edit: I just tested this and it worked with no errors.

[raidflex]

@ritchierich

Are you passing a single parameter or 3? You need to pass 3 in this order:

So I would need to add 3 parameters? instead of just a single line?

[ritchierich]

Correct. Original instructions mention that as well.

@ritchierich

You will then need to set 3 String type parameters and the order is important based on the order of the command within the HADB parent device (see screenshot above)

Whenever you call a custom command via RM you have to mimic the inputs for the command you see on the device page. Order is important as well - mention this because come device commands will have say a string first, then a number, and then a string so you have to set your rule action accordingly.

But with Run Command it is 3 string parameters.

[raidflex]

@ritchierich

Whenever you call a custom command via RM you have to mimic the inputs for the command you see on the device page. Order is important as well - mention this because come device commands will have say a string first, then a number, and then a string so you have to set your rule action accordingly.

But with Run Command it is 3 string parameters.

Its working now with the 3 parameters. Thanks.

[ymerj]

FYI: The latest version of HADB support select entities directly without having to rely on the call service feature. Furthermore, it will allow to report back the current option to Hubitat.

[raidflex]

@ymerj

FYI: The latest version of HADB support select entities directly without having to rely on the call service feature. Furthermore, it will allow to report back the current option to Hubitat.

Nice, even better!

[mluck]

Do I understand correctly that HADB support of thermostat devices does not include the humidity setpoint entity? If so, is it straightforward to add it? I can see and manage the entity from within the corresponding HA thermostat device without issue.

I’m trying to get more aggressive about managing humidity in our home and would love to bring that entity across to drive automations.

[ymerj]

I messaged you with something to try.

[s1godfrey]

I also have a binary sensor created in ESPHome that is for a physical wall switch. It shows up on HADB but will only create device in HE as "Generic Component Unknown Sensor".

There is no device_class: contact; However I tried 'connectivity' and it still is Unknown.

For Webcore automation I have it's important to know the state of the Wall Switch on/off.

Update: the only 'current' way I have got it to be seen is:

binary_sensor:
  - platform: gpio
    name: Switch
    pin: GPIO04
    id: physical_switch
    **device_class: motion**
    filters:
      - invert:
    on_press:
      then:
        - switch.toggle:
            id: fan
    on_release:
      then:
        - switch.toggle:
            id: fan

Which logically works but it is not very good organizationally or functionally.

[ymerj]

Version 2.14:

• Add support for humidity control in climate entity. (thanks to @mluck testing)

[ymerj]

I'm not sure what you are asking.

You have a sensor in HA you want for HE to see as a switch?

[s1godfrey]

I suppose that would be better than having to import it into HE from HA as a motion device.

I know it's just a binary sensor, so what diff does it make so long as it reports true/false. Well, it just seems that with all the wonderful things the HADB is offering, bringing in ESPHome binary sensors should be a baseline feature.

And using a binary sensor is a pretty common method to determine the state of a hard wired wall switch in a esp based device, aka Martin Jerry switches...

[ymerj]

I fail to understand what you find not suitable.

The unknown binary sensors are reporting a state of either ON or OFF. Can't a Webcore automation use that as is?

[s1godfrey]

lol... no, the binary sensor with no device_class assigned will not load into HE via HADB and assigns a driver as "Generic Component Unknown Sensor".

It does not respond to changes when the devices output changes true/false. Why else would I be posting all these messages..

Forgive me if it wasn't clear.

I'm sorry I don't have it set that way anymore, I needed it to work, so set it to device_class: motion.

But before it would be like a dummy device and would never respond from the HA which is via ESPHome.

[vitaliy_kh]

I am using bunch of Virtual Switches created in HA and passed to HE via HADB. The communication is bidirectional. Maybe this can help you.

[ymerj]

@s1godfrey

It shows up on HADB but will only create device in HE as "Generic Component Unknown Sensor".

@s1godfrey

lol... no, the binary sensor with no device_class assigned will not load into HE via HADB and assigns a driver as "Generic Component Unknown Sensor".

These statements are confusing and worth investigating of their meaning.

I'm always open to improve HADB. I would like to help you with your perceive problem with HADB but it would require some envolvement on your part in terms of little time and logs provision.

[tray_e]

@ymerj

Just tried to update to the latest version of the app. Not sure how to handle this (Do I need to turn off or pause the devices??)
Error Occurred During Installation

An error occurred while installing the package: Failed to upgrade driver https://raw.githubusercontent.com/ymerj/HE-HA-control/main/HADBgenericComponentThermostat.groovy. Please notify the package developer.. Be sure the package is not in use with devices.