Help testing the new Home Assistant IHC integration
I have been working on new verion of the IHC integration for Home Assistant.
If you want to help test this you can install a “beta” version as a custom component in Home Assistant. You can get it here:
- Configflow. Allow you to setup the IHC controller using the UI.
- The controller will be represented as a device in HA, and identified by its serial number.
- Entities will get a unique id, allowing you to easier change name/icon. The unique id is a combination of the controller serial and the resource id
- Autosetup IHC products as devices in HA. To group related entities, and easier automation (Because the HA UI now have better support for automations on devices)
- Extra attribute to identify the IHC controller on an entity. (When you have multiple IHC controllers)
- Migrating old ihc manual config from configuration.yaml to new ihc_manual_setup.yaml file.
- Suggested area from IHC groups. You need to setup the IHC controller again. The initial config dialog will ask if you want to use suggested areas.
The most critical part is the IHC controller serial number. Devices and entities in HA needs a unique id, and I use the controller serial number (as advise in the HA documentation). I am not 100% sure this function is available on all IHC controller versions. I have IHC controller hardware version 6.1 and the new version 7.1, both of these have a serial number available. I assume version 6.2 will be no problem since it is in between. Controller version 6.0 could be a problem since it is older. The other “brands” of the IHC controller like “ELKO” may be different?
If you have a different controller or one of the ? – please help testing and report in the comments below – then I will update the list. If you find bugs you can report this in github
I have updated the HA IHC documentation here: IHC integration Notice the “migration” part if you have manually configured IHC entities.
Before you start testing – it is probably a good idea to make a backup of your IHC configuration. (But you do that regulary already of cause;-)
And a disclaimer/warning – this is a beta/preview version – I may make changes before the final version in Home Assistant. Also notice that entities added with a unique id will be stored in the HA entity registry, so if you go back these will show unavaialable entites, that you will have to delete yourself.
Hej
I made a setup using the Home Assistant UI and the auto setup just went fine.
When I tried to do a manual setup i’m getting this error:
Invalid IHC manual setup data: extra keys not allowed @ data[‘ihc’][0][‘012345678901’]
I have no idea what is going on.
Could you help please.
the /config/ihc_manual_setup.yaml file looks like this:
ihc:
– 012345678901:
– light:
– id: 17755
hilsen Lars
Remove the “-” before “light”. This was wrong in the documentation I have updated it now: IHC Integration
Hej Jens
Weird still getting the error.
looks like this now
ihc:
– 0123456789:
light:
– id: 17755
name: tablelight
Log details (ERROR)
Logger: custom_components.ihc
Source: custom_components/ihc/__init__.py:354
Integration: IHC controller (documentation)
Another bug i my documentation – it is updated now. It should be like this
ihc: - controller: xx0123 light: - id:123123(I made the change after making the documentation, so I forgot about it. My first controller had a serial number with just a few digits. The second one has a serial beginning with letters and then some digits. Having the serial number as key in yaml could probably cause problems – since I don’t know the format of the serial number on other controllers)
Hej Jens.
Så spiller det!
It’s working and now I can edit Entities.
Super work,
Thank you Jens 🙂
Hej Jens.
Jeg prøver at på liv i din beta version på HA, men kan ikke rigtigt få hul igennem. Jeg prøvede først en opgradering fra en fungerende konfiguration i configuration.yaml. Jeg kunne se at “ihc” blev flyttet til ihc_manual_setup.yaml, og nu med serienummer men uden brugernavn og password. Jeg slettede så opsætningssektionen i config.yaml, men du kender HA jo ikke længere url + bruger + password. Sikkert derfor der ikke er hul igennem.
Mit spørgsmål er så: Hvad skal der være af minimums konfigurationer i config.yaml og ihc_manual_setup.yaml? Hvormeget af det skal jeg selv sætte ind og hvad kommer automatisk?
Jeg finder heller andrig den IHC integrationskomponent du referer til og som skulle findes under configuration >> intefration >> + Add integration. Er det noget der kommer senere eller hvordan?
Hilsen
Kjeld
Du mangler at tilføje IHC integration gennem UI . Indstillinger|Integrationer – tryk på stor blå knap i nederste venstre hjørne “+ Tilføj integration”. Find “IHC” i listen -> herefter vises dialogen hvor du indtaster url, brugernavn og adgangskode
Jeg tænkte nok der var noget der manglede. IHC kommer dog ikke frem på listen. Kan jeg mangle at installere noget?
Kig i HA loggen og se om du hat nogen fejl der har med IHC integrationen at gøre. Har du selv kopieret til custom_components eller installeret via HACS. HVis du selv har kopieret så check at du har alle filer og “translations” subfolder
Hi Jens,
Nice work with the IHC V2 integration!
I have the LK IHC 6.2 controller and everything seems to work very well.
I have a 6.2 controller. But, I am new to HA. In what way is the betaversion “better” than the old one – what are you/we trying to achive here?
You can see what is new/changed in the list above in the post. The most important new thing is the config flow, esiacially for new users. A config flow allows you to configure the integration using UI. Otherwise you will have to manually edit the configuration.yaml file. (Home assistant do not allow new integrations to be without a config flow). The unique id for entities and devices also allows you to esier rename/change icon e.t.c from the HA UI.
Ok, i will give it a shot
virker fint med min 6.2 controller. Prøver at installere din viewer også 🙂
Hello Jens
I’m trying to bring your beta version to life in HA, but I have an error warning in the log that says:
Logger: homeassistant.loader
Source: loader.py:802
No ‘version’ key in the manifest file for custom integration ‘ihc’. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of ‘ihc’
I’m using HA version: core-2021.3.4
Can this be the reason why i have problems
This is just a warning – it has no impact on functionallity. What are your problems?
When i install it thru hacs everything looks good.
After restart of HA the logg says, unable to load IHC
I don’t get the ihc_manual_setup.yaml
The ihc: part is still in configuration.yaml
Look for other errors in the log – there should be something related to why IHC fails to load. The ihc section is not removed automatically from configuration.yaml, you must do this manually. If you have some manual ihc configuration you should run it once to have it converted to ihc_manual_setup.yaml. If you have errors in your configuration it could fail. You could try to validate your configuration before installing the new IHC integration. You can do it in configuration|Server control Server control
(Note you must have advanced mode enabled on your user)
Hej Jens
I jumped back to the snapshot created before i tried to install the new ihc.
This time everything worked perfect, so I don’t know what the problem was?
I always check my config files before i restart HA, so it was not the reason.
I have tested 5 different snapshots to see if i was able to reconstruct the problem, but all worked perfectly.
Do you have any idea, when new integration version would be merged to HA, i.e., from beta to ready? I would like to use it and the new HA IHC viewer. HA 2021.6 is also one step closer, when viewer will not load anymore.
You will be able to use it after 2012.6 – i have added the “version” to the viewer manifest and i will do that also for the ihc integration.
I will probably make a PR for the IHC integration within the next week, can’t say how long it will take to be included, last time it was more than a month.
Will this work with more than one controller? I have 2 controllers, but how do I get both controllers into the new beta version now that it is configured through the HA integration?
It works with more than one controller – you just add each controller in the HA integration. (and my IHCviewer for HA now also support more than one controller). Each controller is identified by its serial number. The integration will get the serial number when it connects to the controller.
“Not loaded”
Jeg har efterhånden prøvet et par gange med den nye integration og jeg kan ikke få det til at virke.
Efter at have fulgt instruktionen og installeret vha. HACS ender jeg blot med at jeg ser “IHC Controller” “(!) Not loaded” under integrations.
I loggen:
2021-05-30 13:29:05 WARNING (SyncWorker_6) [custom_components.ihc.migrate] Your old ihc configuration in configuration.yaml file has been copied to the file /config/ihc_manual_setup.yamlYou can now delete the ihc section in configuration.yaml. Restart Home Assistant and add the IHC controller through the UI. See https://www.home-assistant.io/integrations/ihc/ for more information
2021-05-30 13:29:07 ERROR (MainThread) [homeassistant.setup] Setup failed for ihc: Integration failed to initialize.
2021-05-30 13:29:08 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of ihcviewer. Setup failed for dependencies: ihc
2021-05-30 13:29:08 ERROR (MainThread) [homeassistant.setup] Setup failed for ihcviewer: Could not set up all dependencies.
Er der nogen krav om HTTPS? Er det et problem at IHC controlleren sidder på et andet netværk med firewall imellem?
Det virker fint med den gamle integration.
Du skal fjerne IHC sektionen fra din configuration.yaml fil, genstarte ha og tilføje ihc controlleren via indstillinger|integrationer i HA. Den opdaterede dokumentation er her ihc integration (Linket var forkert i readme – det var den orginale documentation)
Ok … jeg troede egentligt jeg blot kunne lade den gamle configuration stå sådan at det var nemt skifte tilbage.
Du kan udkommenterer med #
Der er er krav fra HA at nye integrationer ikke mere skal opsættes i configuration.yaml og have et “config flow” til opsætning via UI. Så jeg har fjernet det for at følge de retningslinjer.