Nicolas Glassey

How about adding a new variable for this to the u-boot environment ? Those won't be reset by anything the user does in the OS itself (through apt or anything...

Any update system that has to account for changes made by the user since the installation of the "known" image will be a massive pain in the lower back area......

Bump. #23 being solved, anything left to do for this ?

Any news on this ?

Anything we can do in the meantime?

Sorry. To either install them manually if they're not installed or... well, to help you ? :) The goal would be, as Bergmanu stated, to be able to install them...

I've also tried disabling the option, publishing the flow, re-enabling the option and re-publishing the flow, to no avail. You need to create a new node to have that function...

Today, I tried to simply add a new DIN with the correct settings, and that one didn't work either. It was on the very first run of Node-red. Is there...

Oh it just inverts the payload. ```js return { payload:!msg.payload } ``` Both function blocks were the same (copy-pasted).

So the trigger works on deploy for you after copy-pasting the node ? Odd... I don't think there's anything that you're missing in your flows. I guess the only variant...