Feature request: self-awareness of developer mode

already started via support request, but re-doiing here too

I'd like my flows to be self-aware of whether it's in Developer Mode or not, specifically so the tests we run can log whether this is the case.

Is there a way to determine this? I'd like to think I could pull a boolean of this from an environmental variable or something, but I can't find anything on this online.

This comes from me wanting to have better awareness of which devices are running in developer mode, as accessed by our production database, not the flowfuse UI. In each 'test' that our NR flows perform, it would be nice to be able to have a flag for whether it is in developer mode or not. We could then do alerting on this and analytics on how many of our tests were done in developer mode and over what time frame, etc. The flowfuse UI only gives a current snapshot, not historical.

This could also allow me to make sure certain flows stop at a certain point if in developer mode, further guarding from running production processes in developer mode accidentally

Hi @butteronadonut

Thanks for the feedback. There isn't currently a way to do this easily.

A challenge with using env vars is that it requires a restart of Node-RED in order pick any changes. We don't currently restart Node-RED when coming in/out of developer mode - so that would be a disruptive change to how it currently works.

I've raised Awareness of Developer Mode within Node-RED · Issue #326 · FlowFuse/device-agent · GitHub to capture the request.

Nick

1 Like