- makes a new item in a list. Seems like you are overwriting the cover: items couple of times.
Have a closer look at KNX - Home Assistant
You did it right in light:
Also consider configuring travelling_time_down and _up for covers
This is the case when you delete (or invalidate) configuration of an entity. It leaves an orphaned entity in the entity_registry. You should be able to delete it from UI after a restart - or it works again after you fixed your configuration.
Iâve been successful in pulling 95% of my KNX lights/Vents/Covers into HA. HVAC is an uglier problem.
For my first pass I used a program off Github to extract addresses from my KNXProj file.
It worked with a few problems and I have all my lights etc working in HA.
So I asked someone with access to ETS to run an âofficial exportâ . I still have the same problems and donât know how to fix these problems and there is an inconsistency between the outputs from the GitHub and ETS that I cannot reconcile.
Issues are:
HVAC - HVAC is Mitsubishi City that is connected to to AMX/KNX set up. I will need to replace the existing MN converter that uses RS-232 with Coolmasternet to connect with units and let HA control. The other side of the equation is to continue to use the KNX wall panels in each room to turn HVAC on/off and see temperature and set point. The AMS controller connect to these KNX wall panels uses KNX address - but there is only one KNX address (see below) listed in the ETS output. How do I control Setpoint and temperature that are also visible on wall switch?
Dimmers - there is only 1 KNX address. From the KNX wall switch I can do a long push to dim the lights, from HA I can only turn on and off.
Covers - Similar problem - there is only 1 KNX address. from my old AMX or wall controllers I can stop and have short address. In HA I connect up to one address and have only up/down âmove long addressâ
Lights all work fine. They also have just one address and no state address. Nevertheless Lovelace shows state and allows me to turn on/off.
Problem #2
Reconcile output format:
Example 1:
Output from Github tool (and this address works in HA):
1/0/1 Basement Guest Spots
Output from ETS
1 New Main Group
1/1 Basement Guest spots. Length 1 bit
Why is the â0â left out of the ETS Export?
Example 2 (Bigger Issue)
Output from Github tool
10/1/17 Office HVAC (This turns the red indicator light on and off on the KNX wall panel. So the address works)
ETS seems to be configured to use 2-level GA format. The script you used uses 3-level.
Both should work from with the knx Integration.
there has to be more GAs for temperatures etc. one GA can only have one data type. Binary (on/off) canât Transport temperature/brightness/etc information.
see 1; HA needs brightness in % to work here. DPT3 dimming is possible from a blueprint you can find here in the forum.
not sure what you mean
not having a state address is fine for most cases. If a read-flag is set on one CO in the GA you can just use the same address for âaddressâ and âstate_addressâ. If you canât check from ETS, just try it, restart HA and see if there are errors in the logs. Or try to read the GA value from ETS Groupmonitor - Demo license is sufficient for this.
Thanks to this cookbook, I was able to integrate my KNX devices into Home Assistant flawlessly.
My KNX integration was working fine. When I update Home Assistant to the 2021.4 release, it no longer works. I have therefore undone the update for now and imported the previous snapshot.
In the release notes for 2021.4 and 2021.5 I find the following notes:
2021.4: The config_file YAML option for KNX is deprecated, please remove it from your YAML configuration if you have it configured.
*2021.5* The config_file YAML option for KNX was deprecated before and has now been removed.
OK, thanks for the explanation. I think I already use the HA KNX config schema. So my error must be somewhere else. I will then install the update 2021.05 and look for the error somewhere else.
This is what an excerpt from my knx.yaml looks like:
Seems that some of the addresses for the HVAC were not included in the ETS Report. However I have found other addresses in the AMX code and other addresses from the KNX Log.
From AMX Code
10/1/17 - Set Temp
9/2/17 - Set Heat/cool
9/1/17 - on/off
From KNX Log on HA. From pushing button on the KNX wall panel the log listed these addresses.
10/4/4 Turn on LED HVAC unit on/off
10/4/7 - Turn off LED HVAC unit on/off
10/4/18 -Raise Temperature
10/0/17 - Lower Temperature
10/4/13 - Also appeared in Log
10/4/16 Also Appeared in log
I can switch the HVAC on/off on the the KNX wall panel and move the temperature dial from Lovelace. However the Lovelace temp dial does not change the KNX wall panel and the only option is heat
Setting temperature, target temperature and setpoint shift to the same address will definitely fail.
The only modes you configured are âheatâ and âoffâ. operation_mode_address provides presets in HA.
Also setpoint_shift_address needs setpoint_shift_state_address to be set and the value has to be read from the bus to initialize.
See HA knx climate documentation for basic configuration help and Link to Logs â My Home Assistant for logs. There are usually error messages telling you why something was not working.
Hey !
In the next release some HA core changes to Lights are accounted for. But I donât have any colored lights so I canât test it on actual hardware.
does anybody know how to create the template sensor for a KNX weatherstation now that create_sensors is deprecated? I have no clue how to do thatâŠ
Thanks for any hint