IHC problem after update

Configuration
1

Will it in the future be possible again to have all the binary sensors in a seperate binary_sensors.yaml file instead direct under the configuration?
Before updating from 0.82.1 to 0.84.4 this was possible.

2

AFAIK it still is.

I’m running 0.84.6 and have a separate binary_sensors.yaml

Make sure you have the line

binary_sensor: !include binary_sensors.yaml

in your configuration.yaml file

3

I do have that line in my configuration.yaml and then this in the binary_sensors.yaml, but after updating from 0.82.1 to 0.83.x+0.84.x it does not work any longer.

  - platform: ihc
    binary_sensors:
      - id: 5156700
        name: IHC kitchen 1
      - id: 5156956
        name: IHC kitchen 2

I have also tried “binary_sensor:” instead “binary_sensors:” according to this issue but still no IHC shown in entities.

https://github.com/home-assistant/home-assistant/issues/19353

4

Did you find a solution to your problem? I have the same now when updating to 0.86.0. I also had issues with other naming conventions that has changed.

5

No I am still having all the IHC binary sensors placed in my configuration.yaml. Strange!
Yes every entity id with strange characters like æ ø å will now be replaced with other characters instead of just leaving them out.

6

I also had it defined in my configuration.yaml before I upgraded. Only difference is that I updated to 0.86 and binary swicthes are now all gone. Not only my IHC but also the HUE ones. The Hue ones are now directly working with the HUE integration but I’m missing all my IHC wall switches(The battery powered ones). Any clue? I checked for weird spelling as addressed.

7

My switches are all the battery powered ones and they Work after defining them in the configuration.yaml.

My IHC part in the config,yaml looks like this:

ihc:
   url: http://192.168.1.40
   username: xxx
   password: xxx
   auto_setup: False
   info: false
   binary_sensor:
     - id: 5156700
       name: IHC kitchen upper left
8

Thanks, same here. But not working :(. The good thing is that It seems like I’m not the only one having this issue!!

9

For your info I found the reason; The Binary_sensor IHC feature is somehow not supported by the Lovelace UI; Weird yes but if I change to the standard UI it works and is req.
I tried going back to lovelace UI and the issue can be reproduced.

10

Thanks for the feedback. Lets hope it Will be corrected.
How Can I swap between standard UI and lovelace to test myself?

11

You can find it in the left pane; development information(Button=(!))

In the middle of the page you will find a link saying “go to Lovelace UI” or “go to states UI”

12

found it… thanks :slight_smile:

13

Super. Pure coincidence that I tried it out. Must say that its a nice piece of software but my good it really fuck up things when I try to update; I’m not that kind of guy that that reads manuals or release notes😉.

14

Yes it is really some software but most updates are also followed by some issues.

15

How to get the ihc smart plug to work in HA?
configurator yaml file
ihc:
url: http://192.168.1.211:8123
username: xxxxx
password: xxxxx
info: true
switch:
- id: b4430dc56581
name: Bed Fan
position: Master Bedroom
The error I receive is:
Invalid config for [ihc]: expected int for dictionary value @ data[‘ihc’][0][‘switch’][0][‘id’]. Got None. (See /config/configuration.yaml, line 46). Please check the docs at https://home-assistant.io/components/ihc/

16

The hex number of the switch id in the .XML file has to be converted to integer.

1 Like