Then tell me what that solution is.
I can’t find anything about what remote commands has been learned in HA.
Only in the .storage folder which means you need to either open it manually or use node red to read the content and create a sensor of it.
But please tell me how you would create the sensor then
I would create the sensor when I learn the commands and would never need to dig into .storage which you should not be doing. Your forgetfullness and edge case aren’t a reason to use node-red for what is essentially a one-off use case.
You mean manually?
That’s convenient. 
Just to get back to the reloading thing.
When I change something in configuration.yaml
(adding a sensor, changing a html-scrape or rest-api call)
I will have to go to Configuration / Server Control / Restart
resulting in HA restarting which takes approx 20-30 seconds on my RPi4"
Correct? Or did I miss something that makes all of this a lot faster? 
Yes, unless it comes under one of the categories below there on the page.
if you add/modify some entity of integration being already used, then it is enough to use reload feature (if does exist for this category) which executes almost instantly.
This way adding new mqtt sensor, or modifying light groups etc doesn’t require ha restart
It’s difficult to believe that somebody that has gone to some depth into both yaml and NR still defends yaml is so superior. I believe both can achieve similar things but there are major differences in the how.
It is common sense that if you need to write, let’s say, 50 lines of code in YAML to build something whereas in NR you can achieve the same with 5 lines of code, any human being is less prone to make an error in that scenario. It’s just common sense.
Not only that, but a decent chunck of the things you write in NR are fields that autocomplete.
Not only that but, when there’s an error you instantly spot it in NR following the flows course.
Not only that but, as it has been said, deploys are instant, but that’s not its biggest quality.
Maybe traces has improved something but, how come that, if YAML is so superior, that YAML is constantly adding new features, that have been there in NR from the beggining, to look more like NR? Like better debugging tools and improved templates, choose clause to mimic the branching ability of NR, diagrams for traces, and so on? Why isn’t NR improving to look more like YAML??
it’s also common sense and it has been demonstrated by science that human beings have better retention of images than words. So it’s not like: if you can grasp code you’ll preffer YAML, if you can’t and you are a visual thinker, go NR. Any human being has a better visual understanding of things than a symbolic approach. Get any mnemonic book or just see how diagrams, charts and graphics have been there in every school from childhood. Look how speech therapist work.
If you want to stay in YAML just do it but please don’t insult common sense. Just go YAML.
My mother, who is the most antitech person on the world, a person who struggles with Android, one day dared to play around with a door sensor and a light, and she loved it. She even went as far as to write a transition and some color changes and just loved it.
It’s hard to believe this thread has gone so far, some saying 2 + 2 = 4 and others saying it equals 5.
Anyways, mixing HA with NR they both get a lot better.
Why did you write this in reply to @duittenb’s specific, and rather reasonable question? This poster is looking for specific advice about a Home Assistant feature. I don’t see anything in their (now second) post on this topic that requires any Node Red information.
I’d just like to point something out here, if you’ll direct your eyes to your browser url bar, you’ll hopefully notice that you are on the Home Assistant Community. I’m not sure why you would expect people to NOT suggest using Home Assistant tools in a Home Assistant community. Yes NR definitely has a place in the ecosystem, and even excels in some areas, but (for instance) would you expect in a Hubitat community, for a member to just blanketly recommend Home Assistant over Hubitat for any and all use cases, especially when the topic doesn’t even require any mention of it whatsoever?
This is just me personally, but I tried Node Red and really didn’t like the way it worked conceptually. I didn’t like the ‘visual’ code layout, it seemed messy and it didn’t make it easier, for me. It wasn’t that I didn’t try, I’d read up on it and understood the approach they were taking. It just wasn’t “for me”. I wouldn’t stop anyone else from using it, or appreciating when someone does something particularly cool with it, but it’s still not a thing I ‘need’ in my personal home automation journey.
@duittenb I believe other posters have covered the general idea, but you mentioned scrape sensors and rest sensors. Rest is able to be reloaded, while scrape unfortunately, is currently not(afaik). You could put in a feature request to add scrape to the list of reloadable items. I’m sure other people would appreciate that being an option.
I used to be in your position as a new Home Assistant user, and much earlier in its development it almost always required a restart for reconfiguring things(and it took a lot longer to do).
Two things happened over time that made me have to restart much less often. 1) I’ve got things mostly where I want them in my home, so I don’t often need to make a lot of changes, and 2) Home Assistant is leaps and bounds beyond where it was when I began as far as working on most things directly in the UI.
And FWIW, personally, I’ve never really liked YAML either, but in most of my newer automations, I don’t even need to think about what the underlying code format is. I can create them directly in the UI, with all of the nice features like entity and device pickers, options for service calls (e.g. brightness and transitions), the recent tracing/debugging features, etc.
It’s difficult to believe that somebody that has gone to some depth in both yaml and NR still defends NR is so superior. (sorry my grammar is bad, just copying yours)
I look at node red flows people post and they are really hard to fathom. A whole lot of boxes joined by spidery arrow. Not for me. However I appreciate some people like it, so stop the sniping.
You generalise. Everyone is different. There are visual people for sure. But you cannot generalise that to the whole population, so lets just stick to the subject, like @duittenb was trying to do.
I said to some depth… it’s clear none of you two have gone deeply into it. That’s usually what happens with people not liking NR, they usually haven’t given NR a reasonable chance.
And yes, I’m generalising because I can. It’s widespread. I stick to that.
EDIT
@nickrout Why has traces added a visual diagram? To make things worse? Lol
Go to a thread discussing nr then
And that is because they have never needed to…
Still talking from ignorance… I said everything I needed to say. I’m off. Sorry for any trouble caused. Just don’t insult common sense.
the difficulty with common sense is that it is not very common.
