Known problems and limitations #2
Tom-Bom-badil
announced in
zz~ archived / deprecated or invalid
Replies: 1 comment
|
On the startup warnings in the log file: As a temporary fix (until I find a better solution) you can add the following to your logger:
default: warning
logs:
homeassistant.components.rest: critical
homeassistant.components.sensor: error |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This post lists the currently known problems and limitations. We are in a very early stage of development, and as with every software there are some things that do not work as intended. However - I think it is better to have a limited software, than no software to solve a problem.
Errors on startupThis one is related to the default starting sequence of HA. When HA is starting, entities are created, then integrations / compnents are intialized, then the entities -including our input_text's- get their values from the database (if configured that way).
Unfortunately, the REST integration seems to do a first run upon startup. As the input_text's do not yet have their values from the database, this will result in failures.
You will see a bunch of 'Unexpected error fetching rest data data', followed by 'Platform rest not ready yet: None; Retrying in background in 30 seconds' (1 log line per sensor). After a minute or so, everything is set, and the errors stop.
I am currently investigating how to solve this. It's not actually an error; it's annoying behavious, as it spoils the log file on HA start.
Side note: Already tried 'initial: attribute for the text_input's; no success.
Sensor errorsI have currently 2 sensors that are misbehaving for unknown reason: "UGreen NAS Memory Speed" and "UGreen NAS UPS Power Free". Not clue why, but from time to time these 2 do not initialize after a HA restart. They are commented out in
ugreen_nas_rest.yamlfor the moment. Feel free to experiment and uncomment, and please report back your findings.Reloading REST/YAML without restart if many sensors fail
Occasionally (1 in 20 restarts or so) there are more than just 1 or 2 REST sensors that do not initialize. You can force them to reload really quick and without restarting HA in two ways (one of them is sufficient to reload):
I am currently thinking about making an automation that does the RESFTful reload 60s after every HA restart, without any user interaction. That way it is ensured that all sensors are loaded properly.
All reactions