ekutner
after updating to 1.3.2 I dont receive events
Describe the bug
After updating to version 1.3.2, I am experiencing an issue with my dishwasher integration. Somehow, I now have the same device registered twice in Home Assistant. After the update, the entities reverted to the old dishwasher device, which I no longer use.
As a result, some functionality no longer works, including receiving events from the device.
I downgraded the integration back to version 1.3.1, after which everything worked normally again, including events. I deleted all the entities in the old dishwasher (vaatwasser oud).
How can I solve this, so everything is working well in version 1.3.2?
Version of the custom_component
1.3.2
Configuration
I have not changed the default configuration for this device. the same device is added twice in home_connect_alt. I don't know why, maybe because i've changed soms entity-id's in the old device? Because of this, maybe the home_connect_alt intergration added a new device or something?
Debug log
The error appears in the log as follows:
Logger: custom_components.home_connect_alt Source: custom_components/home_connect_alt/init.py:395 Integration: Home Connect Alt (documentation, issues) First occurred: 21:43:21 (2 occurrences) Last logged: 21:43:21
No device found for appliance 011090388878000094, cannot publish event BSH.Common.Event.ProgramAborted = BSH.Common.EnumType.EventPresentState.Present No device found for appliance 011090388878000094, cannot publish event Dishcare.Dishwasher.Event.SaltNearlyEmpty = BSH.Common.EnumType.EventPresentState.Present
This should be fixed in 1.3.3-b1 but you may have to uninstall and re-install the integration
1.3.3-b1
1.3.3-b1 is not disponible for the download I see in the hacs panel but is imbossible to download
The events are working fine after the update as far as I see. Thank you so much! One last thing, after the update to 1.3.2 (and 1.3.3-b1), i'm also missing this sensor: sensor.siemens_011090388878000094_bsh_common_option_programprogress. It doesn't excist anymore. Could that be right?
I can't think of a reason. Does sensor.011090388878000094_bsh_common_option_programprogress exist?
Ah okee. On this site you can see it exist: https://api-docs.home-connect.com/events/#availability-matrix Thank you in advance!
That just shows the option exists in general. It is not likely that it just disappeared because the integration doesn't delete entities. Use the developer tools to look for the entity above
I can't think of a reason. Does sensor.011090388878000094_bsh_common_option_programprogress exist?
I reverted to 1.2.1 today from a HA backup and noticed that all my missing entities came back. In 1.3.2 I get this message in the integration view when I look at the settings of one of these newly disabled entities. Is this related, or perhaps a totally separate issue/user-error? I’m not sure what has disabled all these entities in 1.3.2 that I use in a number of automations…
In previous version, before 1.3, the Home Assistant entity ID always started with the Home Connect ID (which confusingly is called HAID). This caused problems for users who wanted to use it in some templates. So version 1.3 changes the Home Assistant entity IDs in that case to begin with the brand name. That way they no longer start with a digit and everything works well in templates. To prevent breaking changes the integration checks if there are already existing entities without the brand name and if there are it doesn't add it. This describes how it was supposed to work, however, due to some bugs it didn't actually work like that in some cases. I believe that version 1.3.3-b1 has fixed all of those bugs, however, if you went through 1.3.1 and 1.3.2 you might be left with some dead entities. The easiest way to fix it is to remove the integration from Home Assistant and add it back. This will clear all the dead entities and create new ones with the new IDs schema.
In previous version, before 1.3, the Home Assistant entity ID always started with the Home Connect ID (which confusingly is called HAID). This caused problems for users who wanted to use it in some templates. So version 1.3 changes the Home Assistant entity IDs in that case to begin with the brand name. That way they no longer start with a digit and everything works well in templates. To prevent breaking changes the integration checks if there are already existing entities without the brand name and if there are it doesn't add it. This describes how it was supposed to work, however, due to some bugs it didn't actually work like that in some cases. I believe that version 1.3.3-b1 has fixed all of those bugs, however, if you went through 1.3.1 and 1.3.2 you might be left with some dead entities. The easiest way to fix it is to remove the integration from Home Assistant and add it back. This will clear all the dead entities and create new ones with the new IDs schema.
Gave this a shot. Completely removed the integration + repository download followed by HA restart for good measure. I did a fresh install of 1.3.3-b1, and then set it up first while keeping credentials from the old installation, and then a second time starting over and removing the credentials and redoing the Oauth procedure. However, about half of the entities are still disabled by the device in both cases. Any other recommendations for things I can try?
I don't know how entities get to this "disabled by device" state, the integration doesn't disable entities, it just makes them temporarily unavailable, which is a different thing. My guess is that those entities are left overs from the previous installation. I suggest you remove the integration again, then clean up any remaining entities (go to Settings - Devices & services - Entities and filter the list for disabled entities). Then reinstall. Hopefully this will eliminate all those deleted entities.
I tried again and deleted the integration, but all entities go with it when I do so and there are no disabled entities left over. I'll reinstall the integration and upload the debug log upon integration reload. I don't understand everything that is going on in the log, but it looks like the GET part of the API goes ok and has values for e.g. the door sensor entity, but then something else happens to them.
Thanks for your help!
Update: Removed and reinstalled the integration again and now all the entities are working. Not sure what I did differently this time, but could be this is the first time I’ve removed the integration with 1.3.3-b1 installed beforehand.
Here's the relevant part of the debug log before I removed and reinstalled the integration. In this log, I manually reloaded the integration at a moment when it had many of these disabled entitied (not remove/reinstall). After reloading those entities were still disabled.
home-assistant_home_connect_alt_2025-11-16T07-35-05.453Z.log
It's all working now for me, but not sure exaclty what I did that corrected the issue. Perhaps this helps pinpoint something.
So after doing that you still have deleted entities? Can you give the IDs of a couple of them please?
I no longer have any disabled entities, and this issue is resolved for me. I'm just not sure exactly what did it in the end since I removed and reinstalled the integration a few times, some without success and this last one apparently successfully. One of the previously disabled entities was e.g. sensor.siemens_dishwasher_operation_state. That particular entity was disabled on 1.3.3-b1 with the resulting log that I attached above.
I'm honestly not sure what caused it. As I mentioned, generally speaking, the integration doesn't entities so it shouldn't be able to cause entity to become deleted. Anyway, I'm glad that it's solved. I'm going to leave the issue open for a few more days, just in case someone with the same issue was following it that then close it if there are no additional comments.