Closed guerda closed 1 year ago
It seems to be a different reason. As soon as I reload the addon, some messages appear in the logs.
It seems that the newest home Assistant version is not allowing those IDs anymore
Logger: homeassistant.components.binary_sensor
Source: helpers/entity_platform.py:610
Integration: Binärsensor (documentation, issues)
First occurred: 30. September 2023 um 14:25:28 (300 occurrences)
Last logged: 21:02:35
Platform freeathome does not generate unique IDs. ID ABB700D18BBF/ch0003 already exists - ignoring binary_sensor.licht_xxxx1
Platform freeathome does not generate unique IDs. ID ABB700D27923/ch0003 already exists - ignoring binary_sensor.licht_xxxx2
Platform freeathome does not generate unique IDs. ID ABB700D27939/ch0000 already exists - ignoring binary_sensor.licht_xxxx3
Platform freeathome does not generate unique IDs. ID ABB700D39087/ch0000 already exists - ignoring binary_sensor.licht_xxxx4
Platform freeathome does not generate unique IDs. ID ABB700D3908B/ch0000 already exists - ignoring binary_sensor.licht_xxxx5
I am on homeassistant 2023.9.3 and SysAP 3.2.2 with no issues. So this should have something to do with version 2023.10. I do not dare to upgrade yet.
It's safe to upgrade fah as long as you have the newest addon installed.
I forgot to upgrade the addon via HACS. Since I installed the newest upgrade, I have no problem anymore
@guerda I have not installed HACS. So you think I am safe to upgrade homeassistant to 2023.10 ?
If you have a manual installation of the addon, I recommend updating it too. It should be safe to upgrade the addon (manual or via HACS) and also update HA.
Since I updated the free at home firmware to version 3.2.2. I cannot control devices anymore and the communication fails with an error in home Assistant.
Here is one example for an error in the log