pyscript

1) You can basically do this today with Blueprints. There's also things like Pyscript [0]. 2) The Node-RED implementation in HA is phenomenal and kids can very easily use with a short introduction. 3) Again, already there. ESPHome is a first class citizen in HA. I feel like you've not read the HA docs [1,] or took the time to understand the architecture [2]. And, for someone who has more than enough self-proclaimed skills, this should be a very understandable system. [0] https://github.com/custom-components/pyscript [1] https://www.home-assistant.io/docs/ [2] https://developers.home-assistant.io/

If you are expecting auto discovery of state variables or service calls then that would be nice, but that seems like a bit too much to ask. And it's not something that I personally feel is necessary as you're likely already are familiar enough with the home assistant states/services that you want to interact with by checking them out in the home assistant developer UI. My PyCharm just shows those types as unknown, not as errors. I get auto completion & type checking for all the code I write myself. It's also important to note that PyScript isn't regular python. Instead it's an interpreted script[1] that is compatible with the Python syntax. This is unfortunate, but enables most of the magic of PyScript which otherwise would not be practical. [1] https://github.com/custom-components/pyscript/blob/master/cu...

Pyscript adds rich Python scripting to HASS : https://github.com/custom-components/pyscript An example script: @state_trigger("security.rear_motion == '1' or security.side_motion == '1'") @time_active("range(sunset - 20min, sunrise + 20min)") def motion_light_rear(): """Turn on rear light for 5 minutes when there is motion and it's dark""" task.unique("motion_light_rear") log.info(f"triggered; turning on the light") if light.outside_rear != "on": light.turn_on(entity_id="light.outside_rear", brightness=255) task.sleep(300) light.turn_off(entity_id="light.outside_rear") It's what made me ditch node red after going down the same path.

> ... for the off->on transition and another for the on->off. It'd be nice to set a rule that defines a level rather than an edge and have it internally do the transformation The "solution" I found was to poll, and use "choose", and sometimes some helper switches for state, to do what is needed. But, I think at any reasonable level of complexity, you're better off using one of the three python components: the one built into Home Assistant, pyscript, or AppDaemon. Home Assistant Python: https://www.home-assistant.io/integrations/python_script/ No imports. pyscript: https://github.com/custom-components/pyscript Full python. Supports Jupyter. Straightforward. AppDaemon: https://appdaemon.readthedocs.io/en/latest/HASS_TUTORIAL.htm... Full python. A little lower level. Allows the creation of dashboards. Related, the Matter protocol is on its w

You can try pyscript (https://github.com/custom-components/pyscript), which allows you to write automations in plain Python.

You can try pyscript (https://github.com/custom-components/pyscript), which allows you to write automations in plain Python.

There's also PyScript, a custom component that allows you to write automations in Python. The docs have a bunch of nice examples that give you an idea how it looks. https://github.com/custom-components/pyscript https://hacs-pyscript.readthedocs.io/en/stable/tutorial.html...