5 ms·

Alternatively Homeassistant also offers an integration for Node Red, which feels a bit odd to work with at first but I learned to love it more and more. I never

by Dumbdo 6y ago

Alternatively Homeassistant also offers an integration for Node Red, which feels a bit odd to work with at first but I learned to love it more and more. I never really bothered to learn Homeassistants YAML automation syntax. https://nodered.org/ https://nodered.org/

OJFord 6y ago
I wish NodeRed had a YAML (or whatever) syntax though, something git-friendly; that it was a viewer/editor for a sane human-readable text format. (As I recall, it's JSON with lots of long numeric IDs for each node, semantic data also mixed with presentational - coordinates for how you laid it out in the visual editor, etc.)
- BrandoElFollito 6y ago
  Yes, this is also why I got rid of it when giving a try. This is not maintainable outside of the GUI
- theshrike79 6y ago
  NodeRED keeps its stuff in a single directory, which can be backed up easily. Also the state can be fully restored with just the contents of that directory. It's not git-friendly though, no easy way of versioning stuff really.
- spdustin 6y ago
  If you enable Node-RED "Projects" [0], you not only get git-friendly flow configs, but can have them automatically push to remote repos. [0]: https://nodered.org/docs/user-guide/projects/ https://nodered.org/docs/user-guide/projects/
  - OJFord 6y ago
    You got me excited for a second, but that seems just to be a UI for people that don't know what 'a git' is, and `commit -a`-ing of changes, in the same non-'git-friendly sane human-readable plaintext format' I was complaining about. I know what git is, so I can already `git commit -a -m 'Updated nodes'` if that's what I wanted, but it isn't, I want logical diffs that show me what I did and why; not spurious ID changes because I accidentally moved a node visually a millimetre or two.
    - spdustin 6y ago
      It does give you a better diff option, actually. :) It may not meet your needs, but it will show you a diff between commits that is more context-aware for Node-RED.

by Dumbdo 6y ago

OJFord 6y ago

I wish NodeRed had a YAML (or whatever) syntax though, something git-friendly; that it was a viewer/editor for a sane human-readable text format. (As I recall, it's JSON with lots of long numeric IDs for each node, semantic data also mixed with presentational - coordinates for how you laid it out in the visual editor, etc.)

BrandoElFollito 6y ago
Yes, this is also why I got rid of it when giving a try. This is not maintainable outside of the GUI
theshrike79 6y ago
NodeRED keeps its stuff in a single directory, which can be backed up easily. Also the state can be fully restored with just the contents of that directory. It's not git-friendly though, no easy way of versioning stuff really.
spdustin 6y ago
If you enable Node-RED "Projects" [0], you not only get git-friendly flow configs, but can have them automatically push to remote repos. [0]: https://nodered.org/docs/user-guide/projects/ https://nodered.org/docs/user-guide/projects/
- OJFord 6y ago
  You got me excited for a second, but that seems just to be a UI for people that don't know what 'a git' is, and `commit -a`-ing of changes, in the same non-'git-friendly sane human-readable plaintext format' I was complaining about. I know what git is, so I can already `git commit -a -m 'Updated nodes'` if that's what I wanted, but it isn't, I want logical diffs that show me what I did and why; not spurious ID changes because I accidentally moved a node visually a millimetre or two.
  - spdustin 6y ago
    It does give you a better diff option, actually. :) It may not meet your needs, but it will show you a diff between commits that is more context-aware for Node-RED.