Hi all
I have an issue that’s causing me both troubles and headaches.
I try to keep my HA setup current, I run Hassio on an RPi-4 and choose to update when those are available. This time something broke big time.
At startup the notification gives me
Invalid config
The following integrations and platforms could not be set up:
input_number
default_config
Please check your config and logs.
My configuration.yaml has this at the top.
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
python_script:
api:
I have 0 idea where to start looking and at the moment I’m rather desperate since one of my main automations, which is calling input_number.set_value, is broken. I can add new input_number entities using configuration.yaml but in the GUI the helper section for input number is greyed.
Hi
I ran the CLI “ha core update --version 2021.10.4” command, very useful feature by the way, but I still get the error message and input_number seems to have dropped completely.
I don’t understand. The ONLY change I’ve done to my system for a few months is the upgrades as suggested by HA, not even the beta track.
I found this in the Core logs after a restart
Logger: homeassistant.components.input_number
Source: components/input_number/__init__.py:277
Integration: input_number ([documentation](https://www.home-assistant.io/integrations/input_number), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+input_number%22))
First occurred: 08:39:23 (1 occurrences)
Last logged: 08:39:23
Error adding entities for domain input_number with platform input_number
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in async_add_entities await asyncio.gather(*tasks) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 587, in _async_add_entity await entity.add_to_platform_finish() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 681, in add_to_platform_finish await self.async_added_to_hass() File "/usr/src/homeassistant/homeassistant/components/input_number/__init__.py", line 277, in async_added_to_hass value = state and float(state.state) ValueError: could not convert string to float: 'unavailable'
No change, input_number is still not loaded and I even tried loading 2021.10.2 without any progress. I’m franticly digging through my logs trying to find something to go at but I don’t even know where to start.
But some troubleshooting led me to delete my input_number file under /config/.storage and after that the input_number integration reappeared and I was able to add my previous input_number helper entries.
What, what was this about?
I have the same situation now. Input_number service has disappeared and is nowhere to be found. Automations using it are not working, Developer Tools/ Services does not find it.
Get the error:
Logger: homeassistant.components.automation.set_tank_current_level
Source: components/automation/__init__.py:525
Integration: Automation (documentation, issues)
First occurred: 09:41:00 (33 occurrences)
Last logged: 10:12:00
Error while executing automation automation.set_tank_current_level: Unable to find service input_number.set_value
Have the latest OS and core on rasp pi 4B 4. I have also a second system with same hardware and same sw updates. It is working alright there
Neither did renaming input_number file under /config/.storage
In persistent notifications there is now the following:
Obviously, because there is no service input_number anymore
How is it possible, that this kind ogf integral part of the core just disappears? How do I get it back?
EDIT:
I managed to sort the problem soon after, but in case it might help somone, a brief description. The error was caused by testing various values with Developer tools/ states. By mistake, I fed in a decimal value with comma as a decimal symbol insted of a dot.
This caused an error in the integration and thus led the system to disable it.
To solve the problem, I edited config/.storage/core_restore_state and corrected the value. It should be noted, that if you try to restart the system, it will write the current (faulty) value to the file before restarting. Obviously You should avoid that and the quick & dirty solution is to save the file and then pull the plug so the system has no change to write anything anymore
