Created a new user with pw to log in with from the Android, and even after a full restart of Home Assistant, I’m still not getting logged in, and still getting failed login attempt notifications on Notifications at lower left of the full sized rendering of the Dashboard. Is there likelihood that a browser user-interface which can’t create a new script also can’t create a new user, and at what point in creating a new user should I find that out ?
[edit] eventually and several tries later it did log in at the Android. Remote control of a fan heater by “smart plug” immediately demonstrated off a touchscreen handheld device, thanks to sensible layout of the default Overview.
[edit] from Android14 with 1GB of RAM, exactly the same sequence as above to create a new first script seems to have done that. I asked it to increment and then decrement a number helper, several times closing sections at x to find the action which I’d need on a small touchscreen, and pressing on the blue (Save). scripts.yaml does not say anywhere which number helper that should be poking, and I wasn’t asked.
[edit] back at the Pi 2, > Settings > ?&? > Scripts > now lists a New script which was editable from here and contained recent extra actions which had been added from Android. Disabled the not-working increment and decrement and saved. From … to the right of this New script, got it to run and switch the fan heater.
[findings] There seems to be something wrong at creation in memory, from at-least one 32-bit browser, of any new script. I’d had glitchy creation of new first automation too, getting glitched out at creation of a When in one attempt and at creation of a Then Do in the other.
Duplicate from … far right of the existing script in the 32-bit browser at http://homeassistant.local:8123/config/script/dashboard did make a duplicate and append that to the relevant scripts.yaml
Moving content of scripts.yaml to somewhere else linked to from configuration.yaml, and hand editing that content, including hand typing in the icon all worked, after Developer tools > Check configuration shows green and doing All YAML configuration.
It was only by hand editing yaml that I got to having automations for on and off which had both of the necessary When and Then Do items. So failure at creation of a new script is not the only to-do for the bugfix people. At least the interface falls back to a few steps before.
Anyone remember The Blue Screen Of Death from 1990’s computers? These failures seem to demonstrate that Home Assistant doesn’t do that.
At least I have a working first script to work from.
