Valve Domain In HomeKit

Feature Requests
1

Now that HomeAssistant supports a Valve domain, would it be possible to have valve types added to the HomeKit integration UI so they can be directly added (rather than manually add manually through configuration.yaml as a switch and changing its type)?

2

Don’t forget to vote for your own feature request @jvm!

There is already some support for valves already:

image

3

Duplicate:

They both should be closed, maybe, probably…

1 Like
4

Thank you! That worked and I was able to add as a valve.

So now my request is a bit modified - it would be to have this done via UI. But for now, I have it working.

1 Like
5

Hi,

Can you paste your config here? I’m still learning HA and I canton make it work. Having an example would help me.

Thanks

6

Your “valve” first needs to be a switch entity in Home Assistant.

Then you can add something like the following to your configuration.yaml:

homekit:
  - name: "HASS Bridge - YAML" 
    port: 21063
    filter:
      include_entities:
        - switch.whole_house_hot_water_plug
    entity_config:
      switch.whole_house_hot_water_plug:
        type: shower
2 Likes
7

Questions

  1. Can this be done through UI?
  2. It seems if I insert this line of code into confirmation.yank, I would filter out all the other HomeKit devices.
8

No, only YAML for now.

  • It seems if I insert this line of code into confirmation.yank, I would filter out all the other HomeKit devices.

If you don’t already have any HomeKit Bridges setup in your configuration.yaml, the code should not affect any other HomeKit Bridges (or Devices).

It will create an additional Bridge, separate to anything you have configured in the GUI. You will just need to change the entity names from switch.whole_house_hot_water_plug to match your own.