Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: after Update to 2025.1.04 configured program is broken #116

Open
kwithus opened this issue Jan 16, 2025 · 4 comments
Open

BUG: after Update to 2025.1.04 configured program is broken #116

kwithus opened this issue Jan 16, 2025 · 4 comments
Labels
Next Release In next release

Comments

@kwithus
Copy link
Contributor

kwithus commented Jan 16, 2025

After I updated to the latest version, my configured test-program is broken.
The card is still shown, however I am no longer able to access the settings of the program.
Trying to open the configuration results in an error : 500 Internal Server Error Server got itself in trouble
Looking at the prior configured switched (enable program, enable zone etc.), they are no longer available
seems that the upgrade somehow deleted them.
I had to delete the configured program and re-configurate

Doing this I noticed another bug in the card-configuration

I named the program 'garten', the configuration created a switch.garten, however in the card YAML the switch was referred to as switch.garten_2, which resulted in an invalid card, as this entity doesn't exist. I renamed all instanced of switch.garten_2 in the card YAML to switch.garten and it worked.

greetings

Karl

P.S.: I first suspected, that the underlying issue might be that I already do have a sensor named switch.garten, but that's not the case. However, isn't that a realistic risk scenario? Shouldn't you probably add some clear differentiating "add on" to the name, as e.g. a leading 'irr' or similar? Or wouldn't an existing entity with the same name raise an issue, as HA distinguished based on underlying integration?

@petergridge
Copy link
Owner

Hi Karl,

Thanks I can see the issue, now I have to figure out what is causing it, another strange issue.

@petergridge
Copy link
Owner

I have resolved the issue, an interesting find, the entity_id changes as the program goes through the reload in HA. The entity_id is generated by HA using one of it's functions. Anyway I have moved the call to generate the yaml to later in the reload process and it is producing the expected output now.

I will release a new version soon.

in relation to:

I first suspected, that the underlying issue might be that I already do have a sensor named switch.garten, but that's not the case. However, isn't that a realistic risk scenario?

HomeAssistant will automatically append the _number if it finds something else with the same name.

Cheers
Pete

@kwithus
Copy link
Contributor Author

kwithus commented Jan 18, 2025

_ HomeAssistant will automatically append the number if it finds something else with the same name.

_ok, you are absolutely right, that's a standard behavior of HA, I forgot.

@kwithus
Copy link
Contributor Author

kwithus commented Jan 18, 2025

installed the update, added new zone, everything worked as expected.
However I still have to do the manually setup of the card by copy/paste the (new) YAML definition, which I believe is also expected as not addressed in this update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Next Release In next release
Projects
None yet
Development

No branches or pull requests

2 participants