6 Likes
I’m having serious issues with** input_text in the latest Home Assistant update! I had to roll back to a backup because there were just too many problems. I’m getting errors when trying to assign values using input_text.set_value **. Does anyone know what’s going on?
Protect stopped working. I have latest version of protect.
If you have input_text in yaml, that have a max value, make sure that max is <=255.
There was validation change that enforces that, given that any states longer than 255 are not legal and would generate an error.
Should be a message in your log about it if that was the case.
2 Likes
Also documented in the breaking changes above. See details here
1 Like
Error in describing action: Cannot read properties of undefined (reading ‘set_value’)
The value assigned to it is “Off”
Breaking changes suggests that a reauth will be presented if the API token can’t be created. However this is not correct for many cases (my case HA Unifi Protect user read only for control plane). So for me it was hidden in the logs that there was an issue to correct. Great help provided to get me going. Best would be to have a ‘Repair’ noted in this situation.
Special thanks to @piitaya and @MindFreeze, and @hmmbob for the quality-of-life improvements!
I frankly couldn’t care less about any of the generative AI stuff (sending data to OpenAI seems antithetical to Home Assistant’s purpose and all), but I am glad it’s not taking too much time away from other improvements. For example, controlling individual group members from the group entity dialog is the best change to the Home Assistant frontend I’ve seen in recent memory. I tried to implement this years ago but the frontend component code was beyond me. This will be a game changer for my 3 million light groups!
Now to go update all my automations to specify weekdays in the time trigger instead of a complex set of conditionals, another huge time saver 
15 Likes
I always check the logs after an upgrade and that’s where I found the issue too. I’m giving the integration developers a break since they put a lot of work to reverse engineer the API / token change to work. Perhaps they will have the “Repair” option in a future release.
Agree that the developers do a great job. Even a note in the breaking changes that not all cases may be covered by the expected flows would be great.
1 Like
I think I found the error. In the** configuration.yaml file, I have a line declaring input text like this: input_text: !include_dir_merge_named input_text . Inside that directory, there are many input_text entries with a max **value of 1000 instead of 255. The weird thing is that this causes all the other input_texts I’ve created through the interface to stop working! I’m going to try changing the length and see if they work. For now, I’ve commented out that line.
Is there a way to turn it off?
It’s all off by default, you have to set up AI integrations for it to do anything.
5 Likes
I could not work out how to fix it, so deleted the hub and set it up from scratch again following the docs.
Um, it’s the middle of winter down here In the southern hemisphere
5 Likes
“In most parts of the world, summer mode is in full effect! 
”
80% of the worlds population lives in the Northern Hemisphere also 80% of the worlds land mass lies there. So in “most parts of the world” it is summer. You weren’t being left out, if anything you got more recognition then necessary :).
3 Likes
You can pick whatever provider you like from home brew (mine selected for this purpose runs on a machine on my desk…)
You’re not married to OAI
6 Likes
This update looks very cool, and I did the beta updates earlier but had to roll back to 7.4 due to lots of my new Tuya lights just not work anymore. So sadly I don’t feel like spending more money getting all my light switches, power sockets replaced.
I don’t like new “Suggest with AI” button in UI, I don’t need any suggestions from AI.
Good thing it’s disabled by default.
“Control individual members of a group” - this one is useful, I think it would be nice to have a button to show/hide them.
I also want to remove “Effects” button from that dialog, I never use it like those scenes round buttons that you can remove. Ideally I want to remove or hide everything except of Turn on/off button to make that dialog more compact and minimal.
2 Likes
If the issue is specific to substitutions from the secrets file, that might be worth logging as a bug. Perhaps the new validation happens before the substitution happens, casing the whole input text integration to fail. Are all of your input text helpers unavailable when this issue happens? I see you’re referring to one’s created via the UI, but it’s not clear whether you have some created via YAML too.