I have been using home assistant since 0.32. Since moving to 2021.12.7 on a new machine, when I turn on an input_boolean through the UI, it instantaneously switches back off. Mine are run of the mill and are defined in my configuration.yaml (old habits).
The docs don’t mention anything about a change in the behavior of an input_boolean in the UI.
Any idea why my input_boolean controls won’t stay set when I click on them?
My question woul dbe did they review ALL the Release Notes between 0.92 and 2021.12 for breaking changes> If not, do that and report back if you did not find your answer,
We are here to help people help themselves, not to encourage laziness.
No, I am trying to direct them to the pinned thread and common sense upgrade processes tso we can better assist them. The developers do not write Release notes just to waste time. I strongly suspect there was a documented breaking change. If it is not important enough for them to check, it is not important enough for me to do their work for them.
Stiltjack, now that I have retired from the crazy world of real work, I am excited to be back. It was pretty awkward being stuck on 0.99 without the spare time to move to the new stuff. You know how it is with Home Assistant: a labor of love. Based upon the date on my first enhancement request, Add random_offset: to platform: sun, I must have started my Home Assistant journey sometime in early 2017.
I searched the forum for various combinations of input_boolean won’t stay set on then off, etc, but is it so generic that I didn’t find anything that related to clicking a boolean in the UI and not have it stay set.
Pretty sure it is not a search-skills issue.
From my post: “The docs don’t mention anything about a change in the behavior of an input_boolean in the UI.”
That was a struggle. Would value feedback on what I should have selected.
Sorry. Didn’t think to apply a tag.
Both complete and sufficient: “Just upgraded to 2021.12.7 from 0.99 and input_boolean seems different”
From my post: “…when I turn on an input_boolean through the UI, it instantaneously switches back off. ”
Prodigyplace, I appreciate your motive in trying to make the forum be a useful resource for knowledge about Home Assistant. Given that you know nothing about me and my practices, the use of laziness is inappropriate. Per Stiltjack’s comment, maybe offer tips and tricks regarding effective knowledge discovery and forum engagement.
I will take the opportunity to explain why this forum will always be a help desk, which I have done in the past in this forum. For illustration, I will use the CalDav component. You are right that the key to successful knowledge sharing is the Home Assistant documentation. Here is the challenge: if one is honest about the currency, sufficiency, and completeness of the content, it would deserve no better than a B-. Here is why. The amount of knowledge about Home Assistant in this forum is both overwhelming and very inefficient to access. A significant amount of what is in this forum could be unnecessary with a simple change.
The culture change that would benefit everybody is to move away from the practice of providing knowledge in forum threads and move the collection of that knowledge into the documentation. The Caldav component is a good case in point. Do a quick search for Caldav iCloud. Many of those threads contain knowledge that should be on the Caldav integration page, which is far from sufficient. Many of them should be able to find their answers on the Caldav integration page. The Caldav page does not mention that adding the caldav component in configuration.yaml will — in the current version — add a Calendar item to the left rail. It only mentions two caldav products against which is has been tested. It makes no reference to iCloud. It has none of the specifics about the nuances that are associated with the iCloud configuration. It is silent about the functionality of the calendar that shows up in Home Assistant. Can the calendar be use to add new items, edit existing, are there any limitations.
I will encourage you to continue to be on the lookout for newbs in the forum and help shepherd them onto the straight and narrow. Maybe check to confirm newbness before considering them to be.
Then, I would challenge you to be on the lookout for posts in the forum that should really be updates or edits to documentation content. Teach users how to submit those changes. I have submitted some. It is not hard…… the second time. Maybe create a copy-and-paste reply with instructions how to submit a change to the knowledge content.
Until this becomes a community that values and curates knowledge content, the forum will always be the help desk where knowledge is buried in threads that are read by faithful members like you.
[I hold out little hope that it will ever change based upon the way software developers behave at work: knowledge about software functionality that can only be found in email, or jira stories, or from the most tenured member of the team. Few are those who value a single design document that describes the intended functionality of a specific software asset so that it is not necessary to search the inbox or the ticket system to try and figure out how it works. If the pros can’t do it, it is unreasonable to expect the hobbyists who enjoy investing their precious free time implementing Home Assistant to adopt the practice. Ed.]
I don’t imagine the development team has time to test all possible upgrade combinations, such as from an ancient version like 0.99 to the most recent version. It’s possible something didn’t convert correctly because an input_boolean that fails to hold its state is genuinely weird (and rare).
You might be facing the prospect of performing a new installation and then slowly adding whatever configuration data you have, taking care that some of your integrations may no longer be configurable via YAML.
FWIW, this is what I did, many versions ago, when I was faced with a leap of about (only) 4 versions. Installing from scratch allowed me to familiarize myself with the onboarding process (something one doesn’t see when performing upgrades) so it was instructive.
oh, yikes. I realize the title should be Just Installed fresh 2021.12.7 and input_boolean seems different.
Updated title and first post to clearly indicate that i am on a fresh install of the current version.
another suggestion would be to restore from a backup to your original version and then update one version at a time using the latest patch release (.99.x->.100.x->101.x->…2021.12.7).
that way you can be fairly sure that you can fix things as they break for each version rather than trying to fix potentially all issues at once.
TBH, I’m extremely surprised that you ONLY had issues with the input_booleans. And I’m REALLY surprised that you actually had any issues with input_booleans at all since I don’t remember any breaking changes with them.
sorry. had two hands full of chocolate covered espresso beans last night so working with zero sleep.
Supervisor is trying to install 2021.12.7. Since it is a new feature for me, i am guessing it truncates the log. here are the complete contents after i turned on an input_boolean and it immediately turned off.
2022-01-01 04:02:55 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to connect: Cannot connect to host a0d7b954-zwavejs2mqtt:3000 ssl:default [Connect call failed ('172.30.33.0', 3000)]
2022-01-01 04:02:55 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Cannot connect to host a0d7b954-zwavejs2mqtt:3000 ssl:default [Connect call failed ('172.30.33.0', 3000)]; Retrying in background
for good measure, i have sudo systemctl stop node-red so I am sure it is not doing anything on the backend.
Out of curiosity, have you tried without any custom_components? With such a long time between updates I’m shocked you don’t have a whole mess of problems and might be using outdated components or add-ons that are forcing you down a rabbit hole.
If it were me I would start as bare-bones as I could and work my way forward until the break. If it breaks at bare bones you might just be in a situation where you should restore .99 and incrementally upgrade until it breaks so you can figure out what went wrong and where.
That’s a pretty tough one, I don’t envy you figuring this one out!
Thanks for the extra eyes. I am so accustomed to looking “through” the browser that it is not something i usually consider.
Works as expected when I use safari.
What is interesting is that I have “always” only used Firefox with Home Assistant on my mac.
Build ID 20211218203254
edit to configuration.yaml
# per Taras' suggestion adding this to the config
# Configure a default setup of Home Assistant (frontend, api, etc)
Final edit: input_boolean state changes sync across Safari and the iOS app as expected.